Bug 1403857 - Kernel Panic with IPA images on 2 GiB VM
Summary: Kernel Panic with IPA images on 2 GiB VM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-python-agent
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dmitry Tantsur
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 13:50 UTC by Kevin Tibi
Modified: 2017-08-29 16:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-29 16:43:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
kernel panic (92.69 KB, image/jpeg)
2016-12-12 14:04 UTC, Kevin Tibi
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.