| Summary: | 6.1. Upgrading to Satellite Server 6.2 does not require an upgrade to 6.1.10 or later | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> |
| Component: | Docs Install Guide | Assignee: | Chris Roberts <chrobert> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | satellite-doc-list |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2.4 | CC: | adahms, ahumbe, bkearney, bmcelvee, chrobert, rdickens, swadeley |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://gitlab.cee.redhat.com/satellite-6-documentation/installation-guide/merge_requests/138 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-22 01:23:48 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: | |
|
Description
Mike McCune
2016-11-14 22:21:59 UTC
Created MR: https://gitlab.cee.redhat.com/satellite-6-documentation/installation-guide/merge_requests/138 I think there should be a check provided to confirm the satellite they are running is on Sat v 6.1.9 GA. This will avoid any chances of upgrading satellite from 6.1.8 or previous versions to 6.2.x. (In reply to Ashish Humbe from comment #2) > I think there should be a check provided to confirm the satellite they are > running is on Sat v 6.1.9 GA. This will avoid any chances of upgrading > satellite from 6.1.8 or previous versions to 6.2.x. As we do not know of an easy way to do that the extra steps which asks you to attempt to upgrade one last time using "katello-installer --upgrade" were added. Those are the steps "Update all packages" followed by "If you have new packages after updating" "katello-installer --upgrade". However, that step was added before 6.1.10 was released, then later updated to say it was optional by adding "If you have new packages after updating". This content is live on the Customer Portal. Closing. |