yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80138
[Bug 1845284] [NEW] Config CONF.libvirt.inject_partition=-1, build instance with metadata will remain some images in /var/tmp/.guestfs-0/appliance.d
Public bug reported:
Description
===========
Boot instance with metadata will remain some images in '/var/tmp/.guestfs-0/appliance.d' when this compute_node config CONF.libvirt.inject_partition=-1.
Steps to reproduce
==================
1) Config inject_partition=-1(/etc/nova/nova.conf) in compute_node.
2) boot instance with metadata on this compute_node.
3) boot instance success but some images were remained.
Expected result
===============
In the end of booting instance, can remove those images in /var/tmp/.guestfs-0/appliance.d
Actual result
=============
Those images be left forever.
Environment
===========
1. Exact version of OpenStack you are running. See the following
openstack-nova-api-18.0.2-1.el7.noarch
2. Which hypervisor did you use?
Libvirt + KVM
2. Which storage type did you use?
LVM
3. Which networking type did you use?
Neutron with OpenVSwitch)
Logs & Configs
==============
{'message': u"No operating system found in <LocalFileImage:{'path': u'/var/lib/nova/instances/7e79433f-917d-43da-88f0-757c6d3572c5/disk', 'format': 'qcow2'}>", 'class': 'NovaException', 'kwargs': {'code': 500}}
** Affects: nova
Importance: Undecided
Status: New
--
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/1845284
Title:
Config CONF.libvirt.inject_partition=-1, build instance with metadata
will remain some images in /var/tmp/.guestfs-0/appliance.d
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
Boot instance with metadata will remain some images in '/var/tmp/.guestfs-0/appliance.d' when this compute_node config CONF.libvirt.inject_partition=-1.
Steps to reproduce
==================
1) Config inject_partition=-1(/etc/nova/nova.conf) in compute_node.
2) boot instance with metadata on this compute_node.
3) boot instance success but some images were remained.
Expected result
===============
In the end of booting instance, can remove those images in /var/tmp/.guestfs-0/appliance.d
Actual result
=============
Those images be left forever.
Environment
===========
1. Exact version of OpenStack you are running. See the following
openstack-nova-api-18.0.2-1.el7.noarch
2. Which hypervisor did you use?
Libvirt + KVM
2. Which storage type did you use?
LVM
3. Which networking type did you use?
Neutron with OpenVSwitch)
Logs & Configs
==============
{'message': u"No operating system found in <LocalFileImage:{'path': u'/var/lib/nova/instances/7e79433f-917d-43da-88f0-757c6d3572c5/disk', 'format': 'qcow2'}>", 'class': 'NovaException', 'kwargs': {'code': 500}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1845284/+subscriptions
Follow ups