Bug 1377430

Summary: boot.iso creating failed without firewalld in chroot
Product: Red Hat Enterprise Linux 7 Reporter: Vit Ry <Frodox>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: Frodox, jstodola, lkocman
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lorax-19.6.79-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 16:43:18 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 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