Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1691381 - Enable the ansible-2.8 repository for Satellite 6.6
Summary: Enable the ansible-2.8 repository for Satellite 6.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Amit Upadhye
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-21 14:07 UTC by Mike McCune
Modified: 2019-10-22 19:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:47:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26598 0 High Closed Enable the ansible-2.8 repository for Satellite 6.6 2020-11-24 14:19:48 UTC

Description Mike McCune 2019-03-21 14:07:01 UTC 
We are moving to Ansible 2.8 for Satellite 6.6 and need to update the logic in Foreman Maintain to disable the older 2.6 repo and enable 2.8.

This does mean we may need special logic to handle only doing this for Satellite 6.6 and leave 6.5 and prior versions on Ansible 2.6.

See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1684573
Comment 4 Bryan Kearney 2019-04-24 14:02:39 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26598 has been resolved.
Comment 7 Kavita 2019-06-24 12:53:38 UTC 
 Available in foreman-maintain version >= 0.4.0 so moving to ON_QA
Comment 8 Kavita 2019-06-24 12:54:17 UTC 
(In reply to Kavita from comment #7)
>  Available in foreman-maintain version >= *0.4.2 so moving to ON_QA
Comment 9 Nikhil Kathole 2019-06-24 13:03:20 UTC 
VERIFIED

Version tested:

# rpm -qa | grep maintain
satellite-maintain-0.0.1-1.el7sat.noarch
rubygem-foreman_maintain-0.4.3-1.el7sat.noarch


D, [2019-06-24 14:56:28+0200 #28336] DEBUG -- : Running command subscription-manager repos --enable=rhel-7-server-rpms --enable=rhel-server-rhscl-7-rpms --enable=rhel-7-server-satellite-6.6-rpms --enable=rhel-7-server-satellite-tools-6.6-rpms --enable=rhel-7-server-satellite-maintenance-6-rpms --enable=rhel-7-server-ansible-2.8-rpms with stdin nil

For beta,

D, [2019-06-24 14:58:48+0200 #28825] DEBUG -- : Running command subscription-manager repos --enable=rhel-7-server-rpms --enable=rhel-server-rhscl-7-rpms --enable=rhel-server-7-satellite-6-beta-rpms --enable=rhel-7-server-satellite-tools-6-beta-rpms --enable=rhel-7-server-satellite-maintenance-6-beta-rpms --enable=rhel-7-server-ansible-2.8-rpms with stdin nil
Comment 10 Bryan Kearney 2019-10-22 19:47:30 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.