Bug 1149694

Summary:	ovirt-node el7: cannot use BOOTIF=link
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Douglas Schilling Landgraf <dougsland>
Component:	ovirt-node	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.0	CC:	aberezin, aburden, cshao, dfediuck, dougsland, ecohen, fdeutsch, gklein, hadong, iheim, juwu, lsurette, mgoldboi, ovirt-bugs, rbalakri, ycui, yeylon
Target Milestone:	---	Keywords:	TestOnly
Target Release:	3.5.1
Hardware:	All
OS:	Linux
Whiteboard:	node
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	The BOOTIF=link argument is currently not supported for Red Hat Enterprise Linux 7.0 Hypervisors.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-11 13:57:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1094719

Description Douglas Schilling Landgraf 2014-10-06 13:28:17 UTC

Description of problem:

During autoinstall with the below params ovirt-node goes to dracut interface.

firstboot storage_init=/dev/sda adminpw=RHhwCLrQXB8zE BOOTIF=link

Please note: if I use BOOTIF=ens3 it works.

Version-Release number of selected component (if applicable):

Build from source tree or use last rhevh7 iso available.
Additional note: From my tests, not related to selinux.

Output
======
Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.

dracut:/#


In the file:
<snip>
bio: create slab <bio-2> at 2
bio: create slab <bio-3> at 3
localhost dracut-initqueue[392]: Warning: Could not boot.
localhost systemd[1]: Starting Setup Virtual Console...
localhost systemd[1]: Started Setup Virtual Console.
localhost systemd[1]: Starting Dracut Emergency Shell...

Comment 1 Fabian Deutsch 2014-10-22 12:30:34 UTC

I spoke to the dracut people.
On el7 we should use ip=dhcp to achieve a similar behavior.

The whole solution needs to be investigate, because we need to check if we can still pass BOOTIF=link on the cmdline along with ip=dhcp (to signal the userspace/installer code that we want to start an auto-installation).

If we
a) can pass both BOOTIF and ip= then it might work right away

if

b) we can not pass BOOTIF anymore, then we can
  1) ask dracut to ignore it if BOOTIF=link is passed
  2) update our complete userspace to handle the case where ip=dhcp is passed, but not BOOTIF=link

I believe that 1) is a viable way, if a) is not working.

Comment 3 Fabian Deutsch 2014-11-06 15:44:51 UTC

> 1. prepare a patch where we ignore BOOTIF=link on rhel7, but still use this
> to trigger auto-installation
> 2. With a scratch iso try auto-installation using: "BOOTIF=link ip=dhcp
> storage_init=…"
> 
> So basically:
> BOOTIF=link will be ignored (to set the ip) but it will be used to determine
> if the user want's a auto-installation or not.
> 
> Then: On RHEL 7.+ the user needs to provide BOOTIF=link ip=dhcp if he want's
> a auto-installation.

This does not work.

I'd say we do not support the BOOTIF=link argument on RHEL7 for now and note this in the release notes.

Arthur, is this a viable way?

Comment 4 Julie 2014-12-01 23:02:59 UTC

Hi Fabian,
 Doc text pls.

Cheers,
Julie

Comment 6 Arthur Berezin 2014-12-03 14:24:57 UTC

(In reply to Fabian Deutsch from comment #3)
> > 1. prepare a patch where we ignore BOOTIF=link on rhel7, but still use this
> > to trigger auto-installation
> > 2. With a scratch iso try auto-installation using: "BOOTIF=link ip=dhcp
> > storage_init=…"
> > 
> > So basically:
> > BOOTIF=link will be ignored (to set the ip) but it will be used to determine
> > if the user want's a auto-installation or not.
> > 
> > Then: On RHEL 7.+ the user needs to provide BOOTIF=link ip=dhcp if he want's
> > a auto-installation.
> 
> This does not work.
> 
> I'd say we do not support the BOOTIF=link argument on RHEL7 for now and note
> this in the release notes.
> 
> Arthur, is this a viable way?

We are basically relying on dracut's behavior with RHEL7 here, so ack from my end.

Comment 7 Fabian Deutsch 2014-12-03 15:25:56 UTC

Julie, I've modified the doctext slightly. "currently" got added, because we plan to support it again.

Comment 8 Julie 2014-12-03 23:19:03 UTC

hi Fabian,
    We will not be updating Beta release notes and the release notes we are preparing now is for GA. If this bug is intended to be fixed by GA as I understand that's the plan, this bug doesn't need to be called out as a known issue anymore. I'm removing the release notes flag. 
Please flag again if there are other reasons for this bug to be in the GA release notes.

Cheers,
Julie

Comment 9 Ying Cui 2014-12-04 03:37:09 UTC

I have to change this bug to 'Assigned'.
1. Although this bug is Testonly and no patch on that till now, we still encounter the same issue as initial bug description. QE can not make this bug to Verify.
2. In comment 2,  "prepare a patch where we ignore BOOTIF=link on rhel7, but still use this to trigger auto-installation", till now, this is not achieved yet on build rhev-hypervisor7-7.0-20141119.0.el7ev.
3. In comment 7, this bug still plan to support it future. 

So in current stage, this bug need to be 'Assigned', wait clear expected result future then checking this bug.

Comment 11 Fabian Deutsch 2015-02-11 13:57:47 UTC

The problem really is that dracut has a problem with BOOTIF=link. Our code support this.

We could ask dracut to accept BOOTIF=link, but my suggestion is to not request that fix, but rather to slowly deprecate our custom boot options and reuse the ones dracut provides.

Closing this bug for now.