Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1148191

Summary: Discovery fails on baremetal installs with dracut
Product: Red Hat OpenStack Reporter: Balaji <bjayavel>
Component: foreman-discovery-imageAssignee: Lukas Zapletal <lzap>
Status: CLOSED WORKSFORME QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: bjayavel, fdeutsch, lzap, mburns, morazi, rhos-maint, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: Installer   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-30 16:07:00 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 Flags
discovery error image none

Description Balaji 2014-09-30 22:00:24 UTC 
Description of problem:The discovery image sometimes (yes not always) fails into dracut.Rebooting the node sometimes clears the problem and the node gets discovered. No issues with VMs.


Version-Release number of selected component (if applicable):2014-9-23.3 puddle


How reproducible:


Steps to Reproduce:
1.PXE boot the nodes 
2.Fails with dracut
3.

Actual results:
Output attached

Expected results:
The node should be discovered

Additional info:
Comment 1 Balaji 2014-09-30 22:01:26 UTC 
Created attachment 942854 [details]
discovery error image
Comment 4 Lukas Zapletal 2014-10-02 07:16:40 UTC 
Hey, are you able to retrieve complete kernel logs? I am afraid I can't tell from the screenshot. Adding Fabian to CC.
Comment 5 Lukas Zapletal 2014-10-02 07:18:21 UTC 
Fabian, do you happen to know what can be possibly wrong with ovirt-node on this hardware?

Balaji, just to doublecheck - have your hardware more than 1 GB RAM?
Comment 6 Balaji 2014-10-02 14:19:37 UTC 
Lukas,

This is a bare metal with 48GB memory. The installer has a total of 3gb memory. So I guess memory should not be an issue.
Comment 7 Lukas Zapletal 2014-10-08 12:59:03 UTC 
Balaji,

I am unable to reproduce, I see you got the shell. Can you pastebin whole kernel log using dmesg command please?

alias paste='curl -F '\''sprunge=<-'\'' http://sprunge.us'
dmesg | paste

I am interested also in the sosreport.txt which is displayed there.
Comment 8 Mike Burns 2014-10-08 13:02:00 UTC 
Just a note, we played around with this system last night.  We found that if you simply "exit" from the dracut shell, the host boots correctly.  

Ugly workaround, but it worked...
Comment 9 Lukas Zapletal 2014-10-09 07:44:19 UTC 
Can you guys collect some info from the host? There's not much really I can do with one screenshot...
Comment 10 Balaji 2014-10-09 13:42:10 UTC 
(In reply to Mike Burns from comment #8)
> Just a note, we played around with this system last night.  We found that if
> you simply "exit" from the dracut shell, the host boots correctly.  
> 
> Ugly workaround, but it worked...

Mike,

I have tried that as well. It doesn't succeed all the time. 

Balaji
Comment 11 Fabian Deutsch 2014-10-09 15:24:56 UTC 
Could you please try adding ip=dhcp to the cmdline when you boot the discovery image?
Comment 12 Lukas Zapletal 2014-10-10 08:00:41 UTC 
Here are few tips: http://fedoraproject.org/wiki/How_to_debug_Dracut_problems

Can you retrieve the "/run/initramfs/rdsosreport.txt" via netcat or USB stick?

Thanks
Comment 15 Mike Burns 2015-04-30 16:07:00 UTC 
This does not reproduce in my environments with osp6