Public bug reported:
Resize revertion leaves instance directory on the second host with Ceph
image backend. As the result the second attempt to resize the instance
to the same host fails with n-cpu.log:
Traceback (most recent call last):
File "/opt/stack/nova/nova/compute/manager.py", line 3942
Public bug reported:
If an instance is booted from a volume backed snapshot with
ephemeral(s), it cannot be resized down to a flawor with disk size is
lesser than original flavor disk size.
Steps to reproduce:
1 Prepare flavors
$ nova flavor-create t1.nano-2-e auto 64 2 1 --ephemeral 1
$ nova fl
Well, if all you guys say this is not a bug, it's not a bug. But it's
sadly that Nova cannot guarantee device names even in this simple case.
** Changed in: nova
Status: New => Invalid
** Changed in: nova
Assignee: Feodor Tersin (ftersin) => (unassigned)
--
You r
@Nikola, the problem is not about device names, but about consistency
and workability of volume backed instance snapshots.
Should we support a use case:
1 A user snapshots his volume backed instance which has more than one volume.
2 A user creates a new instance from the snapshot.
3 All services
Public bug reported:
If an image has several volume in bdm, and a user adds one more volume
for boot operation, then the new volume is not just added to a volume
list, but becomes the second device. This can lead to problems if the
image root device has various soft which settings point to other
v
Public bug reported:
Since that https://review.openstack.org/#/c/182994/ is merged, Cinder
doesn't allow an empty volume name. But Nova specifies it for a new
volume when the volume is created from a snapshot or a volume. Thus boot
operation fails on compute node.
Steps to reproduce:
1 Boot an in
Public bug reported:
If an image has settings for the same device in both 'mappings' and
'block_device_mapping' properties, the last one should be used for
instance launch. But currently 'mappings' takes precedence.
=
Steps to reproduce:
1 Create a flavor with ephemeral disk.
opensta
ld `%s' cannot be None") % attr)
ValueError: Field `container_format' cannot be None
** Affects: nova
Importance: Undecided
Assignee: Feodor Tersin (ftersin)
Status: New
** Changed in: nova
Assignee: (unassigned) => Feodor Tersin (ftersin)
--
You rec
inst
where xxx is an image id.
2 Look at the device name:
openstack volume list
Expected value: /dev/vda
Actual value: /dev/vdb
Inside guest OS the volume is displayed as /dev/vda.
** Affects: nova
Importance: Undecided
Assignee: Feodor Tersin (ftersin)
Status: In Progress
Public bug reported:
instance.root_gb means size of host local disk used by the instance root
disk. All code that uses this attribute treats it that way.
Volume-backed instances have root disks placed in Cinder. Therefore
obviously root_gb should be 0 for them. However currently this is not
so. T
The same result is occured with a deleted public flavor or when a private
flavor become inaccessible for the instance project.
For all cases Nova reports the flavor id and doesn't crash. The failure occures
in novaclient side.
Nova reports the id always, even when the flavor exists and is accessi
Public bug reported:
Fail to create a snapshot of an instance booted from a volume backed
snapshot.
It's reproduced with current (~Kilo-3) devstack.
Steps to reproduce:
$ nova boot inst --block-device
id=,source=image,dest=volume,bootindex=0,size=1--flavor m1.nano
$ nova image-create inst volb
Public bug reported:
EC2 API fails to create a snapshot of a volume backed instance
It's reproduced with current (~Kilo-3) devstack.
Steps to reproduce:
$ nova boot inst --block-device
id=,source=image,dest=volume,bootindex=0,size=1--flavor m1.nano
$ euca-create-image -n volback-ec2
Returns:
Public bug reported:
If default security group in tenant is deleted (admin has appropriate
permissions) then launching an instance with Neutron port fails at
allocate network resources stage:
ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)
TRACE nova.compute.manage
Public bug reported:
In EC2 classic mode AWS automatically associates a public IP address to
an instance being launched. See
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-
addressing.html#differences
Since Nova EC2 emulates EC2 classic mode of AWS (there is no VPC support
in N
Public bug reported:
Each AWS describe operation has common and some custom filter parameters
to filter result set by various object attributes. But Nova EC2 supports
filters by object ids only.
I found similar ancient bug https://bugs.launchpad.net/nova/+bug/734912,
but it's closed with 'invalid
Public bug reported:
$ euca-describe-tags --filter resource-id=vol-nnn
returns tags for ami-nnn instance.
For example:
$ euca-describe-tags
TAG i-000e instancexxx yyy
$ euca-describe-tags --filter resource-id=vol-000e
TAG i-000e instancexxx y
Public bug reported:
AWS is able to create and attach a new empty volume while launching an
instance. See
http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html:
---
To create an empty Amazon EBS volume, omit the snapshot ID and specify a volume
size in
Public bug reported:
AWS provides a scenario to expand volumes of an instance
(http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html). It
consist of:
1 Stop the instance
2 Create a snapshot of the volume
3 Create a new volume from the snapshot
4 Detach the old volum
5 Attach
Public bug reported:
AWS allows to register a volume backed image. But Nova doesn't:
$ euca-register -n ebs-image --kernel aki-0002 --ramdisk ari-0003
--root-device-name /dev/vda -b /dev/vda=snap-0006
euca-register: error (HTTPInternalServerError): The server has either erred or
is
Public bug reported:
AWS allows to attach a volume with short device name (without '/dev/'
prefix). But Nova doesn't.
$ euca-attach-volume -i i-0008 -d vdd vol-0003
euca-attach-volume: error (InvalidDevicePath): The supplied device path (vdd)
is invalid.
** Affects: nova
Importance
Public bug reported:
EC2 describe images crashes on volume backed instance snapshot which has
several volumes:
$ euca-describe-images
euca-describe-images: error (KeyError): Unknown error occurred.
Steps to reproduce
1 Create bootable volume
$ cinder create --image
2 Boot instance from volume
Public bug reported:
AWS allows to change block device attributes (such as volume size,
delete on termination behavior, existence) at instance launch.
For example, image xxx has devices:
vda, size 10, delete on termination
vdb, size 100, delete on termination
vdc, size 100, delete on termination
Public bug reported:
For EBS images AWS returns device names, volume sizes, delete on
termination flags in block device mapping structure.
$ euca-describe-images ami-d13845e1
IMAGE ami-d13845e1amazon/amzn-ami-hvm-2014.03.2.x86_64-ebsamazon
available public x86_64 machine
;t do it:
VOLUME vol-0001 1 novain-use
2014-08-10T19:51:06.00
ATTACHMENT vol-0001NoneNoneNoneNone
** Affects: nova
Importance: Undecided
Assignee: Feodor Tersin (ftersin)
Status: New
--
You received this bug notification be
a-create-
volume.
** Affects: nova
Importance: Undecided
Assignee: Feodor Tersin (ftersin)
Status: New
** Changed in: nova
Assignee: (unassigned) => Feodor Tersin (ftersin)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
instances
$ euca-describe-instances
Look on instace type. It must be ebs, but it is instance-store in the output.
Note. If euca-describe-instance crashes on ebs instnce, apply
https://review.openstack.org/#/c/95580/
** Affects: nova
Importance: Undecided
Assignee: Feodor Tersi
For example this affects Tempest. Tempest expects correct (AWS version)
errors in waitXXXStatus functions and raises an error if other error
cames for absent objects. So it make difficult writting tests.
** Affects: nova
Importance: Undecided
Assignee: Feodor Tersin (ftersin
https://review.openstack.org/#/c/95580/
** Project changed: devstack => nova
** Changed in: nova
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.n
Public bug reported:
For instance booted from volume with legacy bdm and image (this method is
documented as workaround in
http://docs.openstack.org/grizzly/openstack-ops/content/attach_block_storage.html)
admin user creates instance snapshot in the image tenant rather than current
tenant.
Cre
Public bug reported:
Launting an instance from bootable volume passing legacy bdm is
available only using vda (no /dev/ prefix) as root device name. This is
weird restriction. It prevents to create consistent instance data,
because root_device_name instance attribute has /dev/ prefix, but
device_n
Public bug reported:
An incorrect snapshot is created from volume backed instance booted from
volume. The snapshot doesn't have disk_format and container_format
attributes. As a result booting from the snapshot fails.
Environment: DevStack
Steps to reproduce:
1 Create bootable volume
$ cinder cr
32 matches
Mail list logo
