Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-26277

MCE 2.10 installation fails on xKS due to CRD deployment conflict

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • MCE 2.10.0
    • MCE 2.10.0
    • Installer
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Installer Sprint 2025-72
    • Critical
    • Approved
    • None

      Description of problem:

      We noticed that CRDs from all components are being applied during MCE startup, regardless of whether the components are enabled or not. This behavior could cause issues for Sylva, as it modifies resources such as CAPI even when that component is disabled.

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

      MCE 2.10.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. Setup xKS environment.
      2. Install MCE 2.10 via Helm Chart
      3. Verify that the operator deploys CRDs.

      Actual results:

      The MCE operator deploys CAPI CRDs onto the cluster, regardless of configuration.

      Expected results:

      The MCE operator should skip creating CAPI CRDs unless the CAPI component is explicitly enabled.

      Additional info:

      -------------------------------------------------------------------------------------------------------
      QE Hand Off Template (fill out when moving to Review) 11/17/25:

      Summary of the Work:
      What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
      e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

      Key Areas to Verify:

      1. What functionality should QE focus on? List what was tested or what is most important to validate.
      2. Ensure the new validation messages appear for required fields
      3. Confirm the workflow still completes as expected after validation fixes
      4. Any edge cases or high-risk areas touched by the change

      Fix or Feature Availability:
      When will this be available in a build?
      Code merged on: YYYY-MM-DD
      Expected downstream build tag (if known): example-build-tag
      (Optional) Related PR(s): Link

              dbennett@redhat.com Disaiah Bennett
              dbennett@redhat.com Disaiah Bennett
              Riccardo Piccoli Riccardo Piccoli
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: