Description of Problem

Argocd login failed on the 2.14.x release but was working fine on previous versions. We have to explicitly pass --skip-test-tls for the login to work:

Additional Info

Upstream Bug: https://github.com/argoproj/argo-cd/issues/21764

Reproducibility

• Always

Prerequisites/Environment

• Openshift-gitops (any version)
• OCP 4.x

Steps to Reproduce

•  Install the latest binary v2.14.5

https://developers.redhat.com/content-gateway/rest/browse/pub/openshift-v4/clients/openshift-gitops/latest/

• Try to login to argocd

Expected Results

argocd login --username admin --password $admin_passwd <gitops-route> 
openshift-gitops-server-openshift-gitops.apps.xyz
...
'admin:login' logged in successfully
Context 'openshift-gitops-server-openshift-gitops.apps.xyz' updated

Actual Results

argocd login --username admin --password $admin_passwd <gitops-route> FATA[0030] context deadline exceeded  

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)

_{We have to explicitly pass "--skip-test-tls" for the login to work:}

argocd login --username admin --password $admin_passwd <gitops-route> --skip-test-tls
...
'admin:login' logged in successfully
Context 'openshift-gitops-server-openshift-gitops.apps.xyz' updated

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.