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

Cluster-bot cannot launch `no-capabilities` clusters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.16.0
    • Test Infrastructure
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • Architecture Call

      Description of problem:

      With the change in OCPBUGS-33793, cluster bot fails to create clusters when the "no-capabilities" option is set

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

      4.16.0-0 (ci and nightly)

      How reproducible:

      Always

      Steps to Reproduce:

      cluster-bot: launch 4.16.0-0.ci aws,no-capabilities

      Actual results:

      
Cluster fails to be provisioned - level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: capabilities: Invalid value: types.Capabilities{BaselineCapabilitySet:"None", AdditionalEnabledCapabilities:[]v1.ClusterVersionCapability{"MachineAPI", "CloudCredential", "CloudControllerManager"}}: the Ingress capability is required

      Expected results:

      
Cluster can be provisioned with no capabilities

      Additional info:

      
Example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/release-openshift-origin-installer-launch-aws-modern/1800239359681630208

              nmoraiti Nikolaos Moraitis
              adkaplan@redhat.com Adam Kaplan
              Nikolaos Moraitis Nikolaos Moraitis
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: