yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #88525
[Bug 1954384] Re: Neutron doesn't use set dns-domain for Nova instance
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1954384
Title:
Neutron doesn't use set dns-domain for Nova instance
Status in neutron:
Expired
Bug description:
I'm trying to get neutron to update designate zones.
There initially wasn't any issue with OpenStack Victoria, but trying to update to (or install fresh) OpenStack Wallaby turned this into a dead-end.
I've deployed both OpenStack Victoria, Wallaby and Xena the exact same
way with kolla-ansible, some configuration changes but for the neutron
and designate configuration there hasn't been any changes - so regular
old neutron with linuxbridge and designate with bundled bind9 server.
Set the network_vlan_ranges in order to create a vlan-network instead of a VXLAN later on for testing.
`ml2_conf.ini` in `/etc/kolla/config/neutron` is set to
```
[ml2_type_vlan]
network_vlan_ranges = physnet1
```
Commands used:
```
kolla-ansible -i all-in-one bootstrap-servers
kolla-ansible -i all-in-one deploy
kolla-ansible -i all-in-one post-deploy
source /etc/kolla/admin-openrc.sh
init-runonce
openstack zone create "virt.xc." --email "post@xc"
```
Deleted the demo-net and router from init-runonce through Horizon, then recreated them as VLAN in the Horizon-Admin section to not hit this requirement:
> network types VLAN, GRE, VXLAN or GENEVE, the segmentation ID must be outside the ranges assigned to project networks
Set the DNS-domain for `demo-net` to `virt.xc.` by `openstack network
set demo-net --dns-domain "virt.xc."`.
```
kolla_base_distro: "ubuntu"
kolla-install_type: "source"
enable_haproxy: "no"
enable_designate: "yes"
enable_neutron_provider_segments: "yes"
enable_neutron_segments: "yes"
neutron_plugin_agent: "linuxbridge"
```
Running
```
openstack server create \\
--image cirros \\
--flavor m1.tiny \\
--key-name mykey \\
--network demo-net \\
demo1
```
on OpenStack Victoria deployed with git kolla-ansible stable/victoria works fine and creates an A-record of `demo1.virt.xc.`.
Wallaby and Xena (deployed with git kolla-ansible stable/wallaby)
however straight up refuses to create an A-record in the
`virt.xc.`-zone for the newly created VM `demo1`. It is just never
created.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1954384/+subscriptions
References