** Also affects: charm-keystone
Importance: Undecided
Status: New
** Changed in: charm-keystone
Status: New => Fix Committed
** Changed in: charm-keystone
Importance: Undecided => Critical
** Changed in: charm-keystone
Assignee: (unassigned) => David Ames
** Changed in: charm-ovn-central
Status: Fix Committed => Fix Released
** Changed in: charm-neutron-api-plugin-ovn
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:
** Changed in: charm-keystone
Status: Fix Committed => 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/1859844
Title:
Impossible to rename the De
** Changed in: charm-neutron-openvswitch
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/1834213
Title:
After kernel upgrade, nf_conntrack_ipv
** Changed in: charm-neutron-openvswitch
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/1832021
Title:
Checksum drop of metadata traffic on i
*** This bug is a duplicate of bug 1722584 ***
https://bugs.launchpad.net/bugs/1722584
Brian,
Thanks for getting back to me. It seems this is a duplicate of LP Bug
#1722584 [0]. And the explanation for my running into it is that we have
not yet pushed your reversion into our Ubuntu packaging.
Public bug reported:
When an isolated network using provider networks for tenants (meaning
without virtual routers: DVR or network node), metadata access occurs in
the qdhcp ip netns rather than the qrouter netns.
The following options are set in the dhcp_agent.ini file:
force_metadata = True
ena
** Changed in: charm-nova-compute
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/1794564
Title:
Apparmor denies /usr/bin/nov
** Changed in: charm-nova-compute
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/1750829
Title:
RFE: libvirt: Add ability to
** Changed in: charm-neutron-api
Status: Fix Committed => Fix Released
--
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/1788631
Title:
KeyError: 'used' securit
Public bug reported:
With glance v2 and swift as the store, glance is unable to delete images.
Tested with Queens and Rocky.
Code snippit:
import glanceclient.v2 as glance_clientv2
glance = glance_clientv2.Client("2", session=keystone.session)
image = glance.images.create(name=image_name, disk_fo
Discussion with roaksoax about this and it seems likely this is a cloud-
int / netplan problem. I have added cloud-init and maas just to be
thorough.
When bionic is deployed using MAAS 2.3.0 using a static network config
the DNS search domain is missing from the netplan configuration and or
system
** Changed in: charm-neutron-gateway
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/1761536
Title:
Nova compute manager fail
** Changed in: charm-neutron-openvswitch
Status: New => Invalid
--
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/1761536
Title:
Nova compute manager failed to creat
onnection to
MySQL server during query') [SQL: u'SELECT 1']
2018-04-25 17:49:33.562 617800 ERROR oslo_db.sqlalchemy.engines
Next steps:
Please redeploy with neutron-gatway aa-profile-mode=complain while we fix the
apparmor profile bug. The current deploy has been tainted by all of our
Public bug reported:
Setup:
Pike neutron 11.0.2-0ubuntu1.1~cloud0
OVS 2.8.0
Jumbo frames setttings per:
https://docs.openstack.org/mitaka/networking-guide/config-mtu.html
global_physnet_mtu = 9000
path_mtu = 9000
Symptoms:
gre_sys MTU is 1472
Instances with MTUs > 1500 fail to communicate across
n: charm-openstack-dashboard
Milestone: None => 18.02
** Changed in: charm-neutron-gateway
Assignee: David Ames (thedac) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net
Re-ran rally and saw this go by:
2017-12-07 00:02:25.399 5255 INFO rally.task.runner [-] Task
a502ee62-c31b-4333-8169-f6a3d07d592e | ITER: 74 START
2017-12-07 00:02:25.915 5252 INFO rally.task.runner [-] Task
a502ee62-c31b-4333-8169-f6a3d07d592e | ITER: 67 END: OK
2017-12-07 00:02:25.927 5252 IN
Xav,
In other deploys we have seen either of the following used:
user_id_attribute=cn
or
user_id_attribute=sAMAccountName
Docs use cn:
https://docs.openstack.org/keystone/latest/admin/identity-integrate-with-ldap.html
I don't think this is a charm bug. It is either configuration or
upstream key
The root cause for this is HAProxy timing out and terminating the TCP
session. The hint in the error was the EOF:
SSLError: SSL exception connecting to
https://keystone-.net:5000/v3/auth/tokens: ("bad handshake:
SysCallError(-1, 'Unexpected EOF')",)
Public bug reported:
We had several instances go into error state on bootstack with the
following traceback:
2014-08-17 22:12:37.022 1232 ERROR nova.api.openstack.wsgi
[req-068c2700-29a4-46ec-a9f7-9e956c06f3c6 4e68a0dd10e04db5b57c917ca8c521b1
d97d645e7867484b81311b7f9ee2ab15] Exception handlin
Public bug reported:
Running into this bug intermittently.
2014-08-04 23:24:43.520 4038 ERROR neutron.agent.dhcp_agent [-] Unable to
enable dhcp for 415a0839-eb05-4e7a-907c-413c657f4bf5.
2014-08-04 23:24:43.520 4038 TRACE neutron.agent.dhcp_agent Traceback (most
recent call last):
2014-08-04 23
22 matches
Mail list logo
