[SRU] Some DNS extensions not working with OVN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Ussuri |
New
|
Undecided
|
Unassigned | ||
Victoria |
New
|
Undecided
|
Unassigned | ||
Wallaby |
Fix Released
|
Undecided
|
Unassigned | ||
Xena |
Fix Released
|
Undecided
|
Unassigned | ||
Yoga |
Fix Released
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
High
|
Dr. Jens Harbott | ||
neutron (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
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-
BadRequestExcep
$ openstack port create p1 --network private --dns-name p1 --dns-domain a.b.
BadRequestExcep
The reason seems to be that https:/
[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-
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.
tags: | added: dns |
Changed in neutron: | |
assignee: | nobody → Dr. Jens Harbott (j-harbott) |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: ovn |
tags: | added: neutron-proactive-backport-potential |
Changed in cloud-archive: | |
status: | New → Confirmed |
description: | updated |
description: | updated |
Fix proposed to branch: master /review. opendev. org/c/openstack /neutron/ +/813969
Review: https:/