Public bug reported:
The User and Groups module's uid parameter does not take effect unless
you specify its value as a string.
I do not know if this is a code defect or if it is working as designed.
If it is working as designed, it would be nice if the documentation were
updated to note that uid
Public bug reported:
The Nova volume attachment is causing the device / mount point of the
volume attachment in Cinder to be set to /dev/na.
The Trove gate is doing the following steps, though it could probably be
recreated with a simple volume attach:
1. Spawn instance with ephemeral disk and
Public bug reported:
The Trove gates are failing when attempting to resize an instance what
has an ephemeral disk and an attached volume.
The stack when it fails is this:
Dec 11 03:03:28.751318 ubuntu-xenial-rax-dfw-0001351106 nova-compute[28059]:
ERROR nova.compute.manager [None
** Also affects: mitaka (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: mitaka (Ubuntu)
--
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/1488111
Public bug reported:
I know of two examples in the documentation that contain dashes in
config keys when they need to be underscores to function at runtime.
Following the examples in this case can lead to a lot of wasted time and
the dash vs underscore difference can be easy to miss, even when
https://my.glance.server:9292/versions: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)
The root cause is that this method creates an HttpClient to fetch the
versions URI and it does not pass in the cert validation information.
** Affects: nova
Importance: Undecide
I created this bug based on old patches I had, a test program that
showed excutils.save_and_reraise_exception() was not re-raising the
exception, and code inspection of the compute manager _shutdown_instance
method.
excutils.save_and_reraise_exception() does not re-raise the exception,
but it
to debug why the virt driver destroy method failed.
[1]
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2252
** Affects: nova
Importance: Undecided
Assignee: Samuel Matzek (smatzek)
Status: New
** Changed in: nova
Assignee: (unassigned) = Samuel Matzek
is in initialize_connection and then work back up the stack to ensure
that when this different exception is thrown a BuildAbortException is
not thrown so the reschedule can happen.
** Affects: nova
Importance: Undecided
Assignee: Samuel Matzek (smatzek)
Status: New
** Changed in: nova
This is purely a Glance bug and can be recreated without Nova in the
picture at all, therefore I do not believe that the bug fix mentioned in
comment 5 will fix this.
See the recreation steps in comment 2. This can be completely
abstracted from Nova. The bug is that Glance v1 allows you to set
Public bug reported:
Creating a sever using a Glance image which has a long (~256 char)
unicode property value fails with database truncation.
The root cause is the same as bug:
https://bugs.launchpad.net/nova/+bug/1389102
and fix:
https://review.openstack.org/#/c/134597/
What's happening is
Public bug reported:
Nova Juno
Scenario:
1. Boot an instance from a volume.
2. Nova snapshot the instance. This produces a Glance image with a block
device mapping property like this:
[{guest_format: null, boot_index: 0, no_device: null, snapshot_id:
1a642ca8-210f-4790-ab93-00b6a4b86a14,
Public bug reported:
Nova Juno
The instance snapshot of volume backed instances does not handle image
metadata the same way that the regular instance snapshot path does.
nova/compute/api/api.py's snapshot path builds the Glance image metadata
using nova/compute/utils.py get_image_metadata which
Public bug reported:
When booting servers using Nova configured for injecting network setup
into the guest OS, Nova is not injecting DHCP network configurations.
Nova.conf has these set:
# Whether to attempt to inject network setup into guest
# (boolean value)
flat_injected=true
# Template file
14 matches
Mail list logo