Reviewed: https://review.openstack.org/612505
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=c39afbd5fcdfff2ad5e7f6963768da9f3d8027d2
Submitter: Zuul
Branch:master
commit c39afbd5fcdfff2ad5e7f6963768da9f3d8027d2
Author: Slawek Kaplonski
Date: Mon Oct 22 22:58:48
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
I believe that this should be reopened, since the issue remains for the
following reasons:
* All installation guide docs refer to Keystone running on port 5000
(OS_AUTH_URL=http://controller:5000/v3). If that's no longer the
recommended deployment model, then the docs should be updated
Reviewed: https://review.openstack.org/584999
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=1ba150fa5233ebeacdc02e89b2e83a1a6861bc19
Submitter: Zuul
Branch:master
commit 1ba150fa5233ebeacdc02e89b2e83a1a6861bc19
Author: Sean Mooney
Date: Tue Jul 31 21:22:52 2018
Public bug reported:
Job: any tempest plugin scenario jobs
Failed test:
neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details
Sample failure:
Public bug reported:
When using the LXD module cloud-init will attempt to install ZFS if it
does not exist on the target system. However instead of installing the
`zfsutils-linux` package it attempts to install `zfs` resulting in an
error.
This was captured from a MAAS deployed server however
Check the [neutron] section of the nova configuration file used for your
nova-conductor service, because that is what is failing. Is that
configured? And if so, what are the values? Are those consistent with
what is in the service catalog for the networking service (neutron)?
** Changed in: nova
This doesn't seem to be a nova problem, but a problem with your
database:
2018-10-11 04:47:49.827 12628 ERROR nova.api.metadata.handler
[req-e8a61425-56dc-4dd7-bbca-05ae913f24c0 - - - - -] Failed to get metadata for
instance id: b9f8fe03-a78b-43f3-bc1f-68ceaff3f978
2018-10-11 04:47:49.827 12628
We should fix keystoneclient. KeystoneAuth is not doing anything wrong
here. I am against a "temp hack" like this. Secondarily, please submit
this patch to gerrit at review.openstack.org so that it can be
considered. Posting patches here is unlikely to be seen as
easily/readily.
** Changed in:
** Changed in: keystoneauth
Status: Triaged => Won't Fix
--
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/1498556
Title:
Reasonable assumptions concerning
** Changed in: pycadf
Status: Fix Committed => Fix Released
--
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/1659053
Title:
use uuids with pycadf
Status in
@Ben, this is nothing to do with oslo-policy. it has to do with the
values passed to oslo-policy in the creds dict. If the creds dict does
not have domain-id populated in it, you can't enforce on it.
** Changed in: oslo.policy
Status: Incomplete => Invalid
--
You received this bug
** Changed in: python-keystoneclient
Status: In Progress => Won't Fix
--
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/1687593
Title:
Create OAUTH request
Is this something in the Keystone Server? this doesn't seem to be KSC
specific.
** Changed in: python-keystoneclient
Status: In Progress => Incomplete
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
removed keystonemiddleware as LP will timeout when trying to update.
** No longer affects: keystonemiddleware
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1266962
Title:
Remove
Revocations are no longer exposed with keystone. Marking this bug as
invalid.
** Changed in: keystonemiddleware
Status: Triaged => Won't Fix
** Changed in: keystonemiddleware
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Yahoo!
marking as invalid for ksm.
** Changed in: keystonemiddleware
Status: In Progress => Invalid
--
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/1440493
Title:
I don't know how we'll address this. Realistically, I think this is
going to have to be marked as invalid/wont fix/opinion. I'm going to
mark it as wont fix, we can circle back on it if there is more
discussion to be had.
** Changed in: keystone
Status: New => Won't Fix
--
You received
newton is EOL
** Changed in: keystone/newton
Status: In Progress => Won't Fix
** Changed in: keystone/ocata
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
This isn't something Keystone directly has control over, what is in our
requirements/g-r is what we ship with. Marking as invalid for keystone
server.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Marking as incomplete for OSC, please re-visit if it is still an issue
(many things have changed across the board) and invalid for keystone.
** Changed in: keystone
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Marking as wont fix. The solution has been discussed and is recommended
that the public_endpoint be unset.
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Marked as invalid. Not a lot we can do about python-memcached, but with
the py3-first testing i think we are beyond this as a bug.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: keystone/newton
Status: Fix Committed => Fix Released
--
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/1630092
Title:
Admin password reset
** Changed in: keystone/newton
Status: Fix Committed => Fix Released
--
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/1635306
Title:
After newton deployment
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
I'm going to mark this as opinion. It likely will get better with scope-
types and policy-in-code, but this bug in itself isn't relevant due to
how trusts were architected.
** Changed in: keystone
Status: Confirmed => Opinion
--
You received this bug notification because you are a member
** Changed in: keystone/newton
Status: Fix Committed => Fix Released
** Changed in: keystone/ocata
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
** Changed in: keystone/ocata
Status: Fix Committed => Fix Released
** Changed in: keystone/newton
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Not a bug in keystone. Something must be fixed in pycadf.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Public bug reported:
OVSNeutronAgent.rpc_loop is always called with "polling_manager"
parameter.
Furthermore, "polling_manager" cannot be retrieved like in [1].
"get_polling_manager" is a generator and must be used within a context
manager.
[1]
Marking as invalid. Validation should not vary based upon options set in
configuration keystone-to-keystone. It makes it hard to know what to
expect when interacting with keystone.
** Changed in: keystone
Status: In Progress => Opinion
--
You received this bug notification because you
I'm going to mark this as invalid. It is recommended to add a rate-
limiter in-front of the openstack services if needed. Ideally Keystone
could support such a bit of software, but it is largely out-of-scope
(can be supplied by the fronting webservers e.g. apache and
mod_ratelimit)
** Changed in:
This is just something to do, update global-requirments and it is
populated down. Updating global-requirements for a past release is hard
to do, it is suggested that you simply propose the changes and it will
be synchronized to keystone once it is approved.
** Changed in: keystone/pike
Marking this as wont fix. This really is not something we can address in
a meaningful way at this time. It expands through a huge set of issues
across all of openstack and is not in line with the direction of the
project now.
** Changed in: keystone
Status: Triaged => Won't Fix
--
You
I believe the bug is right here:
https://github.com/openstack/nova/blob/835faf3f40af6b0e07c585690982a997d6a2ac47/nova/compute/provider_tree.py#L128
That is just comparing the keys in the dict, not the values, so:
>>> old
{'a': 1, 'b': 2}
>>> new
{'a': 1, 'b': 2}
>>> new['b'] = 3
>>> old
{'a':
I guess this shouldn't be a problem in queens because the resource
tracker didn't use that provider tree to report back the inventory
changes:
https://github.com/openstack/nova/blob/stable/queens/nova/compute/resource_tracker.py#L883
That was done in Rocky:
Reviewed: https://review.openstack.org/611484
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=2e85dc47c9301b00f89bd44955534f8d9631e3d6
Submitter: Zuul
Branch:master
commit 2e85dc47c9301b00f89bd44955534f8d9631e3d6
Author: Vishakha Agarwal
Date: Wed Oct 17 16:43:15
Public bug reported:
Nova change https://review.openstack.org/#/c/317693/ set a min=1 value
on the shutdown_timeout config option.
https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.shutdown_timeout
The glance image meta def description for the related
os_shutdown_timeout
** Project changed: neutron => bgpvpn
** Project changed: bgpvpn => networking-bgp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1799455
Title:
AttributeError: 'BgpDrAgentNotifyApi'
Since this report concerns a possible security risk, an incomplete
security advisory task has been added while the core security reviewers
for the affected project or projects confirm the bug and discuss the
scope of any vulnerability along with potential solutions.
** Information type changed
Public bug reported:
(OpenStack 14)
After changing the value of cpu_allocation_ratio in nova.conf from 16 to
1 and restarting nova containers, the ProviderTree still uses the old
value
(A patch with extra debugging is applied to the system for ProviderTree
information)
Nova.conf setting:
Public bug reported:
With db50bc0d9 the sysconfig renderer was enabled for openSUSE and SUSE
Linux Enterprise. This requires that cloud-init.service starts after
wicked, but at present the service is started after wicked.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert
Public bug reported:
Looking at agent/linux/bridge_lib.py, I see that most methods of
BridgeDevice use calls to brctl, using a namespace wrapper. They work as
expected.
However, some methods (get_interface_bridge, owns_interface,
get_interfaces) retrieve information from the file system, and do
Reviewed: https://review.openstack.org/609839
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=184c84ae76b1e4dc6b9907caf0cfa0d65bf8ecc5
Submitter: Zuul
Branch:master
commit 184c84ae76b1e4dc6b9907caf0cfa0d65bf8ecc5
Author: Morgan Fainberg
Date: Thu Oct 11 15:16:02
Reviewed: https://review.openstack.org/546114
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=7f121363935be32b345ec80fd15d478bb8d9f23f
Submitter: Zuul
Branch:master
commit 7f121363935be32b345ec80fd15d478bb8d9f23f
Author: Ameed Ashour
Date: Tue Feb 20 05:54:33 2018
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nova (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/1744079
47 matches
Mail list logo
