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

Can't install clusters with schedulable masters

    XMLWordPrintable

Details

    • Proposed
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-1482. The following is the description of the original issue:
      —
      Description of problem:

      When the cluster to be created has schedulable masters, either because the user has explicitly requested it through the API or because there are no worker nodes, the assisted-service creates the manifest openshift/50-schedulable_masters.yaml. Since https://github.com/openshift/installer/pull/6247 landed in openshift-installer during 4.12, this causes a conflict with the file manifests/cluster-scheduler-02-config.yml which is generated by the installer, and this causes installation to fail.

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

      4.12

      How reproducible:

      100%

      Steps to Reproduce:

      1. Create a compact cluster
2. Start installation

      Actual results:

      Failure to prepare the ignition files with the following error from openshift-installer:

failed to fetch dependency of \"Bootstrap Ignition Config\": failed to generate asset \"CVO Ignore\": multiple manifests for group config.openshift.io kind Scheduler namespace name cluster: manifests/cluster-scheduler-02-config.yml, openshift/50-schedulable_masters.yaml

      Expected results:

      Cluster is installed.

      Additional info:

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1482 Can't install clusters with schedulable masters

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is depended on by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2635 Ingress operator degraded during 3+1 deployment due to insufficient worker nodes

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          Web Link openshift/assisted-service#4583: MGMT-12435: Add a way to apply patches to core manifests

          Activity

            People

              fpercoco@redhat.com Flavio Percoco (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Lital Alon Lital Alon
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: