Verify the restored environment
To confirm your recovery efforts were successful, check the health and status of all your OpenStack services.
Before you begin
- You have completed all restore procedures.
Procedure
-
Verify the control plane status:
$ oc get openstackcontrolplane -n openstackThe control plane should show
Readystatus. -
Verify that all pods are running:
$ oc get pods -n openstack --no-headers | grep -v Completed | grep -v RunningThis command should return no results if all pods are running or completed.
-
Verify OpenStack endpoints:
$ oc exec -t openstackclient -n openstack -- openstack endpoint listAll expected service endpoints should be listed.
-
Verify compute services:
$ oc exec -t openstackclient -n openstack -- openstack compute service listAll compute services should show
upstatus. -
Verify network agents:
$ oc exec -t openstackclient -n openstack -- openstack network agent listAll network agents should show
upstatus. -
Verify that all labeled resources were restored:
$ oc get $(oc api-resources --verbs=list -o name | paste -sd, -) \ -l backup.openstack.org/restore=true -n openstack 2>/dev/null -
Test instance operations on existing instances:
$ oc exec -t openstackclient -n openstack -- openstack server list$ oc exec -t openstackclient -n openstack -- openstack server stop <instance-name> $ oc exec -t openstackclient -n openstack -- openstack server start <instance-name>where:
-
<instance-name> - Specifies an actual instance name from your environment.
-
-
Optional: Create a test instance, for example:
$ oc exec -t openstackclient -n openstack -- openstack server create \ --flavor m1.small --image cirros --network default test-post-restore -
Optional: Run Tempest tests:
$ oc apply -f <your-tempest-cr.yaml>where:
-
<your-tempest-cr.yaml> - Specifies the name of your Tempest test configuration file.
If services are not running, check pod logs for errors.
-