** Also affects: solum
Importance: Undecided
Status: New
** Changed in: solum
Assignee: (unassigned) => yuyafei (yu-yafei)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: networking-infoblox
Importance: Undecided
Status: New
** Changed in: networking-infoblox
Assignee: (unassigned) => hongzhezheng (zheng-hongzhe32)
** Also affects: python-barbicanclient
Importance: Undecided
Status: New
** Changed in:
Reviewed: https://review.openstack.org/330865
Committed:
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=cd423e268491398c06aa34197f2b0c871f2dd90b
Submitter: Jenkins
Branch:master
commit cd423e268491398c06aa34197f2b0c871f2dd90b
Author: YAMAMOTO Takashi
Public bug reported:
The following lines are missing ',':
1. However every case is different and you are invited to seek guidance from
Neutron core reviewers about what steps to follow.
2. However they are still quite happy to answer any questions you might have
about vulnerability management
** Also affects: devstack
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1595440
Title:
neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd
Public bug reported:
As per the comments on [1], the neutron-vpnaas check and gate pipelines
include a fullstack job that tests the base Neutron L3 agent. This job
should be replaced/augmented to actually deploy and test VPNaaS agent
itself.
** Affects: neutron
Importance: High
As Cinder will use encryptors, nova/encryptors is copied to os-brick. We
also need to import this fix into os-brick.
** Also affects: os-brick
Importance: Undecided
Status: New
** Changed in: os-brick
Assignee: (unassigned) => Lisa Li (lisali)
--
You received this bug
Public bug reported:
A few of recent occurrences:
http://logs.openstack.org/92/320092/43/check/gate-tempest-dsvm-neutron-
dvr/cf32111/logs/testr_results.html.gz
http://logs.openstack.org/92/320092/43/gate/gate-tempest-dsvm-neutron-
full/ecf1013/logs/testr_results.html.gz
We should nip this in
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
https://review.openstack.org/329288
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/glance" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option
Reviewed: https://review.openstack.org/330443
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=969309ffae15a56474e5a66100979a6bd76c356f
Submitter: Jenkins
Branch:master
commit 969309ffae15a56474e5a66100979a6bd76c356f
Author: Niall Bunting
Date:
Reviewed: https://review.openstack.org/196482
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=89a61ab8f4602e018763afb173e1a862f151a222
Submitter: Jenkins
Branch:master
commit 89a61ab8f4602e018763afb173e1a862f151a222
Author: Tomoki Sekiyama
Reviewed: https://review.openstack.org/335530
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=00f3ab1f132de6b701c7832626457ad51dd265b6
Submitter: Jenkins
Branch:master
commit 00f3ab1f132de6b701c7832626457ad51dd265b6
Author: Ryan Moats
Date: Wed
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu)
Assignee: (unassigned) => Billy Olsen (billy-olsen)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Reviewed: https://review.openstack.org/313846
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0856095c82b3ef73a0376c741d1a3a61b1a077a6
Submitter: Jenkins
Branch:master
commit 0856095c82b3ef73a0376c741d1a3a61b1a077a6
Author: Fang Zhen
Date:
Reviewed: https://review.openstack.org/289925
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=ab131ee0af32d9eea04f1403a9a134a070e80e02
Submitter: Jenkins
Branch:master
commit ab131ee0af32d9eea04f1403a9a134a070e80e02
Author: Jens Rosenboom
Date:
Reviewed: https://review.openstack.org/336907
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b2de391b215482fb90ac89378a2af4d8a3e32204
Submitter: Jenkins
Branch:master
commit b2de391b215482fb90ac89378a2af4d8a3e32204
Author: QunyingRan
Date:
Public bug reported:
When a duplicate/conflicting entry is attempted to be created, an error
occurs, but this error just says that the entry is a duplicate. Many
deployers are creating multiple keystone objects simultaneously, and so
it can get confusing when trying to decipher what error goes
Public bug reported:
When the L3 agent is dead, if the gateway is removed, the snat namespace
and its rules are not properly cleaned when agent restarts.
Even though the patch https://review.openstack.org/#/c/326729/ addresses
the cleanup of the snat namespace, it does not remove the redirect
Public bug reported:
More on https://bugs.launchpad.net/neutron/+bug/1555042/comments/10
** Affects: neutron
Importance: Wishlist
Status: Confirmed
** Tags: deprecation l3-ha low-hanging-fruit
** Tags added: deprecation l3-ha low-hanging-fruit
** Changed in: neutron
Public bug reported:
The destructive buttons in table are styled to be red to give the user a
warning to process.
The destructive buttons on confirmation modal don't have this styling but they
should be consistent everywhere.
For example, when you try to delete one instance, the Terminate
Public bug reported:
Have a look at http://developer.openstack.org//api-
ref/identity/v2/index.html
The version information here makes no sense, we do not have links to old
documents for the api at all. These links should not appear. Can we make
them configurable, please?
** Affects: keystone
Reviewed: https://review.openstack.org/219215
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e25151be3d71abc9b51cfc85b92b42b3e1162354
Submitter: Jenkins
Branch:master
commit e25151be3d71abc9b51cfc85b92b42b3e1162354
Author: YAMAMOTO Takashi
Public bug reported:
When listing server details, instance_get_all_by_filters() can be
invoked with duplicates in the columns_to_join list. This can result in
both a join and a separate query against the potential "manual_join"
tables.
This appears to have been introduced with the behavior in
** Changed in: networking-midonet
Status: New => 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/1596813
Title:
stable/mitaka branch creation request for
** Changed in: neutron
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1564648
Title:
nova notifier should send first event immediately
Status in
Well, it's been a week, and I've had hundreds of successful deployments
(now on 2.0-beta11), whether i specify constraints or not. I'm marking
this as invalid.
I don't have much to go on for how this fixed itself. I didn't see
recent changes to cloud-init or the azure provider in late 2.0
** Project changed: neutron => python-neutronclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1599061
Title:
Some resources not listed in the help msg of quota-update command and
It's in another project, I already have a bug filed for that project to mock
the call.
I just thought this seemed odd and filed this here too.
Sorry about this.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1599032
Title:
qos for outbond traffic control
Status in neutron:
Invalid
Bug
Public bug reported:
When booting instance with a block_device_mapping with
source=blank,destination=local,tag=foo no entry is created in the
block_device_mapping table and the volume is not tagged. While the
former is existing normal behaviour, the latter is definitely a bug.
** Affects: nova
Public bug reported:
It would be nice to display a human-readable size (e.g.: gibibytes, mebibytes,
etc.) in
addition to showing number of bytes.
E.g.:
```
$ glance-replicator size az3:9292 --token $SECONDARY_AUTH_TOKEN
Total size is 39022543360 bytes (36.3 GiB) across 20 images
```
**
Public bug reported:
I think `glance-replicator size` should display a more informative error
message if no token was provided.
Currently it doesn't check for the no token case and then fails with an
HTTP 401 error:
```
$ glance-replicator size az3:9292
2016-07-04 09:58:58.675 31732 CRITICAL
See earlier comment
** Changed in: python-keystoneclient
Status: Triaged => Fix Released
** Changed in: keystone
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
Public bug reported:
We should check if `args is None` before doing `len(args)` to avoid a `object
of type
'NoneType'` has no len()` error.
Currently what happens:
```
$ glance-replicator size
2016-07-04 09:51:19.030 30204 ERROR glance.cmd.replicator [-] replication_size
size
Determine
That seems like a great example, are you still hitting this error. It's
a basic flow that is tested in our CI and unlikely to be a bug in
keystoneclient or auth.
** Changed in: python-keystoneclient
Status: New => Incomplete
** Changed in: python-keystoneclient
Status: Incomplete
** No longer affects: rally
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586268
Title:
Unit test: self.assertNotEqual in unit.test_base.BaseTest.test_eq
does not work in PY2
** No longer affects: cinder
** No longer affects: keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586268
Title:
Unit test: self.assertNotEqual in
Public bug reported:
When using IPv6 only deployment, including communication between glance-
api and glance-registry, glance client itself can make glance image-list
without problems, however, nova image-list fails with error 500. Same
applies is glance client is called by using v1 API:
** Changed in: astara
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/1259292
Title:
Some tests use assertEqual(observed,
Reviewed: https://review.openstack.org/322408
Committed:
https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=ccde9b3ba78e2dd0f2a726e6d23dba91f8ee061f
Submitter: Jenkins
Branch:master
commit ccde9b3ba78e2dd0f2a726e6d23dba91f8ee061f
Author: yuyafei
The doc impact for this bug appears to be relevant for neutron
documentation, and not for openstack-manuals. Closing as opinion in case
anyone with more neutron experience disagrees :)
** Changed in: openstack-manuals
Status: New => Opinion
--
You received this bug notification because
Public bug reported:
Description
===
Exception is thrown when creating container from nova.
Steps to reproduce
==
1. create a container image in glance
glance image-create --container-format=docker --disk-format=raw --name ubuntu
2. create a container
nova boot --flavor
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
CONFIRMED FOR: MITAKA
** Changed in: nova
Status: Expired => 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/1387812
Title:
Hypervisor summary shows
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen
1 - 100 of 246 matches
Mail list logo