Description of Problem

• Upgrading to OpenShift GitOps 1.18 appears to trigger an issue where viewing an Application in the Argo CD web console can trigger a refresh. This is notable even when the Argo CD instance has `timeout.reconciliation {.jitter}` set to 0s, which should otherwise stop the refresh behavior barring other circumstances.

Problem Reproduction

• Creating an Argo CD instance on 1.18.x and checking the Argo CD web console should demonstrate the issue. Disabling the standard reconciliation should make the behavior easier to witness

Reproducibility

• Always

Prerequisites/Environment

• OpenShift 4.19.14
• OpenShift GitOps 1.18.1

Steps to Reproduce

• Create an instance of Argo CD on OpenShift GitOps 1.18
• (Optional) Disable the standard reconciliation loop using the `timeout.reconciliation` parameter
• Create and view a sample Application from the web UI

Expected Results

• Application does not update due to UI, merely updating in its existing cycle

Actual Results

• Application is updated due to user viewing it's UI page

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.