Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-9117

Vsphere cluster uninstall pod stuck if given the invalid --vsphere-cluster value when installation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • 4.10
    • Hive
    • Moderate
    • None
    • Unspecified
    • If docs needed, set a value

      Description of problem:
      Installing the cluster on the Vsphere platform,an invalid value for `vsphere-cluster` in the install-config.yaml , the pod can be created successfully, but due to the wrong flag information, the cluster installation fails. An uninstall pod is created but it is in CrashLoopBackOff,uninstall pod cannot be deleted.
      Does this bug need installer development to fix?

      e.g. when an invalid value for `network`,installer will not be able to create the infra id,it is skipped directly when destroying, so it can be deleted successfully.
      $ oc get cd
      NAME INFRAID PLATFORM REGION VERSION CLUSTERTYPE PROVISIONSTATUS POWERSTATE AGE
      mihuangnetwork vsphere unknown Provisioning Initialized 4m3s
      mihuangv mihuangv-z5knh vsphere unknown Provisioning Initialized 66m

      Version-Release number of selected component (if applicable):
      registry.ci.openshift.org/ocp/release:4.10.0-0.nightly-2022-02-09-054720

      How reproducible:
      Always

      Steps to Reproduce:
      1.provision a vsphere cluster by set invalid value for `vsphere-cluster` .
      2.wait it failed, then delete the clusterdeployment
      3.the clusterdeployment can not deleted.
      4.check the pod log.

      Actual results:
      $ oc get pod
      NAME READY STATUS RESTARTS AGE
      mhvspher-0-445p8-provision-jxh8w 0/3 Completed 0 112m
      mhvspher-1-l5hpq-provision-zdzqp 0/3 Completed 0 110m
      mhvspher-uninstall-kwplb 0/1 CrashLoopBackOff 13 (2m20s ago) 45m

      Expected results:
      We expect that uninstall pods can also be cleaned up.

      Additional info:
      #uninstall pod log
      '/vsphere/./..2022_02_12_13_56_41.155095920' -> '/etc/pki/ca-trust/source/anchors/./..2022_02_12_13_56_41.155095920'
      '/vsphere/./..2022_02_12_13_56_41.155095920/.cacert' -> '/etc/pki/ca-trust/source/anchors/./..2022_02_12_13_56_41.155095920/.cacert'
      '/vsphere/./..data' -> '/etc/pki/ca-trust/source/anchors/./..data'
      '/vsphere/./.cacert' -> '/etc/pki/ca-trust/source/anchors/./.cacert'
      time="2022-02-12T14:39:52Z" level=debug msg="Couldn't find install logs provider environment variable. Skipping."
      time="2022-02-12T14:39:52Z" level=info msg="running file observer" files="[/vsphere-creds/..2022_02_12_13_56_41.255556917/password /vsphere-creds/..2022_02_12_13_56_41.255556917/username]"
      I0212 14:39:52.904972 1 observer_polling.go:159] Starting file observer
      time="2022-02-12T14:39:53Z" level=debug msg="Find attached objects on tag"
      time="2022-02-12T14:39:54Z" level=fatal msg="Runtime error" error="list attached objects [mhvspher-wxrw8]: GET https://vcenter.sddc-44-236-21-251.vmwarevmc.com/rest/com/vmware/cis/tagging/tag/id:mhvspher-wxrw8: 404 Not Found"

              Unassigned Unassigned
              mihuang@redhat.com Mingxia Huang
              Mingxia Huang Mingxia Huang
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: