** Changed in: cloud-archive/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and host
** Tags added: neutron-easy-proactive-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and host entries
To manage
Reviewed: https://review.opendev.org/666594
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=feab3462b2bf8b06caba6a15b2311309c6c08a50
Submitter: Zuul
Branch:stable/rocky
commit feab3462b2bf8b06caba6a15b2311309c6c08a50
Author: James Page
Date: Tue Jun 11 14:02:44
** Tags added: neutron-proactive-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and host entries
To manage
This bug was fixed in the package neutron - 2:13.0.2-0ubuntu3.3~cloud0
---
neutron (2:13.0.2-0ubuntu3.3~cloud0) bionic-rocky; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:13.0.2-0ubuntu3.3) cosmic; urgency=medium
.
* d/p/bug1826419.patch: Cherry
This bug was fixed in the package neutron - 2:14.0.0-0ubuntu1.1~cloud0
---
neutron (2:14.0.0-0ubuntu1.1~cloud0) bionic-stein; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:14.0.0-0ubuntu1.1) disco; urgency=medium
.
[ Corey Bryant ]
*
This bug was fixed in the package neutron - 2:14.0.0-0ubuntu2~cloud0
---
neutron (2:14.0.0-0ubuntu2~cloud0) bionic-train; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:14.0.0-0ubuntu2) eoan; urgency=medium
.
* d/p/bug1826419.patch: Cherry pick fix
This bug was fixed in the package neutron - 2:14.0.0-0ubuntu2~cloud0
---
neutron (2:14.0.0-0ubuntu2~cloud0) bionic-train; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:14.0.0-0ubuntu2) eoan; urgency=medium
.
* d/p/bug1826419.patch: Cherry pick fix
This bug was fixed in the package neutron - 2:14.0.0-0ubuntu1.1
---
neutron (2:14.0.0-0ubuntu1.1) disco; urgency=medium
[ Corey Bryant ]
* d/gbp.conf: Create stable/stein branch.
[ James Page ]
* d/p/bug1826419.patch: Cherry pick fix to revert incorrect changes to
This bug was fixed in the package neutron - 2:13.0.2-0ubuntu3.3
---
neutron (2:13.0.2-0ubuntu3.3) cosmic; urgency=medium
* d/p/bug1826419.patch: Cherry pick fix to revert incorrect changes to
internal DNS behaviour (LP: #1826419).
-- James Page Tue, 04 Jun 2019 09:40:48
This bug was fixed in the package neutron - 2:12.0.6-0ubuntu1
---
neutron (2:12.0.6-0ubuntu1) bionic; urgency=medium
[ Sahid Orentino Ferdjaoui ]
* New stable point release for OpenStack Queens (LP: #1830341).
* d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch,
Reviewed: https://review.opendev.org/657806
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8f5020120e4fb6789dcf8cda92343fde55f14aee
Submitter: Zuul
Branch:master
commit 8f5020120e4fb6789dcf8cda92343fde55f14aee
Author: James Page
Date: Sat May 4 09:21:28 2019 -0600
bionic-rocky/proposed
xenial-090914-1:~$ host xenial-090914-2
xenial-090914-2.openstack.example has address 192.168.21.27
ubuntu@xenial-090914-1:~$ host 192.168.21.27
27.21.168.192.in-addr.arpa domain name pointer
xenial-090914-2.openstack.example.
** Tags removed: verification-rocky-needed
bionic-stein/proposed
ubuntu@xenial-142455-1:~$ host xenial-142455-2
xenial-142455-2.openstack.example has address 192.168.21.108
ubuntu@xenial-142455-1:~$ host 192.168.21.108
108.21.168.192.in-addr.arpa domain name pointer
xenial-142455-2.openstack.example.
** Tags removed:
bionic/proposed:
ubuntu@xenial-113550-1:~$ host xenial-113550-2
xenial-113550-2.openstack.example has address 192.168.21.6
ubuntu@xenial-113550-1:~$ host 192.168.21.6
6.21.168.192.in-addr.arpa domain name pointer xenial-113550-2.openstack.example.
Forward and reverse lookups are consistent and
cosmic/proposed:
ubuntu@xenial-103848-1:~$ host xenial-103848-2
xenial-103848-2.openstack.example has address 192.168.21.6
ubuntu@xenial-103848-1:~$ host 192.168.21.6
6.21.168.192.in-addr.arpa domain name pointer xenial-103848-2.openstack.example.
Forward and reverse lookups are consistent and
disco/proposed:
ubuntu@xenial-074242-1:~$ host xenial-074242-2
xenial-074242-2.openstack.example has address 192.168.21.181
ubuntu@xenial-074242-1:~$ host 192.168.21.181
181.21.168.192.in-addr.arpa domain name pointer
xenial-074242-2.openstack.example.
Forward and reverse lookups are
Hello James, or anyone else affected,
Accepted neutron into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:12.0.6-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello James, or anyone else affected,
Accepted neutron into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:13.0.2-0ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello James, or anyone else affected,
Accepted neutron into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:14.0.0-0ubuntu1.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Ubuntu SRU information
[Impact]
Use of Neutron internal DNS resolution for resolution of instances attached to
the same project network is inconsistent due to use of configuration options
for the actual hostname entries in the dnsmasq hosts file paired with the
network 'dns_domain' attribute
This bug was fixed in the package neutron - 2:14.0.0-0ubuntu2
---
neutron (2:14.0.0-0ubuntu2) eoan; urgency=medium
* d/p/bug1826419.patch: Cherry pick fix to revert incorrect changes
to internal DNS behaviour (LP: #1826419).
-- James Page Mon, 03 Jun 2019 10:33:42 +0100
**
Log from IRC meeting for future followers:
http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-05-29-14.00.log.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
As discussed at the Neutron L3 meeting last week, it was agreed that the
current behaviour is not compliant with either of the two original specs
related to Internal DNS and external DNS integration and that the
behaviour change would be reverts in master and back to
stable/{queens,rocky,stein}
** Changed in: neutron (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: neutron (Ubuntu Disco)
Status: New => Triaged
** Changed in: neutron (Ubuntu Eoan)
Status: New => Triaged
** Changed in: neutron (Ubuntu Bionic)
Importance: Undecided => High
** Changed in:
** Also affects: neutron (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Cosmic)
@minsel, Miguel Lavalle
Can you check my latest comment? What's your intention for going forward fixing
the explained behavior? Are you actively working on a draft/patch for fixing
this? If so, do yo mind to explain me the approach you are following here?
Thanks
--
You received this bug
** Changed in: neutron
Assignee: James Page (james-page) => Miguel Lavalle (minsel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain
I am able to reproduce the bug 1) Forward and reverse resolution is not
honoring the network defined dns-domain. -expressed on my previous
comment without even having designate enabled on my setup.
Deploying this bundle: http://paste.ubuntu.com/p/FZff5NqfvN/ , with the
following neutron config
@minsel
Apologies - I was not expecting my review to re-assign the bug to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and host
Fix proposed to branch: master
Review: https://review.opendev.org/657806
** Changed in: neutron
Status: New => In Progress
** Changed in: neutron
Assignee: Miguel Lavalle (minsel) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: neutron
Assignee: (unassigned) => Miguel Lavalle (minsel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and host
I think it would be good to get a clear consensus on the intent in
neutron with regards to use of dns attributes on networks and dns in
configuration; behaviour has changed in a somewhat confusing way as of
>= Queens for some use cases and resolution of this bug really depends
on what neutron
Hoping someone with more history on the dns_domain/domain can chime in on this
one.
It's not clear to me if this is a bug or potentially a new RFE to change
behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fairly; I was able to reproduce the mismatch even without designate;
specifically:
/etc/neutron/plugins/ml2/ml2_conf.ini
[ml2]
extension_drivers = port_security,dns_domain_ports
/etc/neutron/neutron.conf
[DEFAULT]
dns_domain = jamespage.example.
I then updated the dns_domain on the
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and host
36 matches
Mail list logo
