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

Upgrading from ACM 2.13 to 2.14 argocd sync fails with "unauthorized change to /cpuArchitecture"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • ACM 2.14.5
    • ACM 2.15.1
    • SiteConfig Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Bug Fix: ClusterInstance updates fail after ACM upgrade with unauthorized change to /cpuArchitecture
      After upgrading from ACM 2.13 to 2.15, the webhook could reject ClusterInstance updates for clusters provisioned before the upgrade because the newly introduced cpuArchitecture field was treated as an unauthorized modification. The webhook now allows this field to be set for the first time on existing clusters.
      Show
      Bug Fix: ClusterInstance updates fail after ACM upgrade with unauthorized change to /cpuArchitecture After upgrading from ACM 2.13 to 2.15, the webhook could reject ClusterInstance updates for clusters provisioned before the upgrade because the newly introduced cpuArchitecture field was treated as an unauthorized modification. The webhook now allows this field to be set for the first time on existing clusters.
    • contract-priority
    • Important
    • None

      After upgrading ACM from 2.13 to 2.15.1 and OCP version from 4.16 to 4.18, a customer is observing one error for a few clusters provisioned using clusterinstance:

       

      2026-02-05T14:21:41.674988918Z 2026-02-05T14:21:41Z     INFO    clusterinstance-webhook Spec change permission level: only base field changes allowed   {"name": "mno-1", "namespace": "mno-1", "resourceVersion": "70288232"}
2026-02-05T14:21:41.678080112Z 2026-02-05T14:21:41Z     ERROR   clusterinstance-webhook Invalid spec changes detected   {"name": "mno-2", "namespace": "mno-2", "resourceVersion": "70288232", "error": "detected unauthorized
 node modifications: [node master0: unauthorized change to /cpuArchitecture node master1: unauthorized change to /cpuArchitecture node master2: unauthorized change to /cpuArchitecture node worker0: unauthorized change to /cpuArchitect
ure]"}

       
      Comparing the clusterinstance CR created on the ACM hub with the CR from the git source we didnt find any discrepancies. Also the argocd app is in sync state which also means that both the CRs source and destination are identical.

      Then why is this trying to modify something?

              sakhoury@redhat.com Sharat Akhoury
              rh-ee-fpiccion Flavio Piccioni
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: