You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ cou upgrade --auto-approve
...
Upgrade plan for 'neutron-api-plugin-ovn' to 'victoria' executed in 2 seconds ✔
Upgrade plan for 'octavia-dashboard' to 'victoria' executed in 2 seconds ✔
Upgrade plan for 'octavia-diskimage-retrofit' to 'victoria' executed in 2 seconds ✔
Verify that all 'nova-compute' units has been upgraded ✖
2024-07-03 06:54:49 [ERROR] Units 'nova-compute/0, nova-compute/1, nova-compute/2, nova-compute/3, nova-compute/4' did not reach victoria.
2024-07-03 06:54:49 [ERROR] See the known issues at https://canonical-charmed-openstack-upgrader.readthedocs-hosted.com/en/stable/reference/known-issues/
I can see that Verify that all 'nova-compute' units has been upgraded ✖ step failed, but this comes directly after Upgrade plan for 'octavia-diskimage-retrofit' to 'victoria' executed in 2 seconds ✔. My first thought is "why is it verifying upgraded before it's actually upgraded the units?". It would be good to print each step/substep before it's executed so we can have a complete log of steps with the default verbosity.
The text was updated successfully, but these errors were encountered:
@Pjack this isn't about this specific failure, this is about in general providing more useful output to stdout. There is more output of the steps in the logs, but we should be providing better information directly to the user at the console output.
I had this case:
I can see that
Verify that all 'nova-compute' units has been upgraded ✖
step failed, but this comes directly afterUpgrade plan for 'octavia-diskimage-retrofit' to 'victoria' executed in 2 seconds ✔
. My first thought is "why is it verifying upgraded before it's actually upgraded the units?". It would be good to print each step/substep before it's executed so we can have a complete log of steps with the default verbosity.The text was updated successfully, but these errors were encountered: