Bug 1656168 - ansible tower items are not listed when part of service bundles
Summary: ansible tower items are not listed when part of service bundles
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.5
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.9.6
Assignee: Tina Fitzgerald
QA Contact: Nandini Chandra
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1653812
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-04 21:19 UTC by Satoe Imaishi
Modified: 2022-07-09 10:15 UTC (History)
11 users (show)

Fixed In Version: 5.9.6.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1653812
Environment:
Last Closed: 2018-12-13 15:16:05 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1652883 0 medium CLOSED ancestry not set for ansible items part of a service bundle 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1654165 0 high CLOSED Service not showing VMs belong to 2022-03-13 16:14:57 UTC
Red Hat Product Errata RHSA-2018:3816 0 None None None 2018-12-13 15:16:07 UTC

Comment 2 Nandini Chandra 2018-12-07 19:43:46 UTC 
Verified in 5.9.6.5
Comment 3 Nandini Chandra 2018-12-10 21:58:13 UTC 
This issue is not specific to Ansible .

Steps to reproduce:
1)Create a service bundle b1 with two service items that create VMs
2)Create a service bundle b2 with two service items that create VMs
3)Create a bundle b3 with the bundles created in steps 1 and 2.

Order bundle b3.

Before fix:
Bundle b3 would only list whatever VMs were created through the first service that got ordered

After fix:
Bundle b3 lists all the VMs that were created through all its services
Comment 5 errata-xmlrpc 2018-12-13 15:16:05 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, 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-2018:3816
Note You need to log in before you can comment on or make changes to this bug.