Description of Problem

• GitOps v1.16, and post that connections to their gitlab repository is failing. The strange part is downgrading the GitOps operator v1.15.1 fixes the connection issue to the same repositories.
• Customer is using FIPS cluster

Additional Info

         logs

• time="2025-04-17T17:46:08Z" level=error msg="finished unary call with code Unknown" error="error testing repository connectivity: unable to ls-remote HEAD on repository: failed to list refs: unexpected client error: unexpected requesting \"https://<>gitlab-repo-url>.git/info/refs?service=git-upload-pack\" status code: 302" grpc.code=Unknown grpc.method=TestRepository grpc.service=repository.RepoServerService grpc.start_time="2025-04-17T17:46:08Z" grpc.time_ms=214.225 span.kind=server system=grpc 

Problem Reproduction

• install gitops on FIPS openshift cluster
• add gitlab repo using GUI or CLI
• check logs of repo server

Reproducibility

 - not able to reproduce

Prerequisites/Environment

• FIPS OpenShift cluster

Expected Results

• Argocd should be able to connect to gitlab repo successfully 

Actual Results

• failing to connect

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.