Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1628599
Summary: | very slow network configuration after upgrade to kernel-core >= 4.18.5-200.fc28.x86_64 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pavel Raiskup <praiskup> | ||||
Component: | cloud-init | Assignee: | Garrett Holmstrom <gholms> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 28 | CC: | adimania, apevec, eterrell, gholms, jlebon, lars, shardy, s | ||||
Target Milestone: | --- | ||||||
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: | 2018-09-14 05:30:04 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
Pavel Raiskup
2018-09-13 14:07:56 UTC
Likely dupe of #1572944. > Is there any easy way to debug such issue? Try `systemd-analyze blame | head`, e.g. see https://bugzilla.redhat.com/show_bug.cgi?id=1572944#c10. (Well "dupe" might be wrong. The bug was initially opened against an older kernel, but judging from recent comments mentioning the same kernel versions as here, it looks like it might have regressed but AFAIK no new bugs have been created yet.) Created attachment 1483069 [details]
full diff
I have working f28 and non-working f28 image, while these changes
might be related:
-selinux-policy-3.14.1-40.fc28.noarch
-selinux-policy-targeted-3.14.1-40.fc28.noarch
+selinux-policy-3.14.1-42.fc28.noarch
+selinux-policy-targeted-3.14.1-42.fc28.noarch
Full diff is attached.
# systemd-analyze blame | head 4min 30.503s cloud-init-local.service 4min 30.221s sshd-keygen 4min 30.142s sshd-keygen 4min 30.136s sshd-keygen 8.866s cloud-init.service 897ms initrd-switch-root.service 526ms cloud-final.service 505ms cloud-config.service 241ms dnf-makecache.service 216ms NetworkManager-wait-online.service This is another box, which started faster (the gap was 12:37:47 -> 12:42:16). Thanks Jonathan, you helped me a lot in the end - I used: $ glance image-update --property hw_rng_model=virtio <THE_IMAGE> ... and the VMs boot fine again. *** This bug has been marked as a duplicate of bug 1572944 *** |