Marked this as Invalid since this isn't really a bug, just a request to
investigate improving this code improvement. I've done the
investigation and couldn't find a good way to improve it
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because
Public bug reported:
If a VM with a floating IP is deleted while concurrently deleting the
floating IP (i.e. "nova delete" and "neutron floatingip-delete") the VM
may go into error state.
Nova receives a 500 error code from neutron because neutron fails to
delete the port and the following stack
Public bug reported:
Using Kilo 2015.1.2 and Glance Client 0.17.0:
Using two users (demo in the demo tenant, alt_demo in the alt_demo
tenant, neither have the admin role), I am able to create an image with
is_public set to False as the demo user/tenant, and then show data/use
that image to
This is complete now:
https://pypi.python.org/pypi/networking_arista/2015.2.0
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
The 'openstack' cli tool defaults to keystone version 2.0. When pointed
to a v3 endpoint, it fails like this:
$ openstack service list
ERROR: openstack
This can easily be resolved by setting OS_IDENTITY_API_VERSION=3 --
that's not obvious from the error message, though,
** Changed in: neutron
Status: Fix Committed => 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/1512937
Title:
CREATE_FAILED status due to 'Resource CREATE failed:
Public bug reported:
The file "network_data.json" is not found in the folder
"openstack/2015-10-15/" of config drive, only in "openstack/latest/".
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Not able to ping v6 address of vm on a different network. With legacy router.
Setup has one controller/network node and two compute nodes.
Steps:
0. Add security rules to allow ping traffic.
neutron security-group-rule-create --protocol icmp --direction ingress
** Changed in: neutron
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1512937
Title:
CREATE_FAILED status due to 'Resource CREATE failed:
Public bug reported:
http://logs.openstack.org/96/237896/4/gate/gate-neutron-dsvm-
api/6e1d5c7/logs/screen-q-svc.txt.gz#_2015-11-04_20_14_34_810
2015-11-04 20:14:34.810 INFO neutron.api.v2.resource [req-da6d1e90-412c-
4c4b-b1ea-b4c5438c9665 FWaaSExtensionTestJSON-1462602448
Public bug reported:
We found our gate failed with following information
3:42.778 ERROR neutron_lbaas.services.loadbalancer.agent.agent_manager
[req-ebb92ee8-2998-4a50-baf1-8123ce76b071 admin admin] Create vip
e3152b05-2c41-40ac-9729-1756664f437e failed on device driver haproxy_ns
2015-11-05
** 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/1510817
Title:
stable/liberty branch creation request for
New question #273752 on anvil:
https://answers.launchpad.net/anvil/+question/273752
Hi, I recently used Anvil to build openstack kilo packages on centos 7.1
server. All bootstrap/prepare/build steps went well and built rpms were saved
in local repos.
But when I tried to use some packages to
Keystone is not responsible for the OSC command.
Tagging OSC, I agree the error message can be further improved
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
** Changed in: python-openstackclient
[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).
You have been subscribed to a public bug:
We found our gate failed with following information
3:42.778 ERROR neutron_lbaas.services.loadbalancer.agent.agent_manager
[req-ebb92ee8-2998-4a50-baf1-8123ce76b071 admin admin] Create vip
e3152b05-2c41-40ac-9729-1756664f437e failed on device driver
Public bug reported:
1. version:
nova 12.0.0 Liberty
2. As mentioned in
https://blueprints.launchpad.net/nova/+spec/allocation-ratio-to-resource-tracker,
cpu/mem allocation ratio have already been moved to resource tracker.
And disk allocation ratio MUST be moved as same.
** Affects: nova
This has been fixed in Liberty - https://review.openstack.org/214434.
Because kilo is security-supported only marking this one as invalid.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
So it is packstack related issue - please refer to
https://bugzilla.redhat.com/show_bug.cgi?id=968310
** Bug watch added: Red Hat Bugzilla #968310
https://bugzilla.redhat.com/show_bug.cgi?id=968310
** Changed in: nova
Status: Confirmed => Invalid
** Changed in: nova
Assignee:
Public bug reported:
Currently, both left & leftid are filled with external_ip automatically. But
sometimes, user may want to specify the leftid as they desired, such as an
email address.
It would be better if this can be supported.
Pre-conditions: None
Step-by-step reproduction steps:
1)
If the bridge doesn't exists the exception is still not caught , which
is the right behaviour according to me because the agent tries to get
the ancillary ports only if it detects ancillary bridges. We were seeing
some race in the test clean up probably., which disappeared since I get
0 hit now. I
*** This bug is a duplicate of bug 1477829 ***
https://bugs.launchpad.net/bugs/1477829
Sorry I checked the wrong branch :-(
It was fixed during Liberty.
** Description changed:
allowed_address_pairs validator raises 500 when non-list value is specified
from users.
In the following
I would question the issue itself.
Processing 860 networks in 30 seconds is much much better than Juno has.
Since we had rootwrap demon, processing time reduced significantly.
You can increase num_sync_threads in dhcp_agent.ini from default value
of 4 to higher and see if it helps.
** Changed
Changed this to invalid/low as this is a defect against kilo which is
now (according to [1]) security supported. This needs to be retested
with liberty/master and re-filed.
[1] https://wiki.openstack.org/wiki/Releases
** Changed in: neutron
Status: Triaged => Opinion
** Changed in:
Public bug reported:
When a driver is specified using the full name (as in, the old config file is
used), for example if I have:
driver = keystone.contrib.federation.backends.sql.Federation
I get a deprecation warning:
31304 WARNING oslo_log.versionutils [-] Deprecated: direct import of
Public bug reported:
[Summary]
the container can not be pinged via name space, after 860
tenants/networks/container created
[Topo]
1 controller, 2 network nodes, 6 compute nodes, all in ubuntu 14.04
(openstack version is 2015.1.2, linux kernel version is 3.19.0-31)
root@ah:~# uname -a
Linux
Public bug reported:
[Summary]
need to wait more than 30 seconds before the network namespace can be checked
on network node when creating network(with 860 tenant/network/instance
created)
[Topo]
1 controller, 2 network nodes, 6 compute nodes, all in ubuntu 14.04
(openstack version is
** Also affects: horizon/liberty
Importance: Undecided
Status: New
** Changed in: horizon/liberty
Assignee: (unassigned) => Matthias Runge (mrunge)
** Changed in: horizon
Importance: Undecided => High
** Changed in: horizon/liberty
Importance: Undecided => High
** Changed
Marking this as invalid, as I think this is the correct behaviour.
There was talk of adding the ability to resize a volume during resize
using BDM, but thats a spec.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
*** This bug is a duplicate of bug 1477829 ***
https://bugs.launchpad.net/bugs/1477829
Public bug reported:
allowed_address_pairs validator raises 500 when non-list value is specified
from users.
In the following example, a user specified True for allowed_address_pairs by
mistake.
In this
Public bug reported:
Using a DS that includes ec2 metadata with an ephemeral disk, even if
the ephemeral disk is not formatted with a filesystem, cc_mounts adds an
fstab entry that is likely invalid and potentially breaking reboot in
some cases. I've seen this affect Debian based images and if
Public bug reported:
The version of oslo.log referenced leads to this error and keystone
won't start:
2015-11-04 15:36:00.423 6292 CRITICAL keystone [-] AttributeError: type object
'deprecated' has no attribute 'MITAKA'
2015-11-04 15:36:00.423 6292 ERROR keystone Traceback (most recent call
** Also affects: fuel-plugins
Importance: Undecided
Status: New
--
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/1512744
Title:
Unable to retrieve LDAP
Public bug reported:
The version of oslo.log referenced leads to this error and keystone
won't start:
2015-11-04 15:36:00.423 6292 CRITICAL keystone [-] AttributeError: type object
'deprecated' has no attribute 'MITAKA'
2015-11-04 15:36:00.423 6292 ERROR keystone Traceback (most recent call
It is master kilo release 2015.1.2
** Changed in: neutron
Status: Invalid => 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/1513048
Title:
the container can not be pinged
Incomplete seems better as we need more information in Liberty.
** Changed in: neutron
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1513048
Title:
It seems an explanation is required when updating the bug status
** 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/1513048
Title:
the
** Changed in: networking-cisco
Milestone: None => 2.0.0
** Changed in: networking-cisco/kilo
Status: New => Confirmed
** Changed in: networking-cisco/kilo
Importance: Undecided => Medium
** Changed in: networking-cisco
Milestone: 2.0.0 => None
** No longer affects:
It is master kilo release 2015.1.2
** Changed in: neutron
Status: Opinion => 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/1513041
Title:
need to wait more than 30 seconds
Meh, this might actually break volume detach in the compute manager:
connection_info = jsonutils.loads(bdm.connection_info)
So let's just ignore this as won't fix for now.
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => In Progress
** Changed in: cloud-init
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: Dan Watkins
Public bug reported:
Somewhere between cloud-init-0.7.4 and cloud-init-0.7.5, the cloud-init
runtime was refactored a bit so that certain cloud-init data is dropped
statically into certain locations (/var/lib/cloud/data and /run/cloud-
init) rather than locations in the configured cloud_dir.
The
Public bug reported:
Cloud administrators have monitoring systems externally placed watching
different types of resources of their cloud infrastructures. A cloud
infrastructure is comprehended not exclusively by an OpenStack instance
but also other components not managed by and possibly not
It seems an explanation is required when updating the bug status
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1513041
Title:
need
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1499856
Title:
latest doa breaks with new db
** Changed in: nova
Status: Invalid => Confirmed
** Changed in: nova
Importance: High => Medium
--
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/1491949
Title:
Public bug reported:
While debugging bug 1489581 we were tracking some BDM updates in the
cells API code:
http://logs.openstack.org/66/241366/1/check/gate-tempest-dsvm-
cells/1d7551e/logs/screen-n-cell-region.txt.gz#_2015-11-03_21_44_58_273
** Also affects: networking-cisco/kilo
Importance: Undecided
Status: New
** Changed in: networking-cisco/kilo
Milestone: None => 1.1.0
** Changed in: networking-cisco
Milestone: 1.1.0 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Tags added: networking-vsphere
** Project changed: nova => networking-vsphere
** Changed in: networking-vsphere
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
When trying to start neutron q-lbaas on ubuntu devstack we receive this
error and was unable to track it to source:
ubuntu@nov-dvs-241480-1:~/devstack$ /usr/local/bin/neutron-lbaas-agent
--config-
file /etc/neutron/neutron.conf
This is not a valid situation anymore.
** Changed in: keystone
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/1425108
Title:
This is not valid in Kilo, as the issue is addressed per Swami in
comment #10.
Kilo is under security only patches now, so it's not clear we can merge
this there.
** Also affects: neutron/kilo
Importance: Undecided
Status: New
** Changed in: neutron
Status: New => Invalid
**
Public bug reported:
The cinder quota on gigabytes is the sum of both volumes and snapshots.
This is not correctly reflected in the create volume dialog, which
allows the user to attempt to create volumes when there is not enough
quota available, which results in a useless error message.
To
53 matches
Mail list logo
