https://review.openstack.org/#/c/537411/ is the last part of the
rollback to 10.1 for openstack ansible.
** Changed in: openstack-ansible
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Very close to this: https://bugs.launchpad.net/barbican/+bug/1734329
** Also affects: openstack-ansible
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).
Public bug reported:
In master, a problem seem to have appeared recently.
In our tests, we run the following task [1], running a db_sync --contract.
That task runs the same for centos, ubuntu, and suse.
However on SUSE (maybe a different version of mysql is packaged, I have to
check) I get the
According to our bug triagers, the error doesn't seem to appear anymore.
There was probably a change that didn't mention this bug.
Could the neutron team verify if that's ok to close for neutron too?
** Changed in: openstack-ansible
Status: New => Invalid
--
You received this bug
This is an upstream issue. Linking bug to nova.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: openstack-ansible
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
Hello,
This issue (Table 'neutron.ml2_vlan_allocations' doesn't exist") appears
in the neutron.conf after a deploy in openstack-ansible. Our deploy is
working fine, and I see no functional test issues, so this seems a low
priority issue. This message appears on both trusty
neutron-dynamic-routing is installed by default in our neutron venvs, so
we are impacted by this issue too.
** Also affects: openstack-ansible
Importance: Undecided
Status: New
** Changed in: openstack-ansible
Status: New => Confirmed
--
You received this bug notification
Ignore this comment, it was fixed because it was master and the upstream
bug was fixed.
** Changed in: openstack-ansible
Status: New => Incomplete
** Changed in: openstack-ansible
Status: Incomplete => Confirmed
** Changed in: openstack-ansible
Status: Confirmed => Fix
** No longer affects: openstack-ansible
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1509312
Title:
unable to use tenant network after kilo to liberty update due to port
security
** Changed in: openstack-ansible
Status: In Progress => Fix Released
** Changed in: openstack-ansible
Assignee: Swapnil Kulkarni (coolsvap) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
10 matches
Mail list logo