Bug 1377430 - boot.iso creating failed without firewalld in chroot
Summary: boot.iso creating failed without firewalld in chroot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lorax
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
: 1422877 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 16:36 UTC by Vit Ry
Modified: 2017-08-01 16:43 UTC (History)
3 users (show)

Fixed In Version: lorax-19.6.79-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 16:43:18 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1962 0 normal SHIPPED_LIVE lorax bug fix and enhancement update 2017-08-01 17:56:16 UTC

Description Vit Ry 2016-09-19 16:36:17 UTC
Description of problem:

lorax fails, when trying to create boot.iso without firewalld


Version-Release number of selected component (if applicable):
lorax-19 (rhel7-branch) : https://github.com/rhinstaller/lorax/tree/rhel7-branch


How reproducible:
Always


Steps to Reproduce:
Create boot.iso without firewalld in deps of pkgs on runtime-install.tmpl
(like, for docker/atomic host, or with custom set of pkgs)

Actual results:
    symlink /lib/systemd/system/rngd.service etc/systemd/system/basic.target.wants/rngd.service
FileNotFoundError: [Errno 2] No such file or directory: '/lib/systemd/system/rngd.service' -> '/var/tmp/lorax.7cgdtz1_/installtree/etc/systemd/system/basic.target.wants/rngd.service'


Expected results:
boot.iso created

Additional info:
There is no check that used dir 'etc/systemd/system/basic.target.wants' exists. And this dir created by firewalld only (in post).

My PR: https://github.com/rhinstaller/lorax/pull/158

Comment 1 Brian Lane 2017-02-17 21:56:51 UTC
*** Bug 1422877 has been marked as a duplicate of this bug. ***

Comment 5 errata-xmlrpc 2017-08-01 16:43:18 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://access.redhat.com/errata/RHBA-2017:1962


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