** Also affects: openstack (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openstack (Ubuntu Xenial)
Importance: Undecided => Critical
** Description changed:
- Once a deploy has completed using the OpenStack with Nova-LXD bundle
- there are attempts made to configure neutron automatically for a more
- turnkey experience. Problem is we do not want to mess with the existing
- lxdbr0 for this so a new bridge will need to be defined and configured
- to work with neutron.
+ [Impact]
+ Any user wishing to deploy a fully turnkey solution will fail to be able to
access external networks.
- The bug is currently a network is defined but not associated with any
- bridge from the host system.
+ [Test Case]
+ A full deploy with 'conjure-up openstack', once deployed login to horizon and
start an instance. Once sshing to that instance attempt to ping google.com or
do any sort of dns lookup.
+
+ [Regression Potential]
+ This doesn't impact the overall deploying of OpenStack but does call a few
'neutron' commands in order to define the internal and external networks.
+
+ [Additional Info]
+ Once a deploy has completed using the OpenStack with Nova-LXD bundle there
are attempts made to configure neutron automatically for a more turnkey
experience. Problem is we do not want to mess with the existing lxdbr0 for this
so a new bridge will need to be defined and configured to work with neutron.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575800
Title:
post processing neutron fails to configure network
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1575800/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
