-
Bug
-
Resolution: Duplicate
-
Undefined
-
4.15
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
No
-
None
-
None
-
None
-
CNF RAN Sprint 248, CNF RAN Sprint 249, CNF RAN Sprint 250, CNF RAN Sprint 251
-
4
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Deployment of OCP SNO spoke with Telco DU profile via ZTP fails with the
following error in the gitops app:
oc get apps -n openshift-gitops clusters
wait for gitops clusters and policies apps to be in sync (1 retries left).
kind: SiteConfig
message: The Kubernetes API could not find ran.openshift.io/SiteConfig for
requested resource helix55/site-plan-helix55. Make sure the "SiteConfig"
CRD is installed on the destination cluster.
name: site-plan-helix55
The root cause appeared to be a filename collision between an default manifest
and a custom manifest in the ZTP siteconfig. In this case it was the
siteconfig/sno-extra-manifest/enable-cgroups-v1.yaml manifest. Not sure if the
issue is with this specific manifest only (it was added as a default manifest
in recent ztp-site-generate container builds)
Removing the local file allows deployment to proceed. The error message is
confusing and doesn't indicate the real cause of the failure; the manifest
filename collision.
Version-Release number of selected component (if applicable):
OCP 4.15.0-rc.3 gitops-rhel8-operator/images/v1.10.1-3 ztp-site-generator:v4.15.0-29
How reproducible:
Always
Steps to Reproduce:
1. Deploy SNO DU node with conflicting manifest filename 2. Observe gitops app status 3.
Actual results:
Error above is shown and install does not proceed
Expected results:
Error message should indicate the case for the failure as a manifest filename collision.
Additional info:
- duplicates
-
OCPBUGS-25820 Siteconfig plugin outputs Siteconfig content when an error
-
- Closed
-
-
OCPBUGS-30886 [4.14] Siteconfig plugin outputs Siteconfig content when an error
-
- Closed
-
- links to