Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Traceback in anaconda which prevents beaker machine to be installed.
How reproducible:
100%
Steps to Reproduce:
1. Clone job TJ#2585938
2. See anaconda.log in Beaker
Actual results:
>03:19:38,595 ERR anaconda: CmdlineError: The following mandatory spokes are not completed: Software selection
>03:19:38,595 DEBUG anaconda: running handleException
>03:19:38,601 CRIT anaconda: Traceback (most recent call last):
>
> File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/simpleline/base.py", line 352, in _mainloop
> prompt = last_screen.prompt(self._screens[-1][1])
>
> File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 107, in prompt
> raise CmdlineError(errtxt)
>
>CmdlineError: The following mandatory spokes are not completed:
>Software selection
>
>03:19:39,729 DEBUG anaconda: Gtk cannot be initialized
>03:19:39,729 DEBUG anaconda: In the main thread, running exception handler
Expected results:
Installed beaker machine
Additional info:
Traceback was raised during errata testing => https://errata.devel.redhat.com/advisory/33879
Comment 2Samantha N. Bueno
2018-07-03 07:47:44 UTC
Please attach logs to this bug as individual, text/plain attachments so we can debug this.
That said, the snippet of traceback shows you must be specifying cmdline mode when booting (look for "inst.cmdline"). This means installation is completely unattended and will not accept user input. In this case, anaconda's default behavior is to treat an incomplete kickstart file as an error.
You should either not specify "inst.cmdline", or fix your kickstart file. Or both.
Comment 5Samantha N. Bueno
2018-07-03 09:49:07 UTC
Thanks. Looking at your kickstart file, why are i386, i686, and ppc packages specified? This is probably why anaconda is running into issues in the first place.
(In reply to Samantha N. Bueno from comment #5)
> Thanks. Looking at your kickstart file, why are i386, i686, and ppc packages
> specified?
The kickstart file is generated and I assume the another archs should not be a problem because of this line:
> %packages --ignoremissing
Comment 7Samantha N. Bueno
2018-07-03 11:57:10 UTC
(In reply to makopec from comment #6)
> (In reply to Samantha N. Bueno from comment #5)
> > Thanks. Looking at your kickstart file, why are i386, i686, and ppc packages
> > specified?
>
> The kickstart file is generated and I assume the another archs should not be
> a problem because of this line:
> > %packages --ignoremissing
I agree, but we should not assume. Do you also happen to have packaging.log and program.log that you can attach? packaging.log especially will have some more telling information.
Hello,
I'm seeing two potential issues in packaging:
1)
04:06:16,051 INFO packaging: gathering repo metadata for beaker-Server-debuginfo
04:06:16,061 ERR packaging: failed to get groups for repo beaker-Server-debuginfo
04:06:16,061 INFO packaging: gathered repo metadata for beaker-Server-debuginfo
04:06:16,062 INFO packaging: gathering repo metadata for beaker-Server-optional-debuginfo
04:06:16,067 ERR packaging: failed to get groups for repo beaker-Server-optional-debuginfo
2)
04:06:37,822 WARN packaging: sos-3.6-1.el7.noarch requires bpftool
Not sure which one is critical but both looks like they are problem with repositories / kickstart. Could you please somehow check if the repositories are correct? It could be by adding them manually and try to install from them by using yum.
I am convinced it is really dup of bz 1595703, since as far as I understood:
- the brew task tried to install abrt
- that has dependency on sos
- sos-3.6-1 tried to install
- that has dependency on bpftool
- bpftool is (currently) available for x86_64 arch only, brew task was for s390x
- that is subject of the bz 1595703
Current plan is two-fold:
1) sos 3.6-2 is without the dependency (that breaks something else we are working on) - but some RPMDiff issue prevents me to attach this build to my sos errata :( (pending point on secalert now)
2) build bpftool on all architectures - ongoing process, ping skozina or jbenc for status
Closing as dup of 1595703.
*** This bug has been marked as a duplicate of bug 1595703 ***