Reviewed: https://review.openstack.org/652662
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=97549a2c416873ed0ef4a497095524516386579c
Submitter: Zuul
Branch:master
commit 97549a2c416873ed0ef4a497095524516386579c
Author: Stephen Finucane
Date: Mon Apr 15 14:34:55 2019
[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
[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
[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
*** This bug is a duplicate of bug 1750660 ***
https://bugs.launchpad.net/bugs/1750660
I think this is covered by
https://bugs.launchpad.net/keystone/+bug/1750660 and the default project
policies now account for domain scope.
** This bug has been marked a duplicate of bug 1750660
The v3 pr
Public bug reported:
Env: stable/queens
CentOS 7.5
kernel-3.10.0-862.11.6.el7.x86_64
There are many bottleneck locks in the agent extensions. For instance, l3 agent
extensions now have lock 'qos-fip' [1], 'qos-gateway-ip' [2], 'port-forwarding'
[3], 'log-port' [4]. For L2 agent, it is 'qos-port
Public bug reported:
Bug originally found by Jakub Libosvar and Assaf Muller:
In the case where a router replica transitions from standby to active
(but also in other cases), it might happen that the keepalived-state-
change-monitor encounters an error (for example in this case as a result
of a p
This information is in e.g.
https://docs.openstack.org/neutron/latest/install/controller-install-
option1-ubuntu.html and in similar documents for other distros also.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Eng
Hmm, from quick look it indeed looks that link to
https://docs.openstack.org/install-guide/launch-instance-networks-
provider.html may be missing in docs' menu. Maybe that should be checked
and fixed.
** Changed in: neutron
Status: Invalid => Confirmed
** Changed in: neutron
Importance:
This was regressed in Stein with change
https://review.openstack.org/#/c/603844/.
** Changed in: nova
Importance: Undecided => High
** Tags added: compute ironic neutron
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => Co
Public bug reported:
In the docu this part of neutron.conf is missing:
[oslo_concurrency]
lock_path = /var/log/neutron
The installation does not work without it.
This bug tracker is for errors with the documentation, use the following as a
template and remove or add fields as you see fit. C
Hi @Realtime,
It seems the document below is what you need:
https://docs.openstack.org/install-guide/launch-instance-networks-
provider.html
I am going to proceed to close this bug but please feel free to re-open
it if it still has problems.
** Changed in: neutron
Status: New => Invalid
Reviewed: https://review.openstack.org/644774
Committed:
https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=1192f185a5fd2fa6177655f157146488a3de81d1
Submitter: Zuul
Branch:master
commit 1192f185a5fd2fa6177655f157146488a3de81d1
Author: Morgan Fainberg
Date: Fri Mar 22 12:35:16
Public bug reported:
Unsetting '[DEFAULT] dhcp_domain' will result in the metadata
service/config drive reporting an instance hostname of '${hostname}None'
instead of '${hostname}'. This is clearly incorrect behavior.
** Affects: nova
Importance: Low
Assignee: Stephen Finucane (stephenf
Updating status for bug and also branch-specific status these are EOL
and many changes were merged performance-wise since
** Changed in: neutron
Status: Incomplete => Invalid
** Changed in: neutron/havana
Status: New => Invalid
** Changed in: neutron/grizzly
Status: New => I
** Changed in: neutron/havana
Status: Triaged => 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/1261510
Title:
Instance fails to spawn in tempest tests
Status in neutron:
** Changed in: neutron/havana
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/1244025
Title:
Remote security group criteria don't work in Midonet plugin
Sta
** Changed in: neutron/havana
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/1300785
Title:
[OSSA 2014-014] neutron allows security group rul
Public bug reported:
There may be a race condition involving dnsmasq startup and port
operations. What appears to happen is that dnsmasq is started but the
pid file isn't available when a port change occurs. The dhcp agent then
attempts to start a new dnsmasq instance even though the previous one
Public bug reported:
>From the debug logs, it looks like the dhcp agent continually checks for
an pid file for an external process that is not expected. e.g.:
DEBUG neutron.agent.linux.utils [-] Unable to access
/opt/stack/data/neutron/external/pids/17951cd9-d28e-
4ea9-9238-f97652690c59.pid {{(pi
Public bug reported:
I installed neutron (Rocky) in Ubuntu exactly following the documentation
https://docs.openstack.org/neutron/rocky/install/controller-install-ubuntu.html
I ended up with having no provider network.
Are there addional steps required to add a provider network? If so, why
is th
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification bec
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you
** 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.
https://bugs.launchpad.net/bugs/1362213
Title:
haproxy configuration spams logged-in users when no server
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug notification becau
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: In Progress => Won't Fix
** Changed in: neutron
Status: Wo
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you
Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification bec
** 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/1549547
Title:
LBaaS leaking password in DEBUG logs
Status in neutron:
Updating bug status
** 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/1600675
Title:
neutron-lbaas - LBaas v2 Pool creation f
** Also affects: charm-nova-compute
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/1824437
Title:
Issue with upgrade of nova-
32 matches
Mail list logo
