Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Create two virtual networks which are "IPv6 only" and "IPv4 and IPv6". Then import two shutoff vm with fedora 31 and change their network interface source to the network which is "IPv4 and IPv6". Then run the two VM, after that check which VM has inet and inet6 in its "IP address" of the network interface tab. then shut off this VM and change its network interface source to the network which is "IPv6 only". Then re-run this VM, its "IP address" of the network interface tab will still contain two IP addresses.
Version-Release number of selected components (if applicable):
cockpit-258-1.el9.x86_64
cockpit-machines-256-1.el9.noarch
libvirt-dbus-1.4.1-5.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1 Create IPv6 only network like follow and activate it:
Connection system
Name IPv6
Forward mode NAT
Device Automatic
IP configuration IPv6 only
IPv6 address FEC0:0:0:8000::1
Prefix length 64
Set DHCP range checked
Start FEC0:0:0:8000::2 End FEC0:0:0:8000::242
2 Create IPv4 and IPv6 network like follow and activate it:
Connection system
Name IPv4v6
Forward mode NAT
Device Automatic
IP configuration IPv4 and IPv6
IPv4 address 192.168.100.1
Mask or prefix length 24
Set DHCP range checked
Start 192.168.100.2 End 192.168.100.254
IPv6 address FEC0:0:0:8001::1
Prefix length 64
Set DHCP range checked
Start FEC0:0:0:8001::2 End FEC0:0:0:8001::252
3 Import two shutoff VM with fedora 31
4 Change the VMs network interface source to "IPv4v6"
5 Run the two VMs
6 Enter the VM detail page which shows two IP addresses in network interface tab
7 Shut off the VM in step 6
8 Change network interface source of the VM in step 6 to "IPv6"
9 Re-run the VM
Actual results:
1 After step 9, "IP address" in network interface tab will still contain two IP addresses
Expected results:
1 After step 9, "IP address" in network interface tab should contain only IPv6 address
Additional info:
Comment 2RHEL Program Management
2023-06-17 07:29:16 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 4RHEL Program Management
2023-09-15 12:54:17 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-15 12:56:15 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Create two virtual networks which are "IPv6 only" and "IPv4 and IPv6". Then import two shutoff vm with fedora 31 and change their network interface source to the network which is "IPv4 and IPv6". Then run the two VM, after that check which VM has inet and inet6 in its "IP address" of the network interface tab. then shut off this VM and change its network interface source to the network which is "IPv6 only". Then re-run this VM, its "IP address" of the network interface tab will still contain two IP addresses. Version-Release number of selected components (if applicable): cockpit-258-1.el9.x86_64 cockpit-machines-256-1.el9.noarch libvirt-dbus-1.4.1-5.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1 Create IPv6 only network like follow and activate it: Connection system Name IPv6 Forward mode NAT Device Automatic IP configuration IPv6 only IPv6 address FEC0:0:0:8000::1 Prefix length 64 Set DHCP range checked Start FEC0:0:0:8000::2 End FEC0:0:0:8000::242 2 Create IPv4 and IPv6 network like follow and activate it: Connection system Name IPv4v6 Forward mode NAT Device Automatic IP configuration IPv4 and IPv6 IPv4 address 192.168.100.1 Mask or prefix length 24 Set DHCP range checked Start 192.168.100.2 End 192.168.100.254 IPv6 address FEC0:0:0:8001::1 Prefix length 64 Set DHCP range checked Start FEC0:0:0:8001::2 End FEC0:0:0:8001::252 3 Import two shutoff VM with fedora 31 4 Change the VMs network interface source to "IPv4v6" 5 Run the two VMs 6 Enter the VM detail page which shows two IP addresses in network interface tab 7 Shut off the VM in step 6 8 Change network interface source of the VM in step 6 to "IPv6" 9 Re-run the VM Actual results: 1 After step 9, "IP address" in network interface tab will still contain two IP addresses Expected results: 1 After step 9, "IP address" in network interface tab should contain only IPv6 address Additional info: