yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-3

-- 
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/1196570

Title:
  xenapi: pygrub running in domU

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  While I was playing with boot from volume, I discovered that I end up
  with a:

  PV instance if --image-id specified
  HVM instance if --image-id is NOT specified

  That should be an issue caused by not having the proper metadata
  without --image-id switch. But, as part of the investigation,
  interesting log entries appeared in cpu log:

  
  DEBUG nova.virt.xenapi.vm_utils [req-67592d22-4561-4a81-8868-8ac6895efa9d admin demo] Looking up vdi OpaqueRef:055...
  WARNING nova.virt.xenapi.vm_utils [req-67592d22-4561-4a81-8868-8ac6895efa9d admin demo] Image format is None: trying to determine PV status using pygrub; if instance with vdi OpaqueRef:05503c3e-f1c2-e789-ac3b-38b616
  6c59aa does not boot correctly, try with image metadata.
  DEBUG nova.virt.xenapi.vm_utils [req-67592d22-4561-4a81-8868-8ac6895efa9d admin demo] Running pygrub against xvdc
  DEBUG nova.openstack.common.processutils [req-67592d22-4561-4a81-8868-8ac6895efa9d admin demo] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf pygrub -qn /dev/xvdc

  Error while executing pygrub! Please, ensure the binary is installed correctly, and available in your PATH; on some Linux distros, pygrub may be installed in /usr/lib/xen-X.Y/bin/pygrub. Attempting to boot in HVM mode.
  TRACE nova.virt.xenapi.vm_utils Traceback (most recent call last):
  TRACE nova.virt.xenapi.vm_utils   File "/opt/stack/nova/nova/virt/xenapi/vm_utils.py", line 2039, in _is_vdi_pv
  TRACE nova.virt.xenapi.vm_utils     out, err = utils.execute('pygrub', '-qn', dev_path, run_as_root=True)
  TRACE nova.virt.xenapi.vm_utils   File "/opt/stack/nova/nova/utils.py", line 162, in execute
  TRACE nova.virt.xenapi.vm_utils     return processutils.execute(*cmd, **kwargs)
  TRACE nova.virt.xenapi.vm_utils   File "/opt/stack/nova/nova/openstack/common/processutils.py", line 173, in execute
  TRACE nova.virt.xenapi.vm_utils     cmd=' '.join(cmd))
  TRACE nova.virt.xenapi.vm_utils ProcessExecutionError: Unexpected error while running command.
  TRACE nova.virt.xenapi.vm_utils Command: sudo nova-rootwrap /etc/nova/rootwrap.conf pygrub -qn /dev/xvdc
  TRACE nova.virt.xenapi.vm_utils Exit code: 96
  TRACE nova.virt.xenapi.vm_utils Stdout: '/usr/local/bin/nova-rootwrap: Executable not found: pygrub (filter match = pygrub)\n'
  TRACE nova.virt.xenapi.vm_utils Stderr: ''
  TRACE nova.virt.xenapi.vm_utils

  This error says, you need to have pygrub in domU. I think, we should
  really be calling down to dom0, and asking those tools to detect if
  the machine is PV bootable or not.

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