Bug 1685534 - Fix IPv6 subnet gateway
Summary: Fix IPv6 subnet gateway
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider
Version: 1.2.7
Hardware: x86_64
OS: Linux
Target Milestone: ovirt-4.3.4
: 1.2.22
Assignee: Ales Musil
QA Contact: Michael Burman
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-05 12:29 UTC by Michael Burman
Modified: 2019-06-11 06:24 UTC (History)
4 users (show)

Fixed In Version: ovirt-provider-ovn-1.2.22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-11 06:24:00 UTC
oVirt Team: Network
sbonazzo: ovirt-4.3?
sbonazzo: planning_ack?
sbonazzo: devel_ack?
sbonazzo: testing_ack?

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 98103 0 master MERGED subnet: Fix IPv6 subnet gateway 2019-03-19 11:42:56 UTC

Description Michael Burman 2019-03-05 12:29:03 UTC
Description of problem:
Fix IPv6 subnet gateway

IPv6 gateway doesn't created.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create an IPv6 subnet with "gateway_ip": via REST api
https://<engine>:9696/v2.0/subnets - POST

Actual results:
Subnet created with success, but the gateway is missing

Expected results:
gateway should be created as expected

Comment 1 Dominik Holler 2019-03-28 17:01:00 UTC
Moving Target Milestone to next release, because the ovirt-provider-ovn is not going to be updated during the ovirt-4.3.3 final compose.

Comment 2 Michael Burman 2019-04-10 08:20:01 UTC
Should be moved to MODIFIED?

Comment 3 Dominik Holler 2019-04-10 08:36:04 UTC
Please note even the relevant change is merged, but there is no release tagged yet.

Comment 4 Michael Burman 2019-05-20 04:57:45 UTC
Verified on - ovirt-provider-ovn-1.2.22-1.el7ev.noarch with rhvm-4.3.4-0.1.el7.noarch

Comment 5 Sandro Bonazzola 2019-06-11 06:24:00 UTC
This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Note You need to log in before you can comment on or make changes to this bug.