Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-15030

new known issue for ACM 2.12 release note

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • ACM 2.12.0
    • Documentation
    • None
    • False
    • None
    • False
    • Hide

      Provide the required acceptance criteria using this template.
      * ...
      Show
      Provide the required acceptance criteria using this template. * ...
    • None

      Create an informative issue (See each section, incomplete templates/issues won't be triaged)

      Using the current documentation as a model, please complete the issue template. 

      Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

      Prerequisite: Start with what we have

      Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

       - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

       - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

      Describe the changes in the doc and link to your dev story

      Provide info for the following steps:

      1. - [X] Mandatory Add the required version to the Fix version/s field.

      ACM 2.12

      2. - [X] Mandatory Choose the type of documentation change.

            - [X] New topic in an existing section or new section

       

      Add a new known issue in ACM 2.12 release note

      Known issue:

      After triggering an prehook/posthook Ansible Job from ACM, the Ansible jobs are completed as expected. But when viewing the ansible job details, the Ansible job link is not redirected to the Ansible tower UI. The issue is observed in the AAP operator (Ansible Automation Platform) V2.5 because the Ansible job link is not reported correctly by the AAP operator.

       

      Workaround:  The Anisble Job ID is correct though the job link is wrong. Users can get the job ID from the job link and then manually log into the Ansible tower UI to get the Ansible job details

       

            - [ ] Update to an existing topic

      3. - [ ] Mandatory for GA content:
                  
             - [ ] Add steps and/or other important conceptual information here: 
             
                  
             - [ ] Add Required access level for the user to complete the task here:
             

             - [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
           
           
             - [ ] Add link to dev story here:

      4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

              Unassigned Unassigned
              xiangli@redhat.com Xiangjing Li
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: