Hide Forgot
Description of problem: After upgrade user unable to spin any VMs up Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Full description: Description of problem: After upgrade user unable to spin any VMs up: - The update was started on 7th of June. Case related 02401260 - The update on the controller completed on the 24th of June. Then had outage the next day. - Stuck on updating compute nodes. case related 02401260 - rebooted all of that control node - there are these two containers unhealthy on overcloud-controller-2: -> nova_metadata Up 3 hours (unhealthy) -> nova_api Up 3 hours (unhealthy) To resolve the issue: - Restart nova_metadata and nova_api - restart the nova container on compute node 2 Version-Release number of selected component (if applicable): openstack-keystone-13.0.2-4 How reproducible: Rebooted all of that control node Steps to Reproduce: 1. Minor update 2. Rebooted all of that control node 3. Actual results: No all container go up in good status Expected results: All work fine Additional info: This is similar to this upstream bug https://bugs.launchpad.net/starlingx/+bug/1823375
I have closed this bug as it has been waiting for more info for 4 weeks. We only do this to ensure that we don't accumulate stale bugs which can't be addressed. If you are able to provide the requested information, please feel free to re-open this bug.