[IBP] Ubuntu 14.04 deployment results in kernel panic

[Bartłomiej Piotrowski]

After provisioning and reboot, Ubuntu boot ends up with kernel panic:
https://paste.xinu.at/2Fm2/

api: '1.0'
astute_sha: 484d5038b81b7260597be027b1265dc88091026b
auth_required: true
build_id: 2015-05-13_22-55-26
build_number: '414'
feature_groups:
- mirantis
fuel-library_sha: f9310aa52628d70b45a8d9cb735dd309f9b556f8
fuel-ostf_sha: 1ae384a28b42d5325bd5d2546aead1e9d502f6a8
fuelmain_sha: 1c03fb884d3e79165a2406d00a5ea8679e35f4f7
nailgun_sha: afbcea1d4928e588a8858e154770cd9d031a1fc7
openstack_version: 2014.2.2-6.1
production: docker
python-fuelclient_sha: e4ebbc720c2d5e4546b51758c5796821ed4377f6
release: '6.1'
release_versions:
  2014.2.2-6.1:
    VERSION:
      api: '1.0'
      astute_sha: 484d5038b81b7260597be027b1265dc88091026b
      build_id: 2015-05-13_22-55-26
      build_number: '414'
      feature_groups:
      - mirantis
      fuel-library_sha: f9310aa52628d70b45a8d9cb735dd309f9b556f8
      fuel-ostf_sha: 1ae384a28b42d5325bd5d2546aead1e9d502f6a8
      fuelmain_sha: 1c03fb884d3e79165a2406d00a5ea8679e35f4f7
      nailgun_sha: afbcea1d4928e588a8858e154770cd9d031a1fc7
      openstack_version: 2014.2.2-6.1
      production: docker
      python-fuelclient_sha: e4ebbc720c2d5e4546b51758c5796821ed4377f6
      release: '6.1'

TEST=deploy_ha_one_controller_vlan using fuel-devops+fuel-qa.

[Vladimir Kozhukalov (kozhukalov)]

Does plain ubuntu of the same version work on this node? if yes, could you please compare the list of installed packages with the one which is installed into an image? And could you please show the kvm process cmdline on the host corresponding to the failed machine?

[Vladimir Kuklin (vkuklin)]

I am pretty sure that this is a kernel bug with virtualization drivers. Let's investigate it deeper, but close if it is just a KVM or virt bug.

[Vladimir Kozhukalov (kozhukalov)]

+1 likely kvm bug

[Bogdan Dobrelya (bogdando)]

Lowered to high as there is no deployment of operations impact for production deployments

[Bogdan Dobrelya (bogdando)]

(If this is a KVM issue)

[Bartłomiej Piotrowski (bpiotrowski)]

Seemingly fixed by downgrading kernel on the host to 3.13.