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

Wait-for install-complete did not exit upon completion.

XMLWordPrintable

    • Moderate
    • Agent Sprint 226, Agent Sprint 227
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When the cluster install finished, wait-for install-complete command didn't exit as expected.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1. Get the latest agent-installer and build image
      git clone https://github.com/openshift/installer.git
      cd installer/
      hack/build.sh
      Edit agent-config and install-config yaml file
      Create the agent.iso image:
      OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=quay.io/openshift-release-dev/ocp-release:4.12.0-ec.3-x86_64 bin/openshift-install agent create image --log-level debug
      
      2. Install SNO cluster
      virt-install --connect qemu:///system -n control-0 -r 33000 --vcpus 8 --cdrom ./agent.iso --disk pool=installer,size=120 --boot uefi,hd,cdrom --os-variant=rhel8.5 --network network=default,mac=52:54:00:aa:aa:aa --wait=-1 
      
      3. Run 'bin/openshift agent wait-for bootstrap-complete --log-level debug' and the command finished as expected.
      
      4. After 'bootstrap' completion, run 'bin/openshift agent wait-for install-complete --log-level debug', the command didn't finish as expected.
      
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

        1. agent-config.yaml.sno
          0.8 kB
        2. install-config.yaml.sno
          0.6 kB
        3. wait-for.output.compact
          677 kB
        4. wait-for.output.sno
          128 kB

            afasano@redhat.com Andrea Fasano
            rh-ee-zniu zhenying niu
            zhenying niu zhenying niu
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: