The VIO status transitions from STARTING to RECONFIGURING.

Products

• VMware Integrated OpenStack

Issue/Introduction

• The OpenStack Deployment is in the RECONFIGURING state. 
• viocli check health indicates everything is fine.
• The deployment was initially stuck in the STARTING state before transitioning to RECONFIGURING.

Environment

7.x

Cause

• The log bundle indicates an issue with the job that was not completed, which aligns with the message as RECONFIGURING.

./pods/openstack/controller-**********/others/health-controller.log

Nov 16 16:06:39 controller-********** health-controller[721]: time="2023-11-16T16:06:39Z" level=info msg="Checking job helm-neutron-neutron*-********* ... not completed, created at 2023-10-30 13:46:28 +0000 UTC (resync period is 15s)."
Nov 16 16:06:39 controller-********** health-controller[721]: time="2023-11-16T16:06:39Z" level=info msg="status state computed as RECONFIGURING"
Nov 16 16:07:06 controller-********** health-controller[721]: time="2023-11-16T16:07:06Z" level=info msg="Checking job helm-neutron-neutron*-********* ... not completed, created at 2023-10-30 13:46:28 +0000 UTC (resync period is 15s)."
Nov 16 16:07:06 controller-********** health-controller[721]: time="2023-11-16T16:07:06Z" level=info msg="status state computed as RECONFIGURING"

Note: The preceding log excerpts are only examples. Date, time, and jobs may vary depending on your environment

Resolution

• Identify the failed job in the log.
  

  # osctl get job | grep helm-neutron
  
     - openstack helm-neutron-neutron*-********** 0/1 17d 17d
  
     - openstack helm-neutron-neutron*-********** 1/1 25s 14d

• Remove the job.
  

  # osctl delete job helm-neutron-neutron*-*********