Description of Problem

• Application created from agent cluster does not work as expected sometimes in of autonomous mode especially when CreateNamespace is set to true. Even with the ns created and auto sync enabled, the app remains in out of sync with a message "waiting for healthy state of /Namespace/<namespace name>"

Additional Info

• Refer tot the attached screenshots and app yamls at different stage

Problem Reproduction

• Setup an autonomous agent and create an application from agent cluster

Reproducibility

• Intermittent

Prerequisites/Environment

• <OpenShift, managed service (e.g., ROSA, ARO), operators, layered product, and other software versions, build details>

Steps to Reproduce

• Enable agent in autonomous mode 
• Create an application with CreateNamespace set to true
• Observe the app sync

Expected Results

• App syncs successfully

Actual Results

• App does not show up in UI at first even though the application yam is found in hub cluster
• Once the application appears in UI. the sync does not happen until 'Sync' is clicked in UI, see app-sync.txt for app yamls before and after sync

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.