Bug 1784289
Summary: | [machines][RFE] Support compressed IPV6 addresses when setting the DHCPv6 during virtual network creation | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | YunmingYang <yunyang> |
Component: | cockpit-appstream | Assignee: | Katerina Koukiou <kkoukiou> |
Status: | CLOSED ERRATA | QA Contact: | YunmingYang <yunyang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.2 | CC: | leiwang, mpitt, wshi, xchen, ymao |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 8.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 15:43:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
YunmingYang
2019-12-17 07:35:53 UTC
The issue here is that the address provided is compressed and we currently do not support that. If you change that to the expanded equivalent the Network Creation will succeed. Expanded Address: fec0:0:0:0:0:0:0:1 Compressed Address: fec0::1 I will keep this open as an RFE though. Fixed with: commit 49c2a1d154aed3ee40137ee8ad63cb82c41b74f9 Author: Katerina Koukiou <kkoukiou> Date: Tue Jan 14 16:56:15 2020 +0100 machines: decompress ipv6 addresses before validating them Verified with package: cockpit-machines-211-1.el8.noarch libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64 Steps: 1. Open the network creation dialog 2. Set the network with the configuration below: name: random string Forward Mode:NAT Device:Automatic IP Configuration: IPv6 only IPv6 Network: FEC0::1 Prefix Length: 64 Set DHCP Range Start: FEC0::1 End: FEC0::10 Then, click the 'Create' Button 3. Click Activate The network can be create and activate successfully. 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:1639 |