Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688913 - [RFE] Ansible Tower upgrades via Satellite 6
Summary: [RFE] Ansible Tower upgrades via Satellite 6
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Ansible
Version: 6.4
Hardware: x86_64
OS: Linux
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-14 17:42 UTC by Ash Westbrook
Modified: 2019-03-16 03:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Ash Westbrook 2019-03-14 17:42:45 UTC
Feature Idea
Push tower update rpms to the Red Hat CDN, so that the upgrade experience is consistent with the rest of Red Hat Products, as well as meeting the mandate for a centralized update process. This would allow for customers to configure via their Satellite Server and prevent the need for a local repository.

Installer (and tower packages)

Red Hat Customers currently, are able to access and download all product packages except for Ansible Tower via the CDN. Many update all of their systems via Satellite, so that their networks can be isolated, but still have a centralized update process (no local repositories). Because Tower is not packaged this way, it leads to upgrade failures and inconsistency with the rest of the Red Hat User Experience. For some of our Government Customers, they have mandates to isolate and limit the use of non-standard processes. In their minds, if the packages come directly from Red Hat (via the CDN) they have a guarantee that the software is secure, has been quality checked and will be regularly updated. Pushing the tower tarball to the CDN should allow for them to be able to access this and upgrade their Tower systems successfully, without issue, whether via CDN directly or via Satellite.

Currently, customer are told to exclude ansible tower from any updates using yum.conf restrictions, which is not one of our suggested or recommended actions.

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