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 1574183 - Unable to upgrade content host from 6.2 to 6.3 using Satellite 6.3 UI
Summary: Unable to upgrade content host from 6.2 to 6.3 using Satellite 6.3 UI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.2.14
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-02 18:31 UTC by sthirugn@redhat.com
Modified: 2018-11-26 19:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-26 19:32:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/var/log/messages from client (4.12 KB, text/plain)
2018-05-02 18:34 UTC, sthirugn@redhat.com
no flags Details

Description sthirugn@redhat.com 2018-05-02 18:31:20 UTC
Description of problem:
Unable to upgrade content host from 6.2 to 6.3 using Satellite 6.3 UI

Version-Release number of selected component (if applicable):
satellite - satellite-6.3.1-3.el7sat.noarch
Client (6.2.z):
katello-host-tools-3.0.2-1.el7sat.noarch
katello-agent-3.0.2-1.el7sat.noarch
katello-host-tools-fact-plugin-3.0.2-1.el7sat.noarch
pulp-rpm-handlers-2.8.7.16-1.el7sat.noarch
python-pulp-common-2.8.7.18-1.el7sat.noarch
python-pulp-rpm-common-2.8.7.16-1.el7sat.noarch
python-pulp-agent-lib-2.8.7.18-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Upgrade Satellite (and capsules) from 6.2.z to 6.3. Clients still use 6.2 Satellite Tools.
2. Client upgrade documentation https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#upgrading_clients states to install `satellite-6.3-tools-upgrade` package and update `katello-agent` package from Satellite UI -> Hosts  -> Content Hosts -> Select Action -> Manage Packages

Actual results:
After the above-mentioned step is performed, the clients started throwing an error (see attachment) in /var/log/messages and the package updates did not happen.

Expected results:
1. Either the package management from Satellite 6.3 should work on the 6.2 tools Client (or)
2. The doc should be updated to remove this method from the recommended steps. This would leave the user with Remote Execution or manual pull from the client to upgrade to 6.3

Additional info:

Comment 1 sthirugn@redhat.com 2018-05-02 18:34:51 UTC
Created attachment 1430236 [details]
/var/log/messages from client

Comment 3 Bryan Kearney 2018-11-26 19:32:08 UTC
Satellite 6.2 has reached maintenance support phase 2 [1]. This bug 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


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