Public bug reported:
I have set up an HA/DVR deployment of OpenStack Pike on Ubuntu 16.04 and
enabled FWaaS v1. After applying the Fix from Bug #1715395, firewall
rules get created in case of HA/DVR, but updates do not have any effect,
e.g. when you disassociate a firewall from a distributed
Public bug reported:
I have setup a fresh HA deployment of OpenStack Pike on Ubuntu 16.04. I
recognized in the logs that Nova sometimes fails during vm creation with
the following exception:
2017-09-11 09:31:28.909 5604 ERROR nova.api.openstack.identity
[req-6efab9e1-78f5-4e85-8247-686ff4f3568c
Public bug reported:
I have manually setup an HA/DVR deployment of OpenStack Pike on Ubuntu
16.04. The neutron.log gives me periodallcy the following exception:
2017-09-11 07:50:34.655 5830 ERROR oslo_db.api
[req-ed871530-109c-475a-8b52-9422b156d24b - - - - -] DB exceeded retry limit.:
Public bug reported:
I have setup a fresh OpenStack HA Pike environment on Ubuntu 16.04.3.
Live migration has been enabled and works so far. As storage backend I
am using Ceph v12.2.0 (Luminous). When you attach a secondary volume to
a vm and try to live migrate the vm to another host, it fails
Public bug reported:
I have manually setup a fresh OpenStack Pike HA environment based on
Ubuntu 16.04.3 in conjunction with DVR. Firewall creation works in case
of centralized routers, but when a firewall gets attached to a
distributed router, the firewall gets stuck in "PENDUNG UPDATE". The log
Public bug reported:
I have set up OpenStack Pike on Ubuntu 16.04.
Running:
$ su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini --subproject neutron_fwaas
upgrade head" neutron
fails with the following error:
INFO
Public bug reported:
I have set up OpenStack Pike on Ubuntu 16.04 in HA mode (2 controllers,
3 compute node). In the current Pike release, router and network
creation in HA mode fails. Whereas, creating routers in non-HA mode
succeeds.
The neutron-server.log gives me the following:
2017-08-31
I have found a solution. Adding the following configuration to my nova-
compute.cong solved the issue:
[libvirt]
hw_machine_type = "x86_64=pc-i440fx-xenial,i686=pc-i440fx-xenial"
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a
Public bug reported:
I am setting up OpenStack Ocata as HA deployment on Ubuntu 16.04. and I
am confronted with a heavy blocker. I have set up Keystone, Glance,
Nova, Neutron and Horizon. I am able to create and spawn a VM, but it
does not boot.
The block device is created and available in my
Public bug reported:
I am running OpenStack Newton on Ubuntu 16.04 using DVR. When I restart
a compute node, the FloatingIPs of those vms running on this node are
unreachable. A manual restart of the service "neutron-l3-agent" or
"neutron-vpn-agent" running in on node solves the issue.
I think
I think, this instruction is missing in the documentation and should be
added.
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Changed in: neutron
Status: Incomplete => 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/1531426
Title:
'dns_assignment' is not transmitted to neutron-dhcp-agent
Public bug reported:
This is a re-post of an issue that was reported for an older OpenStack
version. Unfortunately, I am confronted with the same problem in
OpenStack Mitaka. Keystone has a proper support for the case, when you
use SSL terminating via HAProxy.
Have a look here:
** Changed in: neutron
Status: Expired => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1476469
Title:
with DVR, a VM can't use floatingIP and VPN at the same time
Status
Public bug reported:
I am confronted with a strange problem... I have OpenStack Mitaka
running on Ubuntu 16.04. I have an HA deployment with 2 controllers and
3 compute nodes. I am using OpenSwitch. Everything is working, but after
some days I have a network issue on one compute nodes. I am
Public bug reported:
I am currently trying to update the horizon dashboard on Ubuntu 16.04
running OpenStack Mitaka using the new versions coming in from the
package repository.
aptitude update && aptitude safe-upgrade
Get: 1 http://archive.ubuntu.com/ubuntu xenial-proposed InRelease [247 kB]
Public bug reported:
When a port is created, a notify message gets sent to the neutron-dhcp-
agent. It contains the 'dns_name' but misses 'dns_assignment' causing
that internal DNS added in Liberty is not working as expected. Only a
restart of the neutron-dhcp-agent helps when the ports are
I reverted the configuration and started again from scratch. Its working
now. Unfortunately, I was not able to reproduce the problem. Regarding
to this post here (https://ask.openstack.org/en/question/86655/glance-
image-list-invalid-openstack-identity-credentials-in-l/), I think the
whole
Public bug reported:
I am running Ubuntu 14.04.3 and try to install OpenStack Liberty.
Keystone is running, but I had no luck with Glance. I always get a 401
and I am sure that all credentials ar correct:
The Keystone log contains:
2015-11-25 17:43:54.913446 2015-11-25 17:43:54.913 2255 WARNING
Public bug reported:
I am running OpenStack Kilo on Ubuntu 14.04 (Trusty). I have a separate
network node running Neutron. Sometimes after reboot the neutron-
plugin-openvswitch-agent is not started, whereas the neutron-dhcp-agent
and the neutron-l3-agent get started. The problem is that
20 matches
Mail list logo
