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.
+++ This bug was initially created as a clone of Bug #1931069 +++
Description of problem:
I have done two test installations with rhel-8.3-x86_64-boot.iso.
One installation was as VM on a Proxmox hypervisor the other on a bare metal machine.
In both cases the graphical installer stops with some unknown error.
Version-Release number of selected component (if applicable):
How reproducible:
Try to install a RHEL system with rhel-8.3-x86_64-boot.iso.
Steps to Reproduce:
1.
2.
3.
Actual results:
The installation stops. But it comes up to a point where kernel and grub are already installed. I cannot login afterward because the files are not labelde correctly for SELinux. What I could do is to enter the system with rd.break, change SELinux into permissive mode and do a relabeling.
Expected results:
A working installation.
Additional info:
--- Additional comment from Jan Stodola on 2021-02-22 10:16:38 CET ---
Can you please provide /tmp/anaconda-tb* from the installation environment when the error appears?
Adding Martin to CC, since this is an Insights-related traceback.
--- Additional comment from Frank Ansari on 2021-02-23 17:24:34 CET ---
--- Additional comment from Frank Ansari on 2021-02-23 17:25:16 CET ---
New test installation with Proxmox done. File attached.
--- Additional comment from Jan Stodola on 2021-02-23 19:28:26 CET ---
Here is the error from anaconda-tb:
16:15:48,867 WARNING org.fedoraproject.Anaconda.Modules.Subscription:DEBUG:anaconda.modules.subscription.installation:insights-connect-task: connecting to insights
16:15:48,868 WARNING org.fedoraproject.Anaconda.Modules.Subscription:INFO:program:Running in chroot '/mnt/sysroot'... /usr/bin/insights-client --register
16:15:59,184 WARNING org.fedoraproject.Anaconda.Modules.Subscription:INFO:program:Unable to fetch egg url. Defaulting to /release
16:15:59,184 WARNING org.fedoraproject.Anaconda.Modules.Subscription:INFO:program:Could not connect to the Insights API. Run insights-client --test-connection for more information.
16:15:59,184 WARNING org.fedoraproject.Anaconda.Modules.Subscription:DEBUG:program:Return code: 1
16:15:59,184 WARNING org.fedoraproject.Anaconda.Modules.Subscription:INFO:anaconda.threading:Thread Failed: AnaTaskThread-ConnectToInsightsTask-1 (140107564644096)
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription:ERROR:anaconda.modules.common.task.task:Thread AnaTaskThread-ConnectToInsightsTask-1 has failed: Traceback (most recent call last):
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 280, in run
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: threading.Thread.run(self)
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: File "/usr/lib64/python3.6/threading.py", line 864, in run
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: self._target(*self._args, **self._kwargs)
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 97, in _task_run_callback
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: self._set_result(self.run())
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/subscription/installation.py", line 81, in run
16:15:59,186 WARNING org.fedoraproject.Anaconda.Modules.Subscription: raise InsightsConnectError("Connecting to Red Hat Insights failed.")
As a workaround you can uncheck the "Connect to Red Hat Insights" check box before registering your systems in the installer.
You can try to register to Insights on the installed system later by running:
# insights-client --register
I'm curios if the command will suceed or the same "Could not connect to the Insights API..." error will be printed even on the installed system - can you please try it and report back?
For anaconda part - it should not crash with a traceback when insights-client fails. This problem can be reproduced by disconnecting the network device when the packages are being installed.
--- Additional comment from Frank Ansari on 2021-02-26 17:42:49 CET ---
With unchecked "Insight" Box the installation runs without error and I could login into the system.
After this I tried
insights-client --register
insights-client --test-connection
Both commands failed. I have attached the logs.
--- Additional comment from Frank Ansari on 2021-02-26 17:44:47 CET ---
--- Additional comment from Frank Ansari on 2021-02-26 17:45:16 CET ---
Cloned against insights-client to investigate the insights-client failure described in bug 1931069#c5.
Comment 4Priscila Gutierres
2021-03-18 17:39:59 UTC
(In reply to Priscila Gutierres from comment #3)
> Regarding the iso image, did the client check the md5sum? Which packages
> were marked to be installed?
Comment 5Priscila Gutierres
2021-03-18 17:41:29 UTC
Did the client check the md5sum? Which packages were marked to be installed?
(In reply to Pavol Kotvan from comment #2)
> Hi Jan,
> could you please confirm that credentials for the account you use for
> subscribing to RHSM can be also used for login into cloud.redhat.com?
> Thanks.
Since I'm not the reporter of the problem in bug 1931069, I'm forwarding this question to the original reporter.
For the list of installed packages, see bug 1931069#c2, line 1470.
Also note there is at least one other bug reported with the same error during the installation, bug 1939919.
It may have been just a temporary bug or outage in the Cloud Platform. Closing as CANTFIX. Please file a new report if the problem occurs again. Thank you for cooperation!