viocli stop/start services command timing out

Products

• VMware Integrated OpenStack

Issue/Introduction

You started deployment but the state shown as STARTING first and times out later.
# viocli get deployment
OpenStack Deployment State: STARTING

# viocli start services
requesting to start services...
2021/01/14 15:04:54 the operation timed out

Environment

6.x, 7.x

Cause

• Starting services timed out because cinder service is in stop mode.
• User has stopped cinder service individually
• Based on current design, starting all services can not bring back individually stopped service(s). 

# viocli get deployment
SERVICE       CONTROLLER                READY   FAILURES
cinder        cinder-api                 0/0       -
              cinder-backup              0/0       -
              cinder-scheduler           0/0       -
              cinder-volume              0/0       -

Resolution

Before starting all services, the individual services that were stopped before need to be restarted.

• If deployment in STOPPED state use the command:

viocli start service cinder

Note: This would apply to any service that was individually stopped.  That service would have to be restarted similar to above.

• If deployment is in STARTING state you can not use the command to start individual service as shown below.  In this case, we must remove the mode key from osdeployment.

# viocli start service cinder
2021/01/19 09:13:17 service cinder are already starting

• Do the following:

osctl edit osdeployment

• Search for:

/mode: stop

• remove line mode: stop under -conf: Cinder:cinder1

- conf: Cinder:cinder1
   mode: stop
   name: cinder1
   service: cinder