| Summary: | virt-install attempt fails to reach anaconda after system has been running for a while | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||||
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||
| Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 24 | CC: | agedosier, awilliam, berrange, clalancette, crobinso, itamar, laine, libvirt-maint, rjones, veillard, virt-maint | ||||||
| Target Milestone: | --- | ||||||||
| 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: | 2017-05-03 19:38:42 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: | |||||||
| Attachments: |
|
||||||||
|
Description
Adam Williamson
2016-10-21 23:11:47 UTC
Created attachment 1212979 [details]
virt-install command and output (with -d)
Created attachment 1212983 [details]
journal output after starting the virt-install command
hum, so I think it may be a network issue: I think the VM doesn't have network access, so it can't go out and download the installer from the repo, so it doesn't get there (we're doing a direct kernel boot with an `inst.repo` parameter to tell it where to get the installer from, here).
if I run `ipaddr` from the dracut prompt in the VM, I see:
dracut:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:54:00:34:43:9a brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fe34:439a/64 scope link
valid_lft forever preferred_lft forever
and if I try running dhclient, I get:
dracut:/# dhclient ens2
dhcp: PREINIT ens2 up
dhcp: FAIL
dracut:/#
so that seems to be the problem, but I don't see anything immediately obvious wrong with the libvirt networking config. `virsh net-list` shows:
[root@openqa01 libvirt][PROD]# virsh net-list
Name State Autostart Persistent
----------------------------------------------------------
default active yes yes
[root@openqa01 libvirt][PROD]#
Indeed, adding `--network user` to the virt-install command seems to make it fly. But I don't know why it's failing to work with the 'default' libvirt network. Note to self: rwmjones gave me https://bugzilla.redhat.com/show_bug.cgi?id=1271183#c14 as a reference for debugging this further, whenever I can get to it. Adam are you still seeing this? Is it f24 specific? I implemented the workaround I described in #c3 on the openQA boxes, so I can't tell if this is still a problem. I've got quite a lot of other stuff on my plate right now so I'm not sure I want to switch them back and wait for this to happen again... Okay let's close this then, please reopen if you ever take a stab at reproducing |