Hi Slawek,
Thanks for the pointer! Had a brief look at master code and it seems to
do what we want. Unfortunately we are at Newton, but I'm glad that it's
fixed!
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Enginee
Public bug reported:
All opentack services returns versions data when doing GET to root url.
Placement API instead returns 401. Would be good to have consistency
with other services, so backend check scripts (haproxy) have the same
configuration for placement and other APIs.
root@ctl01:~# curl ht
is not reproduced on master, most probably you have an older OpenStack
version (Pike?)
on recent devstack:
$ curl https://192.168.100.11/placement
{"versions": [{"min_version": "1.0", "max_version": "1.17", "id":
"v1.0"}]}
** Changed in: nova
Status: New => Invalid
--
You received this
ryu in this place doesn't show the address of the peer, but the router
id, which indeed was configured to 0.0.0.82 in that case.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
I see the following traceback in some neutron linuxbridge agent logs:
neutron_lib.callbacks.manager [req-4f4fe77a-3d0e-44d3-b3ef-02a813575d58 - - - -
-] Error during notification for
neutron.services.trunk.drivers.linuxbridge.agent.driver.LinuxBridgeTrunkDriver.agent_port_c
Ok, the notification is like this:
[...]
self._update_network_ports(device_details['network_id'],
device_details['port_id'],
device_details['device'])
self.ext_manager.
*** This bug is a duplicate of bug 1729175 ***
https://bugs.launchpad.net/bugs/1729175
** This bug has been marked a duplicate of bug 1729175
Downloading ec2 creds doesn't work if nova is at newton or newer
--
You received this bug notification because you are a member of Yahoo!
Engineeri
Hmm. the patch did not contain "Closes-Bug: #" unfortunately.
The patch https://review.openstack.org/#/c/524429/ has been merged.
This was fixed in 13.0.0.0b3.
** Changed in: horizon
Status: New => Fix Released
** Changed in: horizon
Importance: Undecided => Low
** Changed in:
According to the discussion above, it seems to happen only when PKI token is
used.
PKI token was dropped from keystone as of now (queens release), so it seems the
time to mark this as Won't Fix.
** Changed in: horizon
Assignee: zhaoyim (yyyiming) => (unassigned)
** Changed in: horizon
Public bug reported:
I am seeing nova-api attempting to use the keystone public endpoint when
/v2.1/os-quota-sets is called on my Pike deployment. This is not valid
in my environment; the API must use the internal endpoint to reach
keystone. When the public endpoint is used, the connection sits in
I added nova to the affect project according to my comment #7.
** Also affects: nova
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/
bug 1709056 is related. The edit flavor feature has been disabled by default
and deprecated in Pike release.
The feature will be dropped in Rocky release.
Considering this, this bug is now marked as Won't Fix.
If we really need to address this bug, we can compare the current and
new values and if
Public bug reported:
Flavor-Edit feature was deprecated in Pike (bug 1709056).
We can drop it in Rocky release.
Note that "Flavor Access" tab should be kept.
** Affects: horizon
Importance: High
Status: New
** Changed in: horizon
Importance: Undecided => High
--
You received
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova
Status: New => 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/175
Public bug reported:
When I open Angular implementation of Create User form, the choices of
"Primary Project" is filled with existing keystone roles. "Role" choices
is empty.
** Affects: horizon
Importance: High
Status: New
** Tags: queens-backport-potential
--
You received this
Public bug reported:
Inter Tenant Traffic between Two Tenants on two different private
networks connected through a common shared network (created by Admin) is
not route able through DVR routers
Steps to reproduce it:
(NOTE: No external, just shared network)
This is only reproducable in Multinod
I can create a new server whose name is #3r even when I used 'nova'
CLI. Horizon can add a validation that nova applies, but it seems nova
has no check to prevent from using a name like #3r in creating a
server. From this observation, we will reject this bug as Invalid. If
nova applies a v
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
18 matches
Mail list logo
