Just updating the latest comments. This is API change and we need spec
for any API change. This is not priority for Rocky and i will check and
discuss in API meeting if we can do and it is worth to do in stein. Or
it is ok to just fix the python client.
Marking invalid for tempest as tempest is
Reviewed: https://review.openstack.org/566961
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=db22f5bfa81df10ce4a30cae725b6e11c843ee30
Submitter: Zuul
Branch:master
commit db22f5bfa81df10ce4a30cae725b6e11c843ee30
Author: Brian Haley
Date: Tue May 8 14:06:30 2018
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive/ocata
Status: New => Triaged
** Changed in: cloud-archive/ocata
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Instance group member records used to be in the cell databases but were
moved to the API database in Ocata. Previously, when deleting an
instance in the cell, we'd also delete it's instance group membership
record in the same cell database. Now that instance group membership
** Changed in: nova
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/1777478
Title:
Public bug reported:
Due to this deprecation in oslo.test 3.5.0:
https://github.com/openstack/oslotest/commit/cae8c8d51a94b891ce5b311a91d01b4264b296d2
#diff-72a674ad74b628edbd0f73729c353b85R24
We get this warning quite a bit:
nova/test.py:323: DeprecationWarning: Using class 'MoxStubout'
Public bug reported:
Hi,
Volumes - Backup panel is visible even if OPENSTACK_CINDER_FEATURES =
{'enable_backup': False} in local_settings.py
Meanwhile setting enable_backup to false removes an option to create
backup of a volume in the volume drop-down options. But panel with
backups itself
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/rocky
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance:
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/pike
Public bug reported:
We don't have an API to delete a consumer. It gets created implicitly
when allocations are created against it, but it doesn't get deleted when
the consumer's last allocation is removed. In some uses of placement,
such as nova's, there is a high rate of turnover of consumers
** Changed in: nova (Ubuntu Cosmic)
Status: Triaged => Fix Released
** Changed in: cloud-archive/rocky
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
** Also affects: cloud-archive/rocky
Importance:
Public bug reported:
This is using microversion 1.28 of the placement API. I will start the
process of finding when this went wrong after submitting this bug. I'm
guessing at the start of POST to /allocations, but we'll see.
When a POST to /allocations contains multiple consumers each writing
Public bug reported:
### Bug in documentation ###
https://docs.openstack.org/neutron/queens/admin/config-qos.html
1) Commands’ order
“The QoS bandwidth limit rules attached to a floating IP will become active
when you associate the latter with a port. For example, to associate the
previously
Public bug reported:
- [x] This is a doc addition request.
According to [1], 'geneve' should be listed as a tunneled network type.
[1]
https://review.openstack.org/#/c/564445/10/nova/network/neutronv2/api.py
---
Release: 11.0.6.dev14 on 2018-06-25 22:39
SHA:
Public bug reported:
cloud-init-integration-lxd-b test 200 failed.
Looking at the console log at [1] shows
boot instance encountered error: ssh: after 120s instance is not reachable
at 2018-06-26 11:23:47,693 which was indeed 120 seconds after starting the
salt minion test.
The summary of the
Public bug reported:
https://github.com/openstack/nova/blob/b992b90d73ab745b41924db9c2173f6cecb9d85e/nova/cmd/manage.py#L859
That should be using the "version2" parameter since the "version"
parameter is deprecated.
** Affects: nova
Importance: Medium
Status: Triaged
** Tags: db
Public bug reported:
I am seeing this error often on Neutron side, I am not using
floatingips, even blocking the action in the policies doesn't fix the
issue neither.
WARNING neutron.pecan_wsgi.controllers.root [req user id - default
default] No controller found for: floatingips - returning
Public bug reported:
https://docs.openstack.org/nova/latest/cli/nova-manage.html#nova-api-
database
nova-manage api_db sync
Sync the api cells database up to the most recent version. This is the
standard way to create the db as well.
There are three things wrong here:
1. It's missing the
The bug reported provided more information in the original bug report
and from it seems [1] that the nova code is heavily diverged from
upstream. Based on [1], the fact that I failed to reproduce the problem
and that the reporter set the original bug to Invalid state I set this
to invalid as
Public bug reported:
### Prerequisites ###
1) VM server is up and running on Nova node
2) Port 80 is added to security groups
3) HTTPD on VM is up and running
4) “Big File” (~100MB) is located in “/var/log/html”
For more details see:
Reviewed: https://review.openstack.org/576046
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=0ffd2529b1c70d04315ee1a7be755fe020645be0
Submitter: Zuul
Branch:master
commit 0ffd2529b1c70d04315ee1a7be755fe020645be0
Author: Takashi NATSUME
Date: Mon Jun 18 16:28:22 2018
Public bug reported:
It appears the neutron-rally-neutron job is failing intermittently with:
2018-06-25 21:27:31.654 4361 ERROR rally.task.engine [-] Invalid Task:
PluginNotFound: There is no plugin
`NeutronTrunks.create_and_list_trunk_subports` in in any platform.
For example [1]
Reviewed: https://review.openstack.org/577669
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=dc51fc509428b441423b2008a62aa2ab3fe00a01
Submitter: Zuul
Branch:master
commit dc51fc509428b441423b2008a62aa2ab3fe00a01
Author: François Magimel
Date: Sun Jun 24 21:52:42
Reviewed: https://review.openstack.org/577090
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=9b6b559eca9822fa887f7cac6b051be126c1d22f
Submitter: Zuul
Branch:master
commit 9b6b559eca9822fa887f7cac6b051be126c1d22f
Author: Ivan Kolodyazhny
Date: Thu Jun 21 11:19:33
stable/pike (16.1.4) is also affected by this.
** Also affects: nova (Ubuntu)
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).
Public bug reported:
https://developer.openstack.org/api-ref/placement/#list-allocation-
candidates
The 'traits' parameter has been added in the response since microversion 1.17.
But it is missing in the API reference.
And the parameter list is not sorted by microverions.
** Affects: nova
Fix proposed to branch: master
Review: https://review.openstack.org/578040
** Changed in: nova
Status: Opinion => In Progress
** Changed in: nova
Assignee: (unassigned) => do3meli (d-info-e)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
### User Workflow (Documentation) ###
According documentation
https://docs.openstack.org/neutron/queens/admin/config-qos.html in order to:
1) Set QoS to Floating IP:
openstack floating ip set --qos-policy bw-limiter
d0ed7491-3eb7-4c4f-a0f0-df04f10a067c
2) Remove Floating
Reviewed: https://review.openstack.org/576923
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f2b40f2cecc116906e77d69797c0c6877bd5b4d
Submitter: Zuul
Branch:master
commit 9f2b40f2cecc116906e77d69797c0c6877bd5b4d
Author: aojeagarcia
Date: Wed Jun 20 18:53:36 2018
Public bug reported:
node_staging_uri configuration option needs a value which always starts with
file:///.
If by mistake operator sets value of node_staging_uri without file:/// then
import api fails with 500 internal server error.
Steps to reproduce:
1. set below value to node_staging_uri in
Public bug reported:
When external bridge is configured in Neutron, the FIP Agent Gateway
port 'fg-' is tagged as a DEAD port with Vlan id of 4095.
This issue is seen in Pike.
It seems that there was fix that recently merged in neutron shown below
https://review.openstack.org/#/c/564825/10
32 matches
Mail list logo
