VMware Integrated OpenStack 6.x backup will fail if a datacenter name includes a period followed by a capital letter

Products

• VMware
• VMware Integrated OpenStack

Issue/Introduction

Symptoms:
If the datacenter specified in the backup configuration has a period followed by a capital letter the backup initialization will fail. In the backup pod you will find a log entry similar to the following:

{"state":"Failed","conditions":{"backup-config":{"State":{"terminated":{"exitCode":1,"reason":"Error","message":"time=\"2020-03-16T10:04:27Z\" level=info msg=\"successfully created k8sClientSet\"\nfailed to backup openstack configuration: load gvk vio.vmware.com/v1alpha1, Kind=TEST in namespace: openstack failed, err: no matches for kind \"TEST\" in version \"vio.vmware.com/v1alpha1\"","startedAt":"2020-03-16T10:04:27Z","finishedAt":"2020-03-16T10:04:35Z","containerID":"docker://b0169372225fe557479b01013f429812b8b1149709c5c4d1197279f489504436"}}},"backup-mariadb":{"State":{"waiting":{"reason":"PodInitializing"}}},"upload":{"State":{"waiting":{"reason":"PodInitializing"}}}}}
failed to create backup backup112: failed to create backup, see status of backup backup112 for details

Environment

VMware Integrated OpenStack 6.x

Cause

The period itself in the custom resources for glance is causing the issue. The manager for VMware Integrated OpenStack returns an error when encountering it.

Resolution

VMware Integrated OpenStack 7.x resolves this issue by accepting the special characters.

To resolve this on VMware Integrated OpenStack 6.x we will need to perform the following:

1. SSH to the management server for VMware Integrated OpenStack as root.
2. Save the current settings for glance with the following command: osctl get glance <glanceXXX> -oyaml > <glanceXXX>.yml
3. Edit the vmware_datastores configuration of the Glance custom resource. Open the file with osctl edit glance. Perform the following change:

spec:
  conf:
    backends:
      vmware_backend:
        vmware_datastores: debug <----change the config here to "debug"
        vmware_insecure: .VCenter:vcenter1:spec.insecure
        vmware_server_host: .VCenter:vcenter1:spec.hostname
        vmware_server_password: .VCenter:vcenter1:spec.password
        vmware_server_username: .VCenter:vcenter1:spec.username
      vmware_backend2:
        vmware_datastores: debug <----change the config here to "debug
        vmware_insecure: .VCenter:vcenter2:spec.insecure
        vmware_server_host: .VCenter:vcenter2:spec.hostname
        vmware_server_password: .VCenter:vcenter2:spec.password
        vmware_server_username: .VCenter:vcenter2:spec.username
  manifests: <----add live_debug flag here
    live_debug: true

4. Watch for the re-deployment of the Glance pods with: pods |grep glance
5. Perform the backup.
6. After the backup is finished and verified in the content library change the Glance custom resource back.