Public bug reported:
When doing a HTTP GET against s3tokens and ec2tokens endpoint we should
get a 405 method not allowed but because the get method is getting
enforced we get a 500 internal server error instead.
AssertionError: PROGRAMMING ERROR: enforcement
Public bug reported:
when doing live migrations for bfv instances the disk remaining in the
nova log says 100 even if there is no disk to migrate
** Affects: nova
Importance: Undecided
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
if an operator has a compute node and reinstalls it but forget to do a
"openstack compute service delete " first (that would wipe the nova-
compute service record and the resource provider in placement) the
reinstalled compute node with the same hostname happily reports it's
Public bug reported:
when managing allowed address pairs in horizon for a neutron port and
you create two identical ip_address but with different mac_address,
horizon crashes because the id in the table is the same, see below
traceback.
solution is to concat mac_address if set in the ID for that
I have no idea what I was referring to there so will set as invalid,
past me should have posted more details :p
** 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.
Public bug reported:
This bug is related to resize with the libvirt driver
If you are performing a resize and it fails the
_cleanup_remote_migration() [1] function in the libvirt driver will try
to cleanup the /var/lib/nova/instances/_resize directory on the
remote side [2] - if this fails the
Public bug reported:
The glance requirement for sqlalchemy says >= 1.0.10 but using 1.3.2
gives error when trying to db sync
this is xena release versions
openstack-glance-21.1.0-1.el8.noarch
python3-glance-store-2.3.0-2.el8.noarch
python3-glanceclient-3.5.0-1.el8.noarch
Public bug reported:
When hosting a large amount of routers and/or networks the RPC calls
from the agents can take a long time which requires us to increase the
rpc_response_timeout from the default of 60 seconds to a higher value
for the agents to not timeout.
This has the side effect that if a
That seems about right. We upgraded from Train to Victoria recently so I
would assume this was related to that. Ideally it should have handled
the word 'master' as a transition and perhaps converted any
/var/lib/neutron/ha_confs//state files or similar since the
service did not work after one
Public bug reported:
When using L3 HA enabled for routers sometimes the state transitions
reports master instead of primary causing a KeyError in the
TRANSLATION_MAP. This causes the agent to fail and stop processing them
all together, if you then move a router (haven't tried for new routers)
to
** 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/1795280
Title:
netns deletion on newer kernels fails with errno 16
Status in
Public bug reported:
The RBD utils get_pool_info() function raises an
processutils.ProcessExecutionError from oslo.concurrency if it fails.
That error message contains the Ceph username and the fact that it's
running Ceph in the error message that a end-user can view.
| fault
Public bug reported:
This is a separation from the discussion in this bug
https://bugs.launchpad.net/neutron/+bug/1815989
There comment https://bugs.launchpad.net/neutron/+bug/1815989/comments/52 goes
through in
detail the flow on a Train deployment using neutron 15.1.0 (controller) and
15.3.0
Think this isn't a bug but was related to SELinux. This issue happend
when I upgraded nova on our compute node and then this occured. So I
removed the @db.select_db_reader_mode decorator usage in
nova/objects/service.py to make it start.
I then proceeded to upgrade Neutron and Ceilometer on the
** 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/bugs/1869929
Title:
RuntimeError: maximum recursion depth
** Changed in: puppet-neutron
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/1585699
Title:
Neutron Metadata Agent Configuration - nova_metadata_ip
Thanks Ryan, I'll mark it as invalid and wait until we are on Stein.
** 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/1828406
Title:
Public bug reported:
Rocky with Ryu, dont have a reproduce on this one or don't know what
caused it in the first place.
python-neutron-13.0.3-1.el7.noarch
openstack-neutron-openvswitch-13.0.3-1.el7.noarch
python2-neutron-dynamic-routing-13.0.1-1.el7.noarch
Public bug reported:
Lost connection to the peer and the hold timer expired but it never
tried to recover.
2019-05-09 13:26:24.921 2461284 INFO bgpspeaker.speaker [-] Negotiated hold
time 40 expired.
2019-05-09 13:26:24.922 2461284 INFO bgpspeaker.peer [-] Connection to peer
lost, reason:
** Changed in: nova/rocky
Status: Fix Committed => 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/1768807
Title:
Live Migration failure: 'ascii'
Public bug reported:
When installing a new bgp-dragent and it's disabled by default
(enable_new_agents=False) and you try to enable it, it throws an error
on the first attempt then works on the second.
openstack network agent set --enable 8139752e-5f08-424b-9b99-09772da3ec7d #
fails
openstack
Public bug reported:
This is probably not neutron related, but need help with some input.
On a 3.10 kernel on CentOS 7.5 by simply creating a network and deleting
it properly terminates all processes, removes interfaces and deletes the
network namespace.
[root@controller ~]# uname -r
Public bug reported:
When upgrading to Rocky we noticed that the pecan requirement is:
pecan!=1.0.2,!=1.0.3,!=1.0.4,!=1.2,>=1.1.1 # BSD
https://github.com/openstack/neutron/blob/stable/rocky/requirements.txt#L11
But when having python2-pecan-1.1.2 which should satisfy this requirement we
get
Public bug reported:
Nova is using async_ introduced in oslo.db 4.40.0 but requirements.txt says
oslo.db>=4.27.0
https://github.com/openstack/oslo.db/commit/df6bf3401266f42271627c1e408f87c71a06cef7
So if you still have an old oslo.db version from queens that satisfies
that requirement services
Public bug reported:
When upgrading from Keystone queens to rocky the requirements.txt for
rocky says oslo.log >= 3.36.0 but versionutils.deprecated.ROCKY is not
introduced until 3.37.0
Should bump requirements.txt to atleast 3.37.0
Error when running db sync:
Traceback (most recent call last):
Public bug reported:
When a end user wants to use the self-service feature to changing their
own password it's very common that they go under Identity -> Users and
press the "Change password" button for their own user which does not
work unless they are admin because it calls update_user keystone
to troubleshoot this here or on
IRC (tobias-urdin).
Best regards
Tobias
[1]
https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged
[2] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133499.html
** Affects: neutron
Importance: Undecided
Status
Public bug reported:
The vpnaas and dynamic routing projects are missing the neutron-tempest-
plugin in test-requirements.txt
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
neutron-dynamic-routing
The implementation of BGP with Ryu supports IPv4 and IPv6 peers but the
MP-BGP capabilities is announced based on if the peer is a v4 or v6
address.
If you want to use a IPv4 peer but announce IPv6 prefixes this will not
work because in
Public bug reported:
Running rally caused subnets to be created without a network_id causing
this AttributeError.
OpenStack Queens RDO packages
[root@controller1 ~]# rpm -qa | grep -i neutron
python-neutron-12.0.2-1.el7.noarch
openstack-neutron-12.0.2-1.el7.noarch
Public bug reported:
Distro: OpenStack Queens running on Ubuntu 16.04
>From this commit [1] nova now needs access to keystone to perform quota
(this bug is mostly related to issue we had with quota update).
When keystone is not available the nova-api (running in eventlet) tries
to use the
** Changed in: puppet-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 (keystone).
https://bugs.launchpad.net/bugs/1649616
Title:
Keystone Token Flush job does
Was caused by our internal infrastructure sending an invalid API
request. I'm sorry for the hassle, marking as invalid.
** Changed in: nova
Status: New => Invalid
** Changed in: nova (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Booting a nova instance with a block device as root volume.
** 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:
New bug introduced when upgrading nova-api on Ubuntu 14.04 for cloud archive
liberty stable repo.
(deb http://ubuntu-cloud.archive.canonical.com/ubuntu trusty-updates/liberty
main)
2016-11-23 11:31:15.341 1600 ERROR nova.api.openstack.extensions
Moving the pid files for the affected router solves the issue.
mv /var/lib/neutron/ha_confs/c1cc1a5d-c0ef-47b7-8d5c-88403e134725.* /root
Found fix thanks to frickler on IRC. It has been merged for liberty
https://review.openstack.org/#/c/299138/3
** Changed in: cloud-archive
Status: New
Public bug reported:
After upgrading to 7.0.4 I have several routers that fails to spawn the
keepalived process.
The logs say
2016-05-20 11:01:11.181 23023 ERROR neutron.agent.linux.external_process [-]
default-service for router with uuid c1cc1a5d-c0ef-47b7-8d5c-88403e134725 not
found. The
Resolved by changing the no_path_retry option in multipath.conf from "queue" to
"0".
The issue was that that when IO was queued and the path was about to be removed
it was blocked and was never removed, so the flushing of the multipath device
failed because the multipath device was in-use by
Public bug reported:
Hello,
When issuing a live migration between kvm nodes having multipath cinder
volume it sometimes hangs and causes qemu-kvm to crash, the only
solution is a restart of the kvm node.
Sometimes when live migrating you get stuck when it tries to migrate the active
RAM, you
Setting to invalid to clean up and since it seems like I was the only
one having this issue.
** 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
Public bug reported:
We have compute nodes with a very small amount of disk so we deploy our
instances to Cinder volumes with a Dell backend.
The issue is that when creating instances with a Cinder volume it still gets
counted towards the local storage used (local_gb_used in compute_nodes table
Public bug reported:
Hello,
Upgrading from Keystone Juno to Kilo breaks my build.
I have had close looks warnings and debug output in keystone.log and read notes
on
https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Identity_.28Keystone.29
but without any luck, I could simply bypass
42 matches
Mail list logo
