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 1244330 - backport support for product.img and updates.img creation from 7.2
Summary: backport support for product.img and updates.img creation from 7.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lorax
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-17 19:17 UTC by Brian Lane
Modified: 2015-11-19 09:41 UTC (History)
7 users (show)

Fixed In Version: lorax-19.6.59-1
Doc Type: Enhancement
Doc Text:
When creating an Anaconda installation image, the lorax utility now also creates a product.img file and an updates.img file. The product image contains the files in the /usr/share/lorax/product/ directory, and can be used to customize the look and behavior of the installer. The updates image contains the files from the /usr/share/lorax/updates/ directory, and can be used to automatically apply updates to the installer. Both product.img and updates.img are placed in the boot.iso image.
Clone Of:
: 1272359 (view as bug list)
Environment:
Last Closed: 2015-11-19 09:41:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
lorax.log (1.51 MB, text/plain)
2015-10-15 11:35 UTC, Jan Stodola 		no flags Details
program.log (57.21 KB, text/plain)
2015-10-15 11:35 UTC, Jan Stodola 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:2289 0 normal SHIPPED_LIVE lorax bug fix and enhancement update 2015-11-19 09:44:13 UTC

Description Brian Lane 2015-07-17 19:17:40 UTC 
Description of problem:
The 7.1 version of lorax doesn't support creating product.img and updates.img, the 7.2 version does. This feature should be back-ported to help support other projects using lorax to create customized boot.iso's and trees.
Comment 8 Jan Stodola 2015-10-15 11:34:32 UTC 
It doesn't seem to work:

# rpm -q lorax
lorax-19.6.66-1.el7.x86_64
# setenforce 0
# mkdir /usr/share/lorax/product/ /usr/share/lorax/updates/ 
# echo product_test > /usr/share/lorax/product/product
# echo updates_test > /usr/share/lorax/updates/updates
# lorax -p test -v 7 -r 2 -s <URLto base repo> -s <URL to optional repo> lorax_result
...
# cd lorax_result/
# find -name "updates*" -o -name "product*"
#

No product.img nor updates.img were created.

Another issue is that README.product says:
"The x86, ppc, ppc64le and aarch64 templates all look for /usr/share/lorax/product/ and /usr/share/lorax/updates/ directories while creating the final install tree."

s390x is not mentioned there and s390.tmpl is not creating those files - is there any reason for not implementing this feature for s390x?

Moving to ASSIGNED.
Comment 9 Jan Stodola 2015-10-15 11:35:04 UTC 
Created attachment 1083219 [details]
lorax.log
Comment 10 Jan Stodola 2015-10-15 11:35:31 UTC 
Created attachment 1083220 [details]
program.log
Comment 11 Brian Lane 2015-10-15 15:48:57 UTC 
(In reply to Jan Stodola from comment #8)
> It doesn't seem to work:
> 
> # rpm -q lorax
> lorax-19.6.66-1.el7.x86_64
> # setenforce 0
> # mkdir /usr/share/lorax/product/ /usr/share/lorax/updates/ 
> # echo product_test > /usr/share/lorax/product/product
> # echo updates_test > /usr/share/lorax/updates/updates
> # lorax -p test -v 7 -r 2 -s <URLto base repo> -s <URL to optional repo>
> lorax_result
> ...

That isn't the correct way to test it. The files it looks for are *inside* the installation root, so they need to be added by a package.

For manual testing you can add something like this to /usr/share/lorax/runtime-postinstall.tmpl

mkdir usr/share/lorax/product/run/install/product/pyanaconda/installclasses/
append usr/share/lorax/product/run/install/product/pyanaconda/installclasses/custom.py "import logging\nlog = logging.getLogger('anaconda')\nlog.info('bcl was here')\n"

> Another issue is that README.product says:
> "The x86, ppc, ppc64le and aarch64 templates all look for
> /usr/share/lorax/product/ and /usr/share/lorax/updates/ directories while
> creating the final install tree."
> 
> s390x is not mentioned there and s390.tmpl is not creating those files - is
> there any reason for not implementing this feature for s390x?

Looks like it needs commit a2c2a4be280794dcb1, but I'm not sure how important s390 support is at the moment. If it is required, please open a new bug with blocker=? set.
Comment 12 Jan Stodola 2015-10-16 08:47:03 UTC 
(In reply to Brian Lane from comment #11)
> (In reply to Jan Stodola from comment #8)
> > It doesn't seem to work:
> > ...
> That isn't the correct way to test it. The files it looks for are *inside*
> the installation root, so they need to be added by a package.

Thanks, I've created bug 1272361 to make it more clear.

After creating the files in the correct location, both product.img and updates.img were created, included on boot.iso and automatically loaded during boot.

> > Another issue is that README.product says:
> > "The x86, ppc, ppc64le and aarch64 templates all look for
> > /usr/share/lorax/product/ and /usr/share/lorax/updates/ directories while
> > creating the final install tree."
> > 
> > s390x is not mentioned there and s390.tmpl is not creating those files - is
> > there any reason for not implementing this feature for s390x?
> 
> Looks like it needs commit a2c2a4be280794dcb1, but I'm not sure how
> important s390 support is at the moment. If it is required, please open a
> new bug with blocker=? set.

Reported as bug 1272359, but it's not a blocker.


Tested with lorax-19.6.66-1.el7.
Moving to VERIFIED.
Comment 14 errata-xmlrpc 2015-11-19 09:41:04 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-2289.html
Note You need to log in before you can comment on or make changes to this bug.