-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
GitOps Tangerine Sprint 19, GitOps Tangerine Sprint 20, GitOps Tangerine Sprint 21, GitOps Tangerine Sprint 22, GitOps Tangerine Sprint 23, GitOps Tangerine Sprint 24, GitOps Tangerine Sprint 25, GitOps Tangerine Sprint 26
Description of Problem
While validating https://issues.redhat.com/browse/GITOPS-6707 we hit an issue with secret not being created
Secret "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiiiing-cluster" is invalid: metadata.labels: Invalid value: "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiiiing-cluster": must be no more than 63 characters
By restricting the length of argocd instance name to 57 chars, `-cluster` secret gets created but gets stuck while creating the initial password for redis
Secret "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing-redis-initial-password" is invalid: metadata.labels: Invalid value: "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing-redis-initial-password": must be no more than 63 characters
Operator pod logs:
2025-07-23T16:55:43Z INFO controller_argocd Creating Secret 'kuttl-test-relaxed-wren/argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing-redis-initial-password' 2025-07-23T16:55:43Z ERROR Reconciler error {"controller": "argocd", "controllerGroup": "argoproj.io", "controllerKind": "ArgoCD", "ArgoCD": {"name":"argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing","namespace":"kuttl-test-relaxed-wren"}, "namespace": "kuttl-test-relaxed-wren", "name": "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing", "reconcileID": "8c0db139-7f50-4412-ab8f-02f97d466cf1", "error": "Secret \"argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing-redis-initial-password\" is invalid: metadata.labels: Invalid value: \"argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiing-redis-initial-password\": must be no more than 63 characters"} sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler /cachi2/output/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.1/pkg/internal/controller/controller.go:316 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem /cachi2/output/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.1/pkg/internal/controller/controller.go:263 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2 /cachi2/output/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.1/pkg/internal/controller/controller.go:224 2025-07-23T16:55:54Z INFO controller_gitopsservice Reconciling GitopsService {"Request.Namespace": "", "Request.Name": "openshift-gitops"} 2025-07-23T16:55:54Z INFO controller_gitopsservice No ResourceQuota set for namespace {"Request.Namespace": "", "Request.Name": "openshift-gitops", "Name": "openshift-gitops"} 2025-07-23T16:55:54Z INFO controller_gitopsservice Reconciling ArgoCD {"Request.Namespace": "", "Request.Name": "openshift-gitops", "Namespace": "openshift-gitops", "Name": "openshift-gitops"} 2025-07-23T16:55:54Z INFO controller_gitopsservice Reconciling plugin service {"Request.Namespace": "", "Request.Name": "openshift-gitops", "Namespace": "openshift-gitops", "Name": "gitops-plugin"} 2025-07-23T16:55:54Z INFO controller_gitopsservice Reconciling plugin deployment {"Request.Namespace": "", "Request.Name": "openshift-gitops", "Namespace": "openshift-gitops", "Name": "gitops-plugin"}
Additional Info
- <Any additional info such as logs, must-gather outputs, etc.>
Problem Reproduction
- See Steps to Reproduce
Reproducibility
- Always
Prerequisites/Environment
- GitOps 1.17.0 build on a regular OCP
Steps to Reproduce
Expected Results
- The test should pass
Actual Results
- The test fails because of below error
Secret "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiiiing-cluster" is invalid: metadata.labels: Invalid value: "argocd-long-name-for-route-testiiiiiiiiiiiiiiiiiiiiiiiing-cluster": must be no more than 63 characters
$ oc get routes -n kuttl-test-strong-teal No resources found in kuttl-test-strong-teal namespace.
Problem Analysis
- <Completed by engineering team as part of the triage/refinement process>
Root Cause
- <What is the root cause of the problem? Or, why is it not a bug?>
Workaround (If Possible)
- <Are there any workarounds we can provide to the customers?>
Fix Approaches
- <If we decide to fix this bug, how will we do it?>
Acceptance Criteria
- ...
Definition of Done
- Code Complete:
- All code has been written, reviewed, and approved.
- Tested:
- Unit tests have been written and passed.
- Ensure code coverage is not reduced with the changes.
- Integration tests have been automated.
- System tests have been conducted, and all critical bugs have been fixed.
- Tested and merged on OpenShift either upstream or downstream on a local build.
- Documentation:
- User documentation or release notes have been written (if applicable).
- Build:
- Code has been successfully built and integrated into the main repository / project.
- Midstream changes (if applicable) are done, reviewed, approved and merged.
- Review:
- Code has been peer-reviewed and meets coding standards.
- All acceptance criteria defined in the user story have been met.
- Tested by reviewer on OpenShift.
- Deployment:
- The feature has been deployed on OpenShift cluster for testing.
- is cloned by
-
GITOPS-7663 1.17.0 RC0 - Host name error for ApplicationSet Webhook Server route
-
- Closed
-