I confirmed the same symptom in OpenStack Train environment using Placement charm.
After upgrading the nova-cloud-controller to cs:~openstack-charmers-next/nova-cloud-controller-475, the issue was mitigated.
Since this is affecting customer's deployment, I have subscribed this to field-high.
Can this fix be backported to stable charm as well?
Thank you
I confirmed the same symptom in OpenStack Train environment using Placement charm. controller to cs:~openstack- charmers- next/nova- cloud-controlle r-475, the issue was mitigated.
After upgrading the nova-cloud-
Since this is affecting customer's deployment, I have subscribed this to field-high.
Can this fix be backported to stable charm as well?
Thank you