Fix was merged May 10.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:4956
When deploying an application with AnsibleJobs multiple times with different namespaces, the topology view may display all the AnsibleJobs rather than just the one within the specific namespace. This behavior can occur because the topology view typically shows all the deployed AnsibleJobs across namespaces by default. It provides a comprehensive overview of the infrastructure and applications. https://www.mykfcexperience.website/
since the problem is very serious in this repost should be resolve in a in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory . If the solution does not work for you, open a new bug report. https://www.mymilestonecard.biz/
Here information is provided by you is very nice thank you for this. https://www.myjdfaccount.net/
It sounds like you're experiencing an issue with the visualization of Ansible jobs in a multi-namespace deployment. The topology should ideally show only the Ansible jobs relevant to a specific namespace, but you're seeing all Ansible jobs from all namespaces. This could be due to how your Ansible playbooks and job configurations are structured. Here are a few things you can check and adjust to ensure that the visualization shows only the relevant Ansible jobs for each namespace: Namespace-Scoped Ansible Jobs: Make sure that your Ansible jobs are being scoped to the specific namespace they should be running in. This might involve dynamically setting variables or parameters that distinguish between namespaces. For example, you could use namespace-specific variables in your playbooks. https://www.paybyplatema.ltd/ Dynamic Inventory: If you're using dynamic inventory, ensure that it's configured to provide information about resources only within the specific namespace. This way, when Ansible runs, it will only see resources within the target namespace. Playbook Organization: Organize your playbooks and job configurations in a way that they are grouped by namespace. Each namespace should have its own set of playbooks and associated files. This will make it easier to isolate the Ansible jobs by namespace. Configuration Management: Ensure that your Ansible roles and playbooks are designed to handle multiple namespaces gracefully. They should use variables and parameters that allow them to adapt to different namespaces while keeping configurations separate. Check Ansible Configuration: Review your Ansible configuration files to make sure there aren't any global settings that could be causing all Ansible jobs to be visualized together. Configuration settings should be specific to each namespace. Ansible Tower/AWX: If you're using Ansible Tower or its open-source version AWX, make sure that you're configuring inventory, templates, and job templates appropriately for each namespace. This might involve using different inventory sources or templates for each namespace. Testing: Test your deployment with a single namespace to see if the visualization behaves as expected. This will help you narrow down whether the issue is with the way Ansible is set up or if it's related to the multi-namespace environment. By addressing these areas, you should be able to ensure that the visualization only displays Ansible jobs relevant to each specific namespace in your multi-namespace deployment.