Bug 2025825
Summary: | anaconda timeouts waiting on timezone module | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Sandro Bonazzola <sbonazzo> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WORKSFORME | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | CentOS Stream | CC: | bstinson, jstodola, jwboyer |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-02-08 11:01:00 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1986335 |
Description
Sandro Bonazzola
2021-11-23 06:47:05 UTC
Hello, such timeouts usually happen on system with poor performance. Could you please check the system you are using to build the images? Even in case of a successful run (build 70), it took 13 minutes to (re)generate initramfs, which seems to be quite slow: 01:25:35 00:25:34,616 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:program:Running in chroot '/mnt/sysroot'... dracut -f /boot/initramfs-5.14.0-12.el9.x86_64.img 5.14.0-12.el9.x86_64 01:38:47 00:38:46,702 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:program:Return code: 0 The system is a 12 GB ram VM with 2 VCPUs Westmere E56xx/L56xx/X56xx (Nehalem-C) @2GHz # dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync 1+0 records in 1+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 27.9559 s, 38.4 MB/s Sandro, can you please confirm this issue is still happening? Unfortunately I could not find any failed jenkins job in the link from comment 0 that would fail due to the problem described in this bug. I'm not able to reproduce this anymore, closing this as works for me now. |