Describe the bug
I have been testing Pegaprox since March, and the most recent update has seemingly caused Pegaprox to be almost unusable in my environment. Previously, tasks such as clicking on a cluster name would load the overview of the cluster inside of 5 seconds; we're now seeing 30+ seconds before the information is populated. This happens every time you click on a different cluster. Additionally, one of my go-to-tasks on testing new versions of Pegaprox is cross-cluster migration of VMs. In this version, it is almost impossible to even initiate a cross-cluster migration, as the dialog box times out waiting for information on the target cluster to load. You have to close it out and re-open it multiple times to get the destination cluster information to populate. See attached screenshots.
We're also seeing things like the Tasks list going completely blank, or being unable to display the task output, instead displaying messages like, "Error reading log" or "No output available." About once every ten or so tries you can get the actual log output to display.
Other things like the syslog viewer on a cluster just give "Failed to load log events."
Under version 0.9.11 we were not experiencing any of these issues. No timeouts trying to view logs or setup cross-cluster migrations.
Pegaprox is deployed via Docker Compose. No changes have been made to the underlying Docker host. No changes have been made to the Compose config. I have tried to roll back to an earlier version of Pegaprox to see if the issues persist, but the backups dialog is showing no backups found. I don't know if this is because it is also timing out or if it actually can't find any backups.
After experiencing these issues, I re-deployed with Docker Compose, pulling a new copy of the image. The issues reported above are still being experienced.
I would be glad to provide additional information, but I am not seeing any log messages in Docker about timeouts regarding these things. If you can direct me to where I can find additional information about the problem, I would be happy to provide.
Environment
- PegaProx Version: 0.9.13.2
- Installation Method: Docker Compose
- OS: Ubuntu 24.04
- Browser: Chrome 148
- Behind Reverse Proxy? Yes, Zoraxy
- UI? Proxmox Dark
Screenshots
Checklist
Describe the bug
I have been testing Pegaprox since March, and the most recent update has seemingly caused Pegaprox to be almost unusable in my environment. Previously, tasks such as clicking on a cluster name would load the overview of the cluster inside of 5 seconds; we're now seeing 30+ seconds before the information is populated. This happens every time you click on a different cluster. Additionally, one of my go-to-tasks on testing new versions of Pegaprox is cross-cluster migration of VMs. In this version, it is almost impossible to even initiate a cross-cluster migration, as the dialog box times out waiting for information on the target cluster to load. You have to close it out and re-open it multiple times to get the destination cluster information to populate. See attached screenshots.
We're also seeing things like the Tasks list going completely blank, or being unable to display the task output, instead displaying messages like, "Error reading log" or "No output available." About once every ten or so tries you can get the actual log output to display.
Other things like the syslog viewer on a cluster just give "Failed to load log events."
Under version 0.9.11 we were not experiencing any of these issues. No timeouts trying to view logs or setup cross-cluster migrations.
Pegaprox is deployed via Docker Compose. No changes have been made to the underlying Docker host. No changes have been made to the Compose config. I have tried to roll back to an earlier version of Pegaprox to see if the issues persist, but the backups dialog is showing no backups found. I don't know if this is because it is also timing out or if it actually can't find any backups.
After experiencing these issues, I re-deployed with Docker Compose, pulling a new copy of the image. The issues reported above are still being experienced.
I would be glad to provide additional information, but I am not seeing any log messages in Docker about timeouts regarding these things. If you can direct me to where I can find additional information about the problem, I would be happy to provide.
Environment
Screenshots
Checklist