RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1253680 - Preupgrade-assistant doesn't inform what should be updated in kickstart
Summary: Preupgrade-assistant doesn't inform what should be updated in kickstart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Hracek
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-14 12:47 UTC by Petr Hracek
Modified: 2015-11-20 01:41 UTC (History)
8 users (show)

Fixed In Version: preupgrade-assistant-2.1.0-6.el6
Doc Type: Bug Fix
Doc Text:
This bug fix contains a number of modifications to the preupgrade kickstart. Previously, the script did not receive warning to which components needed an upgrade before the kickstart could be implemented, and there was no warning telling the user to use the file as a reference and not to be used directly. These upgrades are implemented in this bug fix.
Clone Of:
Environment:
Last Closed: 2015-11-20 01:41:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:2497 0 normal SHIPPED_LIVE preupgrade-assistant enhancement update 2015-11-20 06:41:27 UTC

Description Petr Hracek 2015-08-14 12:47:57 UTC
Description of problem:
Nowadays preupgrade-assistant generates a kickstart with the help of contents. 
Unfortunately on command line is mentioned only a path to kickstart file without information whether kickstart is prepared for RHEL 7 installation directly.

Report from `preupg` should be enhanced so that sections like users, repositories, packages and partitioning has to be properly updated before any RHEL-7 installation.
Also information that kickstart is only a draft and can not or should not be used directly for RHEL-7 installation before any modification.

Also hint for subscription manager should be mentioned in an output.

Kickstart log file should have a reference what to do after a RHEL-7 installation. This is not handled yet.

This bugzila should covered all these issues.

NOTE: Text has to be reviewed by documentation team. Admins and users will modify kickstart file and misunderstanding can cause a lot of problems in future.

Comment 11 errata-xmlrpc 2015-11-20 01:41:53 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.

https://rhn.redhat.com/errata/RHEA-2015-2497.html


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