Skip to content
New issue

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

Create / Save swith settings failed after a fresh installation #8144

Open
stgmsa opened this issue May 13, 2024 · 1 comment
Open

Create / Save swith settings failed after a fresh installation #8144

stgmsa opened this issue May 13, 2024 · 1 comment

Comments

@stgmsa
Copy link
Contributor

stgmsa commented May 13, 2024

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:

  1. prepare a Rocky linux environment
  2. install packetfence using the suggested steps
  3. after the installation is done, go throught the configurator
  4. in mysql configuration during configurator, keep default settings (auth root and pf password)
  5. at last step of configurator, click "start packetfence"
  6. login in to the admin UI and select "configuration" -> "Policy and access control" -> "switches"
  7. create a new switch or click on any existing switch, and save.
  8. hit the 500 error.

Screenshots
Here's the errors:
It's probably due to a bad mysql password / connection.
image

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):

  • OS: Mac / independent
  • Browser: chrome / independent
  • Version: any
@satkunas
Copy link
Contributor

satkunas commented Jul 9, 2024

@stegar123 check if this is needed in 14, or if we can do post-release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants