Bug 2135374

Summary:	Initial-setup freezes for a while while downloading dnf repodata
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan Stodola <jstodola>
Component:	initial-setup	Assignee:	Martin Kolman <mkolman>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.7	CC:	jkonecny, mkolman
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 16:00:07 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:

Description Jan Stodola 2022-10-17 12:19:38 UTC

Description of problem:
When dnf repositories are enabled on the installed system, initial-setup becomes unresponsive for a while after clicking the "Finish configuration" button.
journalctl shows that repository metadata are being downloaded during this freeze and only after that initial-setup is closed and the system continues:

...
říj 17 07:33:21 localhost.localdomain anaconda[1040]: dnf: repo: downloading from remote: rhel-8-for-x86_64-baseos-rpms
říj 17 07:33:39 localhost.localdomain anaconda[1040]: dnf: rhel-8-for-x86_64-baseos-rpms: using metadata from Mon 17 Oct 2022 06:00:36 AM EDT.
říj 17 07:33:39 localhost.localdomain anaconda[1040]: dnf: repo: downloading from remote: rhel-8-for-x86_64-appstream-rpms
říj 17 07:33:49 localhost.localdomain systemd[1]: systemd-localed.service: Succeeded.
říj 17 07:33:50 localhost.localdomain systemd[1]: systemd-hostnamed.service: Succeeded.
říj 17 07:34:00 localhost.localdomain anaconda[1040]: dnf: rhel-8-for-x86_64-appstream-rpms: using metadata from Mon 17 Oct 2022 07:10:29 AM EDT.
říj 17 07:34:00 localhost.localdomain anaconda[1040]: dnf: Last metadata expiration check: 0:00:10 ago on Mon 17 Oct 2022 07:33:43 AM EDT.
...

This only happens when subscription-manager-initial-setup-addon is installed. If the package is uninstalled, metadata are not downloaded and there is no significant delay before clicking the "Finish configuration" button and closing initial-setup.

To reproduce this issue it's good to have repositories with big repodata and/or using slow network connection.

Version-Release number of selected component (if applicable):
RHEL-8.6, RHEL-8.7
initial-setup-0.3.81.7-1.el8
subscription-manager-initial-setup-addon-1.28.32-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL-8 with the default package set (Server with GUI) and register to CDN during the installation.
2. Reboot to the installed system.
3. Accept the EULA in initial-setup and click the "Finish configuration" button quickly.
4. An alternative approach is to configure dnf repositories on the installed system, run "dnf clean all && systemctl enable initial-setup" and reboot the system.

Actual results:
initial-setup freezes until metadata are downloaded.

Expected results:
initial-setup finishes without a significant delay, or there is a notification that metadata are being downloaded.

Comment 2 Jiri Konecny 2022-10-21 08:58:14 UTC

It seems that it could be an issue with Subscription Manager addon in the Initial Setup. Could you please take a look on this?

Comment 4 RHEL Program Management 2023-09-18 15:58:38 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-18 16:00:07 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 6 Red Hat Bugzilla 2024-01-17 04:25:22 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days