Created attachment 950248[details]
attached Screenshot for dracut failed console.png
Description of problem:
From /usr/libexec/ovirt-init-functions.sh
----------------
# oVirt boot parameters
# BOOTIF=link|eth*|<MAC> (appended by pxelinux)
# storage_init=[usb|scsi[:serial#]|/dev/...]
# storage_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MBATA_MB
# mem_overcommit=<overcommit_ratio>
# upgrade
# standalone
# firstboot
# ovirt_runtime_mode
# rescue
# pxelinux format: ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask>
# anaconda format: ip=<client-ip> netmask=<netmask> gateway=<gw-ip>
# or ip=dhcp|off
we known that using ip=off could disable ipv4 configuration.
but auto install will failed in dracut:FATAL:For argement 'ip=off'\n Value 'off' without static configuration does not make sense when auto install with "ip=off"(Seen dracut failed console.png)
Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.0-20141006.0.el7ev
ovirt-node-3.1.0-0.20.20141006gitc421e04.el7.noarch.rpm
dracut-fips-033-161.el7.x86_64
dracut-033-161.el7.x86_64
dracut-network-033-161.el7.x86_64
dracut-config-generic-033-161.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
Actual result:
Expect result:
Additional info:
I'm closing this bug. Because currently it is not really solved how we handle the combination of differen dracut and ovirt specific boot args.
I.e. how should the combination "ip=off BOOTIF=ens0" work?
My suggestion is to not add special logic for this, but to align with RHEL for Node.next.
Please reopen this bug if necessary.
Created attachment 950248 [details] attached Screenshot for dracut failed console.png Description of problem: From /usr/libexec/ovirt-init-functions.sh ---------------- # oVirt boot parameters # BOOTIF=link|eth*|<MAC> (appended by pxelinux) # storage_init=[usb|scsi[:serial#]|/dev/...] # storage_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MBATA_MB # mem_overcommit=<overcommit_ratio> # upgrade # standalone # firstboot # ovirt_runtime_mode # rescue # pxelinux format: ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> # anaconda format: ip=<client-ip> netmask=<netmask> gateway=<gw-ip> # or ip=dhcp|off we known that using ip=off could disable ipv4 configuration. but auto install will failed in dracut:FATAL:For argement 'ip=off'\n Value 'off' without static configuration does not make sense when auto install with "ip=off"(Seen dracut failed console.png) Version-Release number of selected component (if applicable): rhev-hypervisor7-7.0-20141006.0.el7ev ovirt-node-3.1.0-0.20.20141006gitc421e04.el7.noarch.rpm dracut-fips-033-161.el7.x86_64 dracut-033-161.el7.x86_64 dracut-network-033-161.el7.x86_64 dracut-config-generic-033-161.el7.x86_64 How reproducible: 100% Steps to Reproduce: Actual result: Expect result: Additional info: