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

Unable to use ICIC as Cloud Provider to create clusters with RHACM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • 4.16.z
    • None
    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          There is no cloud provider option in RHACM to use IBM Cloud Infrastructure Center (ICIC) to create clusters. Since ICIC and RHOSP are similar I attempted to use the RHOSP cloud provider template to create a cluster using ICIC. However, since the storage and compute information is different in LinuxONE I am unable to create any clusters using this method. 

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

          RHACM 2.11.2 OCP 4.16.4

      How reproducible:

          Easily

      Steps to Reproduce:

          1. Generate a CIC instance to target
          2. Create a credential for RHOSP and in the clouds.yaml file provide your info to reach your cic instance and authenticate with it
          3. Fill out the RHACM templates to create a cluster automatically and use your cloud provider credential to fill out the templates.
          4. Try to create the cluster
          

      Actual results:

          time="2024-09-18T16:10:02Z" level=debug msg="Collecting applied cluster api manifests..."985time="2024-09-18T16:10:02Z" level=error msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: infrastructure was not ready within 15m0s: client rate limiter Wait returned an error: context deadline exceeded"986time="2024-09-18T16:10:02Z" level=info msg="Shutting down local Cluster API controllers..."987time="2024-09-18T16:10:02Z" level=info msg="Stopped controller: Cluster API"988time="2024-09-18T16:10:02Z" level=warning msg="process cluster-api-provider-openstack exited with error: signal: killed"989time="2024-09-18T16:10:02Z" level=info msg="Stopped controller: openstack infrastructure provider"990time="2024-09-18T16:10:02Z" level=info msg="Shutting down local Cluster API control plane..."991time="2024-09-18T16:10:03Z" level=info msg="Local Cluster API system has completed operations"992time="2024-09-18T16:10:04Z" level=error msg="error after waiting for command completion" error="exit status 4" installID=5vnwmgmp993time="2024-09-18T16:10:04Z" level=error msg="error provisioning cluster" error="exit status 4" installID=5vnwmgmp994time="2024-09-18T16:10:04Z" level=error msg="error running openshift-install, running deprovision to clean up" error="exit status 4" installID=5vnwmgmp995time="2024-09-18T16:10:04Z" level=debug msg="Unable to find log storage actuator. Disabling gathering logs." installID=5vnwmgmp996time="2024-09-18T16:10:04Z" level=info msg="saving installer output" installID=5vnwmgmp997time="2024-09-18T16:10:04Z" level=debug msg="installer console log: level=warning msg=Failed to generate OpenStack cloud info: could not find an available volume availability zone\nlevel=warning msg=Empty OpenStack cloud info and therefore will skip pre-flight validation.\nlevel=info msg=Credentials loaded from file \"/etc/openstack/clouds.yaml\"\nlevel=info msg=Consuming Install Config from target directory\nlevel=info msg=Manifests created in: cluster-api, manifests and openshift\nlevel=warning msg=Found override for release image (quay.io/openshift-release-dev/ocp-release:4.16.12-multi). Please be warned, this is not advised\nlevel=info msg=Consuming Master Machines from target directory\nlevel=info msg=Consuming Openshift Manifests from target directory\nlevel=info msg=Consuming Worker Machines from target directory\nlevel=info msg=Consuming Common Manifests from target directory\nlevel=info msg=Consuming OpenShift Install (Manifests) from target directory\nlevel=info msg=Ignition-Configs created in: ....998time="2024-09-18T16:10:04Z" level=debug msg="no additional log fields found" installID=5vnwmgmp999time="2024-09-18T16:10:04Z" level=error msg="failed due to install error" error="exit status 4" installID=5vnwmgmp1000time="2024-09-18T16:10:04Z" level=fatal msg="runtime error" error="exit status 4"

      Expected results:

          Cluster gets created and imported into hub cluster config automatically

      Additional info:

          

              jpoulin Jeremy Poulin
              zcast Zechariah Castillo (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: