← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1661292] [NEW] VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-block(0, 0): error -6

 

Public bug reported:

Description
===========
An kvm instance failed to boot with a kernel panic after hitting this error:

VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
block(0,0): error -6

Steps to reproduce
==================
This doesn't reproduce reliably, it seems to be a race condition.

* I started an instance through the API.  It had not attached storage,
and was attached to a single network. It used an Ubuntu Xenial cloud
image which booted successfully on a different instance on a different
compute node.

Expected Result
===============
* I expected the instance to boot successfully

Actual Result
=============
* The instance failed to boot with a kernel panic:
http://pastebin.ubuntu.com/23911493/

* I used virsh destroy to stop that instance, then started it again
through the API, and it worked.

Environment
===========
xenial/newtown/kvm/openvswitch, no attached storage.

ii  nova-common                          2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - common files
ii  nova-compute                         2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node base
ii  nova-compute-kvm                     2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node (KVM)
ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
ii  python-nova                          2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute Python libraries
ii  python-novaclient                    2:6.0.0-0ubuntu1~cloud0             all          client library for OpenStack Compute API - Python 2.7
ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: oil oil-guestos-fail

** Attachment added: "sosreport-hayward-49-20170202154349.tar.xz"
   https://bugs.launchpad.net/bugs/1661292/+attachment/4812126/+files/sosreport-hayward-49-20170202154349.tar.xz

** Description changed:

  Description
  ===========
  An kvm instance failed to boot with a kernel panic after hitting this error:
  
  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6
  
  Steps to reproduce
  ==================
  This doesn't reproduce reliably, it seems to be a race condition.
  
  * I started an instance through the API.  It had not attached storage,
  and was attached to a single network. It used an Ubuntu Xenial cloud
  image which booted successfully on a different instance on a different
  compute node.
  
  Expected Result
  ===============
  * I expected the instance to boot successfully
  
  Actual Result
  =============
  * The instance failed to boot with a kernel panic:
  http://pastebin.ubuntu.com/23911493/
  
+ * I used virsh destroy to stop that instance, then started it again
+ through the API, and it worked.
+ 
  Environment
  ===========
  xenial/newtown/kvm/openvswitch, no attached storage.
  
  ii  nova-common                          2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - common files
  ii  nova-compute                         2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node base
  ii  nova-compute-kvm                     2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
  ii  python-nova                          2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute Python libraries
  ii  python-novaclient                    2:6.0.0-0ubuntu1~cloud0             all          client library for OpenStack Compute API - Python 2.7
  ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
  ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
  ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
  ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1661292

Title:
  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  An kvm instance failed to boot with a kernel panic after hitting this error:

  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6

  Steps to reproduce
  ==================
  This doesn't reproduce reliably, it seems to be a race condition.

  * I started an instance through the API.  It had not attached storage,
  and was attached to a single network. It used an Ubuntu Xenial cloud
  image which booted successfully on a different instance on a different
  compute node.

  Expected Result
  ===============
  * I expected the instance to boot successfully

  Actual Result
  =============
  * The instance failed to boot with a kernel panic:
  http://pastebin.ubuntu.com/23911493/

  * I used virsh destroy to stop that instance, then started it again
  through the API, and it worked.

  Environment
  ===========
  xenial/newtown/kvm/openvswitch, no attached storage.

  ii  nova-common                          2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - common files
  ii  nova-compute                         2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node base
  ii  nova-compute-kvm                     2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
  ii  python-nova                          2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute Python libraries
  ii  python-novaclient                    2:6.0.0-0ubuntu1~cloud0             all          client library for OpenStack Compute API - Python 2.7
  ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
  ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
  ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
  ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1661292/+subscriptions


Follow ups