Bug 1920654 - On new Application deployment, Ansible Prehook gets executed twice
Summary: On new Application deployment, Ansible Prehook gets executed twice
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.1.z
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.1.5
Assignee: ian zhang
QA Contact: Eveline Cai
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-26 19:40 UTC by Raed Soliman
Modified: 2021-04-09 17:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-24 12:57:56 UTC
Target Upstream Version:
Embargoed:
gghezzo: rhacm-2.1.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 8854 0 None None None 2021-02-22 14:31:03 UTC
Red Hat Product Errata RHSA-2021:0980 0 None None None 2021-03-24 12:59:46 UTC

Description Raed Soliman 2021-01-26 19:40:28 UTC
Description of problem:
When trying to deploy a new application with ACM using a git subscription, the Ansible prehook gets executed twice resulting in 2 distinct Jobs being launched in Ansible Tower

Version-Release number of selected component (if applicable):
2.1.2

How reproducible:
Easily

Steps to Reproduce:
1.Create a new application with git as a repo type (I use this sample in my git for demos, can recreate with it https://github.com/raedrizk/ACMDemo.git)
2.choose main as the branch and deploy as the path and the Tower secret defined in the namespace under "Set pre and post deployment tasks"
3. Hit save and monitor the tower instance that is referenced. 
Actual results:

2 prehook Jobs will be launched


Expected results:

Only 1 Job should be launched

Additional info:

Comment 6 errata-xmlrpc 2021-03-24 12:57:56 UTC
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 (Moderate: Red Hat Advanced Cluster Management 2.1.5 security and bug fix update), 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-2021:0980


Note You need to log in before you can comment on or make changes to this bug.