yahoo-eng-team team mailing list archive

[OpenStack Infra <1947127@xxxxxxxxxxxxxxxxxx>]

This issue was fixed in the openstack/neutron 18.6.0  release.

** Changed in: cloud-archive/wallaby
       Status: Fix Committed => 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/1947127

Title:
  [SRU] Some DNS extensions not working with OVN

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in Ubuntu Cloud Archive yoga series:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Impish:
  Fix Released
Status in neutron source package in Jammy:
  Fix Released
Status in neutron source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  On a fresh devstack install with the q-dns service enable from the
  neutron devstack plugin, some features still don't work, e.g.:

  $ openstack subnet set private-subnet --dns-publish-fixed-ip
  BadRequestException: 400: Client Error for url: https://10.250.8.102:9696/v2.0/subnets/9f50c79e-6396-4c5b-be92-f64aa0f25beb, Unrecognized attribute(s) 'dns_publish_fixed_ip'

  $ openstack port create p1 --network private --dns-name p1 --dns-domain a.b.
  BadRequestException: 400: Client Error for url: https://10.250.8.102:9696/v2.0/ports, Unrecognized attribute(s) 'dns_domain'

  The reason seems to be that
  https://review.opendev.org/c/openstack/neutron/+/686343/31/neutron/common/ovn/extensions.py
  only added dns_domain_keywords, but not e.g. dns_domain_ports as
  supported by OVN

  [Test Case]

  Create a normal OpenStack neutron test environment to see if we can
  successfully run the following commands:

  openstack subnet set private_subnet --dns-publish-fixed-ip
  openstack port create p1 --network private --dns-name p1 --dns-domain a.b.

  [Regression Potential]

  The fix has merged into the upstream stable/xena branch [1], here's
  just SRU into the 19.1.0 branch of UCA xena (the fix is already in
  20.0.0 so it's already in jammy and kinetic and focal-yoga), so it is
  a clean backport and might be helpful for deployments migrating to
  OVN.

  [1] https://review.opendev.org/c/openstack/neutron/+/838650

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1947127/+subscriptions