** Changed in: tripleo
Status: In Progress => 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/1765008
Title:
Tempest API tests failing for stable/queens branch
Public bug reported:
This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:
- [x] This doc is inaccurate in this way:
command example to set image multiqueue property have wrong
Have not heard of this coming up recently.
** No longer affects: glance/newton
** Changed in: glance/ocata
Status: New => Incomplete
** Changed in: glance
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Reviewed: https://review.openstack.org/563995
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e36a2bd65c65d7dad15579aa86bb5fe6614a40ab
Submitter: Zuul
Branch:master
commit e36a2bd65c65d7dad15579aa86bb5fe6614a40ab
Author: Hongbin Lu
Date: Tue
** Changed in: glance
Status: Fix Committed => Fix Released
** Changed in: glance/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Reviewed: https://review.openstack.org/530777
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=35b304661d17e1b64460101ae30273a4c5672a14
Submitter: Zuul
Branch:master
commit 35b304661d17e1b64460101ae30273a4c5672a14
Author: Stephen Finucane
Date: Tue
Public bug reported:
I don't know why the sphinx build doesn't fail for this, but the oslo
config option links for the RAMWeigher and CPUWeigher don't work:
https://docs.openstack.org/nova/latest/user/filter-
scheduler.html#weights
RAMWeigher Compute weight based on available RAM on the compute
OK, so I think the next step here is to create a test xenial image
without that datasource_list and confirm that it boots as expected.
This, however, will not help the situation for already-deployed
instances upgrading, so I guess we'll also need to look at having a
cloud-init postinst hook go
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init
Assignee: (unassigned) => Ryan Harper (raharper)
--
Public bug reported:
When IBMCloud deploys from a template, artifacts from the
provisioning stage are normally cleaned up. Cloud-init relied'
on that behavior to determine the provisioning boot from the subsequent
post-provisioning boot.
However, when testing, the provisioning stage will leave
Reviewed: https://review.openstack.org/550468
Committed:
https://git.openstack.org/cgit/openstack/api-wg/commit/?id=b585c8485d86c2ec9bc19d9f99ab442f9b375374
Submitter: Zuul
Branch:master
commit b585c8485d86c2ec9bc19d9f99ab442f9b375374
Author: Chris Dent
Date: Wed Mar
Public bug reported:
Description
===
Bringing up a new cluster as part of our CI after switch from 16.1.0 to
16.1.1 on Centos, I'm seeing this error on some computes:
2018-04-26 13:36:26.580 14536 ERROR nova.compute.manager Traceback (most recent
call last):
2018-04-26 13:36:26.580
** Changed in: pypowervm
Status: In Progress => 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/1766692
Title:
instance.uuid no longer being a str
Public bug reported:
Seeing occasional functional test failures in the image import tests
(for example [0]). They currently sleep to wait for the server to
complete an action [1], but sometimes the action apparently takes longer
than expected.
Would be good to introduce some kind of
Reviewed: https://review.openstack.org/564278
Committed:
https://git.openstack.org/cgit/openstack/nova-powervm/commit/?id=af0e814d628289c07c8e88629539a3e42c3d3daa
Submitter: Zuul
Branch:master
commit af0e814d628289c07c8e88629539a3e42c3d3daa
Author: Eric Fried
Date: Wed
Is there a way we can invoke using SHAs in pycadf from keystone
directly? It looks like a configuration option was introduced to make
using md5 conditional, but I can't seem to invoke it from config.
We might have to fix this in pycadf directly. I don't think we have any
options for working
** Changed in: nova
Status: Invalid => 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.net/bugs/1766208
Title:
Lift the restriction on choices for
I insist.
** Changed in: nova
Status: In Progress => 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/1766208
Title:
Lift the restriction on choices for
Reviewed: https://review.openstack.org/562220
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b2c40366b3b65876e5465efae05b171be1bc473
Submitter: Zuul
Branch:master
commit 8b2c40366b3b65876e5465efae05b171be1bc473
Author: Jakub Libosvar
Date:
mox3 is also affected, as seen in the test results for this nova change:
https://review.openstack.org/#/c/564343/
https://github.com/openstack/mox3/blob/285bc2a1760d460080df79f1ed3b0988cab44f7b/mox3/mox.py#L909
** Also affects: python-mox3
Importance: Undecided
Status: New
** Changed
** Changed in: keystone
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1750660
Title:
The v3 project API should account for
Not to belabor this: FWIW, as you know, we intentionally restricted the
original feature. So now we're just fixing that "bad" implementation.
So personally, I'd prefer to track this item in this bug too. But if
you really insist, I can let it go.
** Changed in: nova
Status: Invalid => In
** Changed in: keystone
Status: Triaged => Confirmed
** Changed in: keystone
Status: Confirmed => In Progress
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
When running rally scenarios the test fails with PortNotFoundClient exception.
>From the logs we see the following:
Failure:
---
▼ 11 GetResourceFailure Failed to get the resource : The server has either erred or is incapable of
performing the requested
24 matches
Mail list logo