Description of problem: During install of ISO(s), receive "An unknown error has occurred" Version-Release number of selected component (if applicable): RHCI-6.0-RHEL-7-20151216.t.1 RHCIOOO-7-RHEL-7-20160118.t.0 How reproducible: Sporatic Steps to Reproduce: 1. Install ISO 2. 3. Actual results: An unknown error has occurred...."Kickstart error: /usr/sbin/authconfig is missing. Cannot setup authentication." Expected results: Successful install Additional info: This hardware has installed successfully before.
From Python debugger: Exception yum.Errors.RepoError: RepoError() in <bound method YumSqlitePackageSack.__del__ of <yum.sqlitesack.YumSqlitePackageSack object at 0x<address>> ignored Stack trace: /usr/lib64/python2.7/site-packages/pyanaconda/threads.py(211)run() -> threading.Thread.run(self. *args, *kwargs) /usr/lib64/python2.7/threading.py(764)run() -> self.__target(*self.__args, **self.__kwargs) /usr/lib64/python2.7/site-packages/pyanaconda/install.py(79)doConfiguration() -> ksdata.authconfig.execute(storage,ksdata,instClass) /usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py(277)execute() -> raise KickstartError(msg)
Command is auth --useshadow --enablemd5 From /tmp/packaging.log ERR yum.verbose.YumPlugins: Plugin "product-id" can't be imported (3 times) [...] DEBUG packaging: Installing libldb (304/1251) DEBUG packaging: Traceback (most recent call last): DEBUG packaging: File "/usr/libexec/anaconda/anaconda-yum", line 220, in callback DEBUG packaging: return func(amount, total, key, data) DEBUG packaging: File "/usr/libexec/anaconda/anaconda-yum", line 342, in inst_open_file DEBUG packaging: os.unlink(txmbr.po.localPkg()) DEBUG packaging: OSError: [Errno 30] Read-only file system: '/run/install/repo/Packages/libldb-1.1.17-2.el7.x86_64.rpm' DEBUG packaging: FATAL ERROR: python callback <bound method RPMCallback.callback of <__main__.RPMCallback object at 0x<address>> failed, aborting! [...] ERR packaging: systemd is not installed -- can't set default target
Verified in QCI-1.0-RHEL-7-20160819.t.0 And really this has not been seen for quite some time.
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/RHEA-2016:1862