Public bug reported:
Colleagues,
Description
===
Renaming instance (e.g. using "openstack server set --name") brokes DNS
integration, since it makes it impossible to bind port with new instance's
name. So, if user renamed instance and want to access it using name, he can not.
Steps to
Public bug reported:
Dear colleagues,
if there are Subnet1 with Host1 and Subnet2 with Host2 and Host2 serves
Network2 behind it, in order to reach Network2 it is required to add Network2
to Subnet1's host_routes with Host2 as a
nexthop. In this case Neutron will offer in Subnet1 the following
The issue is inside VM, not Nova's one.
** Changed in: nova
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/1791944
Title:
boot_index ignor
Public bug reported:
Dear colleagues,
seems I'm experiencing the issue, similar to
https://bugs.launchpad.net/nova/+bug/1570107 but on Queens. When I try
to boot VM with two volumes attached (both volumes made from bootable
images and are bootable as well) and use boot_index, Nova ignores
boot_in
Public bug reported:
Hi colleagues,
I'm using Heat to provision Neutron and faced the bug which is rather
Neutron's than Heat's, since Neutron receives all information,
provisions control plane ('openstack port/router show' gives updated
config), but do nothing in dataplane.
My config, which I'm
Public bug reported:
Hi colleagues,
The idea behind this design is to easily switch VM between different
address scopes (e.g. "grey" addresses in Subnet-1 and "white" in
Subnet-2), using same port/MAC (which always is in E-Network).
If VR connected to subnets belonging to same network (preformat
Public bug reported:
Dear colleagues,
when I change port admin state to DOWN, this is not reflected
accordingly on VM's side:
$ openstack port set --disable n1-lan
$ openstack port show n1-lan
[ ... ]
+---++
| Field | Value |
+
Public bug reported:
Hi colleagues,
Neutron 10.0.0 (as part Ocata) on Ubuntu 16.04
Everything is ok when I use Neutron CLI to update port parameters, but
when I'm doing the same using Heat, it fails.
Heat's template for the object is:
e-secgroup:
type: OS::Neutron::SecurityGroup
prop
Public bug reported:
Dear friends,
the problem is in the following: Neutron assign global "dns_domain"
value (specified in neutron.conf) to ports in project's network
regardless of network's "dns_domain" value specified in network
definition and incorrectly updates dnsmasq.
# cat /etc/neutron/ne
9 matches
Mail list logo
