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.

Bug 1951973

Summary: RHEL 8.3 "Unknown error has occured"
Product: Red Hat Enterprise Linux 8 Reporter: anonymous <fepel13251>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.3CC: jstodola
Target Milestone: betaFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-22 15:02:55 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:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
dbus.log
none
dnf.librepo.log
none
hawkey
none
lvm
none
packaging
none
program
none
storage
none
syslog
none
X none

Description anonymous 2021-04-21 09:05:15 UTC
Description of problem:
 I downloaded RHEL 8.3 with a developer subscription. During Installation anaconda exits Installation, quoting " Unknown error has Occurred". 

Version-Release number of selected component (if applicable):8.3


How reproducible:
It can be reproduced.

Steps to Reproduce:
1.Download RHEL8.3 with developer subscription.
2.Connect to network during installation.
3.Register to redhat subscription in the installation configuration page.
4.Select Workstation in the configuration.
4.The error occurs when "configuring redhat subscription" after 1549 RPM downloaded and Installed. 

Actual results:


Expected results:


Additional info:

Comment 1 Jan Stodola 2021-04-21 10:41:14 UTC
Can you please provide the installation logs? /tmp/anaconda-tb* from the installation environment should be enough.

See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_installation/troubleshooting-at-the-start-of-the-installation_installing-rhel#using-installation-log-files_troubleshooting-at-the-start-of-the-installation with instructions for getting the logs.

Comment 2 anonymous 2021-04-21 11:42:55 UTC
(In reply to Jan Stodola from comment #1)
> Can you please provide the installation logs? /tmp/anaconda-tb* from the
> installation environment should be enough.
> 
> See
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/
> html/performing_a_standard_rhel_installation/troubleshooting-at-the-start-of-
> the-installation_installing-rhel#using-installation-log-
> files_troubleshooting-at-the-start-of-the-installation with instructions for
> getting the logs.

Will the shell open when I press alt+ctrl+f2 during the middle of installation after it shows " Unknown error has occured " ,Just need to make sure.!?

Comment 3 Jan Stodola 2021-04-21 12:08:41 UTC
Yes, alt+ctrl+f2 will work when you see the "Unknown error" message.

Comment 4 anonymous 2021-04-22 12:08:01 UTC
(In reply to Jan Stodola from comment #3)
> Yes, alt+ctrl+f2 will work when you see the "Unknown error" message.

I got the logs , it's like around 10 files.But in attachment It says I could attach only one. What should I do?

Comment 5 anonymous 2021-04-22 12:09:01 UTC
(In reply to aj03 from comment #4)
> (In reply to Jan Stodola from comment #3)
> > Yes, alt+ctrl+f2 will work when you see the "Unknown error" message.
> 
> I got the logs , it's like around 10 files.But in attachment It says I could
> attach only one. What should I do?

Can I mail it to you?

Comment 6 Jan Stodola 2021-04-22 13:57:07 UTC
You can attach it to this bug via the "Add an attachment" link above.
Of course, feel free to erase any sensitive data from the logs.
If you do not want to share the whole log, you can attach just parts of it - usually the most important parts are "Traceback" messages, but they alone are not always enough for debugging and fixing the problem.

Comment 7 anonymous 2021-04-22 14:40:26 UTC
Created attachment 1774498 [details]
anaconda.log

Comment 8 anonymous 2021-04-22 14:41:01 UTC
Created attachment 1774499 [details]
dbus.log

Comment 9 anonymous 2021-04-22 14:42:01 UTC
Created attachment 1774500 [details]
dnf.librepo.log

Comment 10 anonymous 2021-04-22 14:42:36 UTC
Created attachment 1774501 [details]
hawkey

Comment 11 anonymous 2021-04-22 14:44:36 UTC
Created attachment 1774503 [details]
lvm

Comment 12 anonymous 2021-04-22 14:45:36 UTC
Created attachment 1774504 [details]
packaging

Comment 13 anonymous 2021-04-22 14:46:11 UTC
Created attachment 1774505 [details]
program

Comment 14 anonymous 2021-04-22 14:47:40 UTC
Created attachment 1774507 [details]
storage

Comment 15 anonymous 2021-04-22 14:48:13 UTC
Created attachment 1774508 [details]
syslog

Comment 16 anonymous 2021-04-22 14:48:47 UTC
Created attachment 1774509 [details]
X

Comment 17 anonymous 2021-04-22 14:54:55 UTC
(In reply to Jan Stodola from comment #6)
> You can attach it to this bug via the "Add an attachment" link above.
> Of course, feel free to erase any sensitive data from the logs.
> If you do not want to share the whole log, you can attach just parts of it -
> usually the most important parts are "Traceback" messages, but they alone
> are not always enough for debugging and fixing the problem.

I attached all the logs and explained how to reproduce the error.

Comment 18 Jan Stodola 2021-04-22 15:02:55 UTC
Thank you for the logs - based on them this is another problem with running "insights-client --register" during the installation.

Please see the Doc text field in bug 1931069 for a workaround. The workaround is also documented in the RHEL-8.3 release notes as "Red Hat Insights client fails to register the operating system when using the graphical installer":
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.3_release_notes/rhel-8-3-0-release#known-issue_installer-and-image-creation

I'm closing this issue as a duplicate of an existing insights-client bug.

*** This bug has been marked as a duplicate of bug 1940018 ***