Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-9613

For deployments with multiple nodesets all NodeSet statuses shows "Deployment not started" even after some are deployed

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • openstack-operator-container-1.0.2-3
    • ?
    • ?
    • None
    • Important

       

      [stack@osp-df-4 install_yamls]$ oc get openstackdataplanenodeset
NAME                  STATUS   MESSAGE
openstack-edpm-ipam   False    Deployment not started
openstack-edpm1       False    Deployment not started
 
[stack@osp-df-4 install_yamls]$ oc get openstackdataplanenodeset/openstack-edpm1 -o yaml
<snip>
  conditions:
  - lastTransitionTime: "2024-08-21T08:37:51Z"
    message: Deployment not started
    reason: Requested
    severity: Info
    status: "False"
    type: Ready
  - lastTransitionTime: "2024-08-21T08:37:51Z"
    message: Deployment not started
    reason: Requested
    severity: Info
    status: "False"
    type: DeploymentReady
  - lastTransitionTime: "2024-08-21T05:49:14
<snip>
  deploymentStatuses:
    edpm-deployment:
    - lastTransitionTime: "2024-08-21T08:37:49Z"
      message: Deployment completed
      reason: Ready
      status: "True"
      type: NodeSetDeploymentReady
<snip>

       

       

      This is because we check the we don't set the NodeSetHashes when setting NodeSetDeploymentReadyCondition to true. It's only set when deployment for all nodesets finish.

            rhn-support-ramishra Rabi Mishra
            rhn-support-ramishra Rabi Mishra
            rhos-dfg-df
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: