Description of Problem

After updating OpenShift GitOps, some applications are showing the following error:

Unable to load data: error acquiring repo lock: failed to initialize repository resources: rpc error: code = Internal desc = Failed to fetch default: `git fetch origin --tags --force --prune` failed exit status 128: fatal: could not read Username for 'https://my.repo.com/': terminal prompts disabled

Additional Info

This issue has been documented in the following KCS:

https://access.redhat.com/solutions/7104257

Problem Reproduction

• Create an application with a repo secret that contains the project key-value pair in OpenShift GitOps 1.14 or higher.

or

• Update to OpenShift GitOps 1.14 or higher having appllications with a repo secret that contains the project key-value pair.

Reproducibility

Always

Prerequisites/Environment

• Red Hat OpenShift GitOps operator 1.14 or higher

Steps to Reproduce

Same as in problem reproduction field.

Expected Results

Having the possibility of using project-scoped credentials.

Actual Results

Only global credentials can be used.

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

This is a known issue that was introduced in [ArgoCD project-scoped repository credential improvements](https://github.com/argoproj/argo-cd/pull/18388) pull request.

This issue was reported in upstream ArgoCD in ArgoCD #19585(https://github.com/argoproj/argo-cd/issues/19585).

Workaround (If Possible)

Remove the `project` key-value pair from the repository secret.

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.