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 1318602 - preupgrade.ks is not in directory /root/preupgrade/kickstart
Summary: preupgrade.ks is not in directory /root/preupgrade/kickstart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Hracek
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On:
Blocks: 1335121
TreeView+ depends on / blocked
 
Reported: 2016-03-17 10:31 UTC by Tereza Cerna
Modified: 2016-11-04 08:56 UTC (History)
5 users (show)

Fixed In Version: preupgrade-assistant-2.1.6.post41-6.el6
Doc Type: Bug Fix
Doc Text:
The Preupgrade Assistant now generates the preupgrade.ks file to the /root/preupgrade/kickstart/ directory.
Clone Of:
Environment:
Last Closed: 2016-11-04 08:56:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2616 0 normal SHIPPED_LIVE preupgrade-assistant bug fix and enhancement update 2016-11-03 16:23:38 UTC

Description Tereza Cerna 2016-03-17 10:31:11 UTC
Kickstart file preupgrade.ks is generated by preupgrade assistant to directory /root/preupgrade. There is also new directory /root/preupgrade/kickstart with other kickstart files. It is a little confusing why preupgrade.ks file is not in kickstart directory. Can it by moved? This change would be in RHEL-5 and RHEL-6.

Reproducer:
# preupg
# preupg --migration
# ls -ld /root/preupgrade/kickstart /root/preupgrade/preupgrade.ks
drwxr-xr-x 3 root root    4096 Mar 17 05:57 /root/preupgrade/kickstart
-rw-r--r-- 1 root root 1769475 Mar 17 05:57 /root/preupgrade/preupgrade.ks

Version:
preupgrade-assistant-2.1.5-2

Comment 2 Petr Hracek 2016-04-25 10:41:47 UTC
Good point,
I don't have a problem to change it. What do you think about it?

Comment 6 Tereza Cerna 2016-06-30 10:30:39 UTC
Verified in RHEL-6:
   preupgrade-assistant-2.1.6.post41-6.el6.noarch
   preupgrade-assistant-el6toel7-0.6.49-1.el6.noarch

File preupgrade.ks was moved to directory /root/preupgrade/kickstart.

# preupg
# preupg-kickstart-generator 
The Preupgrade Assistant generates a kickstart file in '/root/preupgrade/kickstart/preupgrade.ks'.
...
# find /root/preupgrade | grep preupgrade.ks
/root/preupgrade/kickstart/preupgrade.ks
#

Comment 8 errata-xmlrpc 2016-11-04 08:56:41 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/RHBA-2016-2616.html


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