Bug 1827526
| Summary: | /64 Prefix is not allowed when ipv6_prefix is configured on a logical switch's other_config | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux Fast Datapath | Reporter: | ying xu <yinxu> |
| Component: | ovn2.11 | Assignee: | Numan Siddique <nusiddiq> |
| Status: | CLOSED ERRATA | QA Contact: | Fei Liu <feliu> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | FDP 20.D | CC: | ctrautma, jishi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovn2.11-2.11.1-45 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-15 13:01:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
ying xu
2020-04-24 05:48:12 UTC
Verified on ovn2.11.1-47.el7:
[root@dell-per740-42 ~]# rpm -qa | grep ovn
ovn2.11-central-2.11.1-47.el7fdp.x86_64
ovn2.11-host-2.11.1-47.el7fdp.x86_64
ovn2.11-2.11.1-47.el7fdp.x86_64
[root@dell-per740-42 ~]# ovn-nbctl ls-add sw0
[root@dell-per740-42 ~]# ovn-nbctl set logical_switch sw0 other_config:ipv6_prefix="aef0::/64"
[root@dell-per740-42 ~]# ovn-nbctl lsp-add sw0 sw0-p1 -- lsp-set-addresses sw0-p1 "00:00:00:00:20:01 dynamic"
[root@dell-per740-42 ~]# ovn-nbctl list logical_switch_port sw0-p1
_uuid : 6374dcf8-62da-40e1-bc0e-f12f81f8f5cf
addresses : ["00:00:00:00:20:01 dynamic"]
dhcpv4_options : []
dhcpv6_options : []
dynamic_addresses : "00:00:00:00:20:01 aef0::200:ff:fe00:2001"
<=== ipv6 is generated
enabled : []
external_ids : {}
ha_chassis_group : []
name : "sw0-p1"
options : {}
parent_name : []
port_security : []
tag : []
tag_request : []
type : ""
up : false
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2942 |