We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug After a fresh install of PF v13.2, saving switch settings failed with a 500 response code from backend API
To Reproduce Steps to reproduce the behavior:
Screenshots Here's the errors: It's probably due to a bad mysql password / connection.
waiting for quite a long time (to make sure all the required services are ready) after going through configurator won't help.
This error can be avoided if we manaully restart pfperl-api after configurator.
Expected behavior after a fresh installation, all api calls that read / writes database works properly.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered:
@stegar123 check if this is needed in 14, or if we can do post-release?
Sorry, something went wrong.
fix(configurator(js)): restart pfperl-api, fixes #8144
3c88556
fix(configurator(js)): reorder pfperl-api restartm, fixes #8144
ac7114d
JeGoi
stegar123
No branches or pull requests
Describe the bug
After a fresh install of PF v13.2, saving switch settings failed with a 500 response code from backend API
To Reproduce
Steps to reproduce the behavior:
Screenshots
Here's the errors:
It's probably due to a bad mysql password / connection.
waiting for quite a long time (to make sure all the required services are ready) after going through configurator won't help.
This error can be avoided if we manaully restart pfperl-api after configurator.
Expected behavior
after a fresh installation, all api calls that read / writes database works properly.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: