Reviewed: https://review.openstack.org/418409
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=46c4c3d4f993e793d32de65f0cc99ad2b00a2cf1
Submitter: Jenkins
Branch:master
commit 46c4c3d4f993e793d32de65f0cc99ad2b00a2cf1
Author: Mateusz Kowalski
Reviewed: https://review.openstack.org/468018
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=9ffb72b2f1e31da6e2b2cb5f4fd8de3db8e6574c
Submitter: Jenkins
Branch:master
commit 9ffb72b2f1e31da6e2b2cb5f4fd8de3db8e6574c
Author: Beth Elwell
Date: Thu
Migrating the instance without nova works (with virsh), so that looks
like a nova bug.
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
cloud-init doesn't currently support providing networking configuration in
user-data.
It does though allow providing network-config through the 'NoCloud' datasource
(which uvtool uses).
So we could extend uvtool to add a '--network-config' parameter like
it's user-data that would then put the
upgrade_level was badly set, so nova-compute was doing the legacy
LiveMigrateData convertion, while the data was already in the correct
format.
What looks weird is why the live-migration have not been rejected during
precheck.
** Changed in: nova
Status: New => Invalid
** Changed in:
Public bug reported:
Seen here:
http://logs.openstack.org/46/487246/2/experimental/gate-tempest-dsvm-
neutron-dvr-ha-multinode-full-ubuntu-xenial-nv/6cd2a5b/logs/devstack-
gate-discover-hosts.txt.gz
localhost | SUCCESS | rc=0 >>
Found 2 cell mappings.
Skipping cell0 since it does not contain
Public bug reported:
Looking at the Neutron Failure Rate dashboard, specifically the tempest
jobs:
http://grafana.openstack.org/dashboard/db/neutron-failure-
rate?panelId=10
One can see the gate-tempest-dsvm-neutron-dvr-ha-multinode-full-ubuntu-
xenial-nv job has a very high failure rate, over
Fix proposed to branch: master
Review: https://review.openstack.org/487925
** Changed in: nova
Status: Invalid => In Progress
** Changed in: nova
Assignee: (unassigned) => Ed Leafe (ed-leafe)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Reviewed: https://review.openstack.org/486208
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=06b4ff7df857f56d6ecb819895c17e1e708dd071
Submitter: Jenkins
Branch:master
commit 06b4ff7df857f56d6ecb819895c17e1e708dd071
Author: Chris Friesen
Reviewed: https://review.openstack.org/389866
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f40e9d438eb759d43e76e837d042740d89d622d8
Submitter: Jenkins
Branch:master
commit f40e9d438eb759d43e76e837d042740d89d622d8
Author: Eddie Ramirez
The issue was a breaking change in Cinder. Symptoms of the failure were
different than what are mentioned earlier. Marking it as invalid
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/newton
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova/ocata
Importance: Undecided => Medium
** Changed in: nova/newton
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: nova (Ubuntu Xenial)
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/1639230
Title:
reschedule fails with ip
Public bug reported:
- It asserts by checking if "exact json body" of created subnets(of
both private and shared networks ,which gets created in test case) is
present in output of "list_subnets(shared=X)['subnets']" for
X=True/False.
Here, "priv" or "shared" is set to the body of subnet at the
This really should come in as a spec, it's a feature add.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Tags added: needs-spec
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: nova
Status: New => Won't Fix
--
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/1682811
Title:
nova boot apis raises 500 error if scheduler_hints
Reviewed: https://review.openstack.org/485082
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=d24abbe792c7ddb911c4f7ffee5c3b2fced4650b
Submitter: Jenkins
Branch:master
commit d24abbe792c7ddb911c4f7ffee5c3b2fced4650b
Author: Lujin
Date: Wed
Reviewed: https://review.openstack.org/475276
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=bf17be9e8ffc393a3af1dbd88b0c0623658b0979
Submitter: Jenkins
Branch:master
commit bf17be9e8ffc393a3af1dbd88b0c0623658b0979
Author: Takashi NATSUME
** Changed in: ossn
Status: Confirmed => Fix Released
--
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/1686743
Title:
Ceph credentials included in logs using older
Public bug reported:
The recently merged patch (https://review.openstack.org/484949) runs the
migration in the driver's init_host() method. It has since been pointed
out that if there are multiple computes handling ironic, some instances
can get skipped if the hash ring is refreshed and an
I pushed up a sanity check patch:
https://review.openstack.org/#/c/488187/2
for this and got a hit in the live migration job:
http://logs.openstack.org/87/488187/2/check/gate-tempest-dsvm-multinode-
live-migration-ubuntu-
xenial/107a810/logs/subnode-2/screen-n-cpu.txt.gz#_Jul_27_22_21_14_766229
Reviewed: https://review.openstack.org/481311
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9e9a8a07c3cb1eed074399af36affe857011133e
Submitter: Jenkins
Branch:master
commit 9e9a8a07c3cb1eed074399af36affe857011133e
Author: Swaminathan Vasudevan
This bug was fixed in the package glance - 1:2015.1.4-0ubuntu2
---
glance (1:2015.1.4-0ubuntu2) trusty-kilo; urgency=medium
.
* d/p/allow-image-list-if-access-to-attrs-is-forbidden.patch:
Allow to list images in v2 if get_image_location policy is set
to role:admin and
Public bug reported:
The GCE data source will always include SSH keys from project metadata
in the default (ubuntu) user's authorized_keys file. If block-project-
ssh-keys is set in metadata, however, project-level SSH keys shouldn't
be included.
** Affects: cloud-init
Importance:
Public bug reported:
It should be using project/attributes/ssh-keys.
** Affects: cloud-init
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Fixed in https://review.openstack.org/#/c/486867/
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1705012
Title:
vif type
Public bug reported:
GCE supports specifying SSH keys for an instance as a tuple of
(username, key). Currently, cloud-init will add all keys to the default
(ubuntu) user, regardless of the user specified in metadata.
This is problematic because there may be users in the metadata who are
not
Public bug reported:
GCE supports the expiration of SSH keys. It does so by including the
expiry time in a JSON blob in the comment section of the SSH key. As
per [0], the format is:
ssh-rsa [KEY_VALUE] google-ssh
{"userName":"[USERNAME]","expireOn":"[EXPIRE_TIME]"}
Keys can remain in
Reviewed: https://review.openstack.org/487772
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=ca07237167e88fb2e26de424c8a859a18552e6e3
Submitter: Jenkins
Branch:master
commit ca07237167e88fb2e26de424c8a859a18552e6e3
Author: Balazs Gibizer
Please find the version details below
* cinder
1.11.0
* python-openstackclient-
openstack 3.9.0
(* nova)
7.1.0
Please let us know if any more further information needed.
** Project changed: nova => cinder
** Changed in: cinder
Status: Incomplete => New
--
You received this bug
Public bug reported:
It's great that the Placement API v1.4 provides a way to query for hosts
that can fulfill a set of allocations. However, because the max_unit
doesn't account for allocation_ratio, the result is not as expected.
For example, my host has 2 vCPU available out of a total of 4
Fixed inside pylint and updated our version of pylint to grab fix:
https://git.launchpad.net/cloud-init/commit/?id=9c33cb24b8a834aa8034db4c989725901a0814c6
Pylint fix:
https://github.com/PyCQA/pylint/issues/1444
** Changed in: cloud-init
Status: New => Invalid
** Changed in: cloud-init
Public bug reported:
As far back as Ocata, compute nodes that manage allocations will end up
overwriting allocations from other compute nodes when doing a migration.
This stems from the fact that the Resource Tracker was designed to
manage a per-compute-node set of accounting, but placement is
I reproduce this bug with libvirt 1.3.1.Since libvirt 1.2.7 this
operation can fail if the filter with the same name already exists for
the given uuid.Nova lasted code has fixed this bug.
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because
35 matches
Mail list logo