-
Bug
-
Resolution: Done
-
Critical
-
1.16.0
-
None
-
None
Description of Problem
argocd-repo-server pod goes to CrashLoopBackOff as cmp container fails to start
cmp container log:
/var/run/argocd/argocd-cmp-server: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
Events:
$ oc events --for pod/argocd-repo-server-75f4bffbd8-2plmr -n argocd LAST SEEN TYPE REASON OBJECT MESSAGE 11m Normal Scheduled Pod/argocd-repo-server-75f4bffbd8-2plmr Successfully assigned argocd/argocd-repo-server-75f4bffbd8-2plmr to test-417-4-w8dpf-worker-0-t47lc 11m Normal AddedInterface Pod/argocd-repo-server-75f4bffbd8-2plmr Add eth0 [10.129.2.143/23] from ovn-kubernetes 11m Normal Pulling Pod/argocd-repo-server-75f4bffbd8-2plmr Pulling image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:e599550a6c98818442ccdfd33872c29a0e73c1f58467b406c385ccd5e2b632ff" 11m Normal Pulled Pod/argocd-repo-server-75f4bffbd8-2plmr Successfully pulled image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:e599550a6c98818442ccdfd33872c29a0e73c1f58467b406c385ccd5e2b632ff" in 338ms (338ms including waiting). Image size: 642052084 bytes. 11m Normal Created Pod/argocd-repo-server-75f4bffbd8-2plmr Created container copyutil 11m Normal Started Pod/argocd-repo-server-75f4bffbd8-2plmr Started container copyutil 11m Normal Created Pod/argocd-repo-server-75f4bffbd8-2plmr Created container argocd-repo-server 11m Normal Pulled Pod/argocd-repo-server-75f4bffbd8-2plmr Successfully pulled image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:e599550a6c98818442ccdfd33872c29a0e73c1f58467b406c385ccd5e2b632ff" in 405ms (405ms including waiting). Image size: 642052084 bytes. 11m Normal Pulling Pod/argocd-repo-server-75f4bffbd8-2plmr Pulling image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:e599550a6c98818442ccdfd33872c29a0e73c1f58467b406c385ccd5e2b632ff" 11m Normal Started Pod/argocd-repo-server-75f4bffbd8-2plmr Started container argocd-repo-server 11m Normal Pulled Pod/argocd-repo-server-75f4bffbd8-2plmr Successfully pulled image "busybox" in 871ms (871ms including waiting). Image size: 4517479 bytes. 11m Normal Pulled Pod/argocd-repo-server-75f4bffbd8-2plmr Successfully pulled image "busybox" in 209ms (209ms including waiting). Image size: 4517479 bytes. 11m (x3 over 11m) Normal Pulling Pod/argocd-repo-server-75f4bffbd8-2plmr Pulling image "busybox" 11m (x3 over 11m) Normal Created Pod/argocd-repo-server-75f4bffbd8-2plmr Created container cmp 11m (x3 over 11m) Normal Started Pod/argocd-repo-server-75f4bffbd8-2plmr Started container cmp 11m Normal Pulled Pod/argocd-repo-server-75f4bffbd8-2plmr Successfully pulled image "busybox" in 211ms (211ms including waiting). Image size: 4517479 bytes. 93s (x48 over 11m) Warning BackOff Pod/argocd-repo-server-75f4bffbd8-2plmr Back-off restarting failed container cmp in pod argocd-repo-server-75f4bffbd8-2plmr_argocd(16a8a890-9902-4352-998c-39048901dacd)
Problem Reproduction
- Install 1.16 RC
- Run the below test
$ kubectl kuttl test tests/parallel/ --test 1-070_validate_config_management_plugin --config tests/sequential/kuttl-test.yaml
Reproducibility
- Always
Prerequisites/Environment
- Any openshift cluster
- 1.16.0 RC
Steps to Reproduce
- See Problem Reproduction
Expected Results
- argocd-repo-server pod is up and running
Actual Results
- argocd-repo-server pod goes to CrashLoopBackOff upon enabling config management plugin
Problem Analysis
- argocd-cmp-server can be built with CGO_ENABLED=0 since that does not use any crypto
Root Cause
- Since 1.16 is made FIPS compliant, images are built with CGO_ENABLED=1
Workaround (If Possible)
- <Are there any workarounds we can provide to the customers?>
Fix Approaches
- Build argocd-cmp-server with CGO_ENABLED=0
Acceptance Criteria
- Enabling config management plugin should work
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.
