Public bug reported:
For some reason nova allows creating a flavor with a disk_size of 0,
when an instance is booted using such flavor its disk will use the
native base image size as the size of the ephemeral root volume (from
the ops docs).
Even though having the disk_size=0 means that the insta
hould
create them from the API layer, before validating the block device
mappings and only if no swap or ephemeral device are defined by the
user.
** Affects: nova
Importance: Medium
Assignee: Xavier Queralt (xqueralt)
Status: New
--
You received this bug notification because you
--image --flavor test
$ nova image-create test test-snap
$ nova delete test
The image 'test-snap' will be left in the SAVING state although it
should be deleted when we detect the situation.
** Affects: nova
Importance: Medium
Assignee: Xavier Queralt (xqueralt)
S
Public bug reported:
With current nova in master, when booting an instance using an existing
volume without specifying the device_name fails with the following
traceback in nova compute:
$ nova boot --boot-volume f1f2de9c-eedf-41cf-9089-a41ec0706b3e --flavor
m1.custom --key-name default server --
Public bug reported:
When attaching volumes from NFS or GlusterFS backends, nova mounts the
share in a temporary directory, this is reused when attaching another
volume from the same share so there is no need to mount it several
times.
On the other hand, when disconnecting those volumes nova does
I've jut checked the log of volume.py module and I couldn't find any
version containing that extra whitespace mentioned in your report. Could
it be that it was introduced by mistake in your local checkout?
See
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/volume.py#L810
** Chang
Public bug reported:
There are several ways of selecting the disk_bus for a BDM. One of them
is using the hw_disk_bus image property which, if present, is inherited
by volumes created from an image.
When booting from a volume that has this property defined, even though
we might think it will be c
Public bug reported:
When booting an instance, in the API layer, we get the image to be used
for this instance or, if the instance is booted from a volume, the image
metadata attached to the volume (if present). This allows us to know a
bit more of the volume through the inherited properties of th
You need a newer version of eventlet. This was reported in [1] and fixed
with the patch in [2]. I'll try to update the packages in RDO but in the
meanwhile, could you open a bug in [3] for tracking it? Thanks.
[1] https://bitbucket.org/eventlet/eventlet/issue/136
[2] https://bitbucket.org/eventlet
Public bug reported:
While setting the bridge up, if the network interface has a dynamic
address, the 'dynamic' flag will be displayed in the "ip addr show"
command:
[fedora@dev1 devstack]$ ip addr show dev eth0 scope global
2: eth0: mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
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/1158807
Public bug reported:
nova-api service will fail to start when the nova-api command is invoked
from a directory containing a file with the same name as the one
specified in the configuration key 'api_paste_config' if it is not an
absolute path (the default is 'api-paste.ini').
[fedora@devstack1 de
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1251757
Title:
On restart of QPID broker, fanout no longer works
Stat
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: packstack
Status: New => Invalid
** No longer affects: nova
** Also affects: nova
Importance: Undecided
Status: New
** Summary changed:
- Nova Scheduler Fails to Start Due to Missing cinderclient
When using cold snapshots nova will stop the instance while copying the
disk and bring it back once done. This is the normal behaviour and won't
happen if your system is capable of doing live snapshots (qemu >= 1.3.0
and libvirt >= 1.0.0).
** Changed in: nova
Status: New => Invalid
--
You
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: nova
Status: Incomplete => Invalid
** Summary changed:
- selected cylinder exceeds maximum supported by bios
+ glusterfs: invalid volume when source image virtual size is bigger than the
requested size
--
This is a problem only with the version of qemu-img shipped in RHEL 6.5
which lacks the -s option.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https:/
** Changed in: nova
Status: New => Invalid
--
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/1223180
Title:
Block device mapping is not updated in the swap volume
S
Nova will always start as much instances as it can fit with the current
quota (try it with nova client).
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
h
** Changed in: nova
Status: Confirmed => Invalid
--
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/1008976
Title:
UnicodeEncodeError when snapshotting an instance or
20 matches
Mail list logo
