Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1582266

Summary: [Satellite 6] satellite-6.3-tools-upgrade-6.3.0-1.el7sat.noarch.rpm is enabling the incorrect repos on "RHEL Workstation" while upgrading the satellite clients
Product: Red Hat Satellite Reporter: Raviraj Lavande <rlavande>
Component: PackagingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: urgent Docs Contact:
Priority: high    
Version: 6.3.1CC: akaiser, bkearney, cdonnell, mmccune, rloring, zhunting
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-26 19:29:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
UI to enable / disable repositories none

Description Raviraj Lavande 2018-05-24 16:48:13 UTC
Created attachment 1441151 [details]
Error description

Description of problem:

While upgrading the satellite clients (Satellite 6.3) using package name "satellite-6.3-tools-upgrade". 

The rpm "satellite-6.3-tools-upgrade-6.3.0-1.el7sat.noarch.rpm" is enabling the "server-satellite-tools 6.3" repo on the RHEL Workstation (satellite clients).

# rpm -qp --scripts satellite-6.3-tools-upgrade-6.3.0-1.el7sat.noarch.rpm

# Disable the 6.2 satellite-tools repo and enable 6.3
subscription-manager repos --disable rhel-*-server-satellite-tools-6.2-rpms  >/dev/null 2>&1
subscription-manager repos --enable rhel-*-server-satellite-tools-6.3-rpms  >/dev/null 2>&1
exit 0
  
Version-Release number of selected component (if applicable):

Satellite 6.3
RHEL Workstation 7.5

How reproducible:

Always

Steps to Reproduce:
1. On a RHEL Workstation machine Download the rpm. 
2. 3. run # rpm -qp --scripts satellite-6.3-tools-upgrade-6.3.0-1.el7sat.noarch.rpm
 
Actual results:

On RHEL Workstation It enables "server-satellite tools repo".

Expected results:

It should not enable "server-satellite tools repos

Additional info:

Generating issues for client upgrade process.

Comment 3 Raviraj Lavande 2018-05-29 14:07:45 UTC
Hello,

May I know, when will this get fixed (ETA)? because customer needs this ASAP, their patching and client upgrade process is stopped.

Thank You.

Comment 4 Mike McCune 2018-05-29 17:35:25 UTC
On 6.3, customers can use the UI to to bulk enable the Satellite 6.3 Workstation which is a superior method to the RPM installation routine.

To utilize this go to:

1) Hosts -> Content Hosts -> Search for all Red Hat Enterprise Linux 7 Workstation hosts

2) Click 'select all' checkbox on the upper left, click the 'select all hosts' to ensure all hosts on the Satellite matching this criteria are selected

3) Select Action on the right: Manage Repository Sets

4) Filter 'Workstation' in filter box

5) Override to Enabled

After the bulk operation is complete, the next time the clients run yum or subscription-manager issues a refresh (every ~4h hours), the clients will then have the 6.3 Workstation Tools enabled.

They can also do this to *disable* the 6.2 Tools repo as well if desired.

See attached screenshot. This will be the preferred method for updating repository configurations in Satellite going forward and the satellite-tools-upgrade will be deprecated.

Comment 5 Mike McCune 2018-05-29 17:35:52 UTC
Created attachment 1445476 [details]
UI to enable / disable repositories

Comment 7 Rich Loring 2018-05-29 19:39:23 UTC
Mike,

I agree that using the bulk action would be a superior way. However the state of the satellite has repo syncs and other processes stepping on each other causing failures of all sorts of automated actions. This along with the inability of the bulk action to tell me what systems have actually received the and which ones have failed the update via FQDN and not registration number makes it more of a less superior way to do this. This makes it a catch 22 for me as I have a case open about the syncs and bulk action failures stepping on each other and they are telling me that upgrading to satellite 6.3 will improve the performance. So my best solution is to use the satellite-tools-upgrade with puppet or ansible this way I know which systems fail and can at least be able to address them.

Comment 11 Bryan Kearney 2018-11-26 19:29:06 UTC
Satellite 6.2 has reached maintenance support phase 2 [1]. Since this bug has a workaround, it does not quality for inclusion in a 6.2.z release during this support phase. I am therefore closing this bug out.


[1] https://access.redhat.com/support/policy/updates/satellite