Bug 1156320 - dracut:FATAL:For argement 'ip=off'\n Value 'off' without static configuration does not make sense when auto install with "ip=off"
Summary: dracut:FATAL:For argement 'ip=off'\n Value 'off' without static configuration...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.6.0
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard: node
Depends On:
Blocks: rhevh-7.0
TreeView+ depends on / blocked
 
Reported: 2014-10-24 07:58 UTC by haiyang,dong
Modified: 2016-02-10 20:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-11 13:56:05 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
attached Screenshot for dracut failed console.png (39.72 KB, image/png)
2014-10-24 07:58 UTC, haiyang,dong 		no flags Details
View All

Description haiyang,dong 2014-10-24 07:58:07 UTC 
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:
Comment 3 Fabian Deutsch 2015-02-11 13:56:05 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.