Bug 1427901 - Rebase subscription-manager component to the latest upstream branch for RHEL 7.4
Summary: Rebase subscription-manager component to the latest upstream branch for RHEL 7.4
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
Depends On:
TreeView+ depends on / blocked
Reported: 2017-03-01 13:33 UTC by John Sefler
Modified: 2017-08-01 19:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-01 19:21:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2083 normal SHIPPED_LIVE python-rhsm and subscription-manager bug fix and enhancement update 2017-08-01 18:14:19 UTC

Description John Sefler 2017-03-01 13:33:40 UTC
Rebase rhel component 'subscription-manager' to the latest upstream version 1.19.X for RHEL7.4

From RHEL7.4 schedule https://pp.engineering.redhat.com/pp/data/rhel/rhel-7-4-0/
Devel: Errata submitted to QE for new and rebased packages, glibc and gcc
Errata filed including all FutureFeature bugs for these packages
Due Date:  Wed 2017-03-15

Comment 3 Shwetha Kallesh 2017-04-13 15:02:37 UTC
Marking verified!!

The latest nightly RHEL7.4 composes include subscription-manager-1.19.7-1 (the latest version)

Errata RHBA-2017:27061-02 RHEL-7.4 has been filed
Errata provides latest subscription-manager build subscription-manager-.19.7-1.el7

All functional issues regarding subscription-manager-1.19.7-1 on rhel7.4 are being opened under separate bugzillas.

Comment 4 errata-xmlrpc 2017-08-01 19:21:47 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.


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