Bug 1403857

Summary: Kernel Panic with IPA images on 2 GiB VM
Product: Red Hat OpenStack Reporter: Kevin Tibi <kodokuu>
Component: openstack-ironic-python-agentAssignee: Dmitry Tantsur <dtantsur>
Status: CLOSED WONTFIX QA Contact: Raviv Bar-Tal <rbartal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: bfournie, kodokuu, mburns, rmahroua, slinaber
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-29 16:43:51 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
kernel panic none

Description Kevin Tibi 2016-12-12 13:50:10 UTC 
Description of problem:
When ironic try to inspect a VM with IPA image, a kernel panic appears.

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


How reproducible:
Try to inspect VM KVM-host with the actual IPA images.

Steps to Reproduce:
1. Boot kvm-VM on network
2. add fake_pxe driver on ironic
3. add the mac nic VM in the inventory

Actual results:
Kernel Panic

Expected results:
VM boot normaly

Additional info:
Works with RDO IPA images: http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/mitaka/delorean/
Comment 1 Dmitry Tantsur 2016-12-12 13:55:09 UTC 
Was it RHEL 7.2 or 7.3? How much memory do you have on VMs? Do you have any screenshots?
Comment 2 Kevin Tibi 2016-12-12 14:01:36 UTC 
VM have 2Gb RAM. 

I use rhel 7.2 for director node and director have 4Gb RAM.

Kernel Panic on VM :

/init: error while loading shared libraries: /lib64/libblkid.so.1: invalid ELF header.

I try to run IPA image on qemu too without success.

RPM used for image is :
rhosp-director-images-ipa-9.0-20161031.1.el7ost.noarch
Comment 3 Dmitry Tantsur 2016-12-12 14:03:04 UTC 
> VM have 2Gb RAM.

Does increasing RAM fix the problem by change?
Comment 4 Kevin Tibi 2016-12-12 14:04:33 UTC 
Created attachment 1230799 [details]
kernel panic
Comment 5 Kevin Tibi 2016-12-12 14:49:26 UTC 
RAM up to 4Gb fix pb.
Comment 6 Razique Mahroua 2017-02-07 22:59:56 UTC 
I ran into the same issue. I confirm that bumping to 3GB did the trick.
Comment 7 Bob Fournier 2017-08-29 16:43:51 UTC 
Closing as WONTFIX as our use case requires 3 GB.