Bug 981168

Summary: Change the Netmask into Prefix Length in IPv6 settings and using digital as its value
Product: Red Hat Enterprise Linux 6 Reporter: wanghui <huiwa>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: acathrow, bsarathy, cboyle, cshao, fdeutsch, gouyang, hadong, jboggs, leiwang, mburns, ovirt-maint, yaniwang, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.0.1-2.el6 Doc Type: Bug Fix
Doc Text:
Previously the term "Netmask" was used incorrectly for the IPv6 prefix length. The name is now corrected and additionally only an integer is allowed as the prefix length.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 19:44:02 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:
Attachments:
Description Flags
ipv6 setting none

Description wanghui 2013-07-04 07:34:20 UTC
Created attachment 768617 [details]
ipv6 setting

Description of problem:
In IPv6 settings, we should using prefix length install of netmask. And we should allow input digital as its value install of ipv6 address.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.5-20130222.0.auto1707.el6.iso
ovirt-node-3.0.0-1.999.20130701111251git99aadc6.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Clean install the rhev-hypervisor6-6.5.
2. Configure the network with ipv6 static mode.
   IP Address:   2001:da8::9000::82    Netmask:   64

Actual results:
After step2, it not allow you to input like that. And the netmaks should be prefix length.

Expected results:
After step2, the digital can be accepted. The netmaks is instead as prefix length.

Additional info:

Comment 4 wanghui 2013-08-06 07:28:57 UTC
Test version:
rhev-hypervisor6-6.5-20130725.0.iso
ovirt-node-3.0.0-6.1.el6.noarch

Test steps:
1. clear install rhev-hypervisor6-6.5-20130725.0.iso.
2. Enter Network page configure NIC with ipv6 static mode.
   a. IP Address:   2001:da8::9000::82    Netmask:   64
   b. IP Address:   2001:da8::9000::82    Netmask:   2001::
   
Test result:
1. The Netmask accepts the digital as input. 
2. The Netmask accepts the ipv6 address as input also.

As qe's option, we need to add the following modifications.
1. Change "Netmask" into "Prefix Length" in TUI. Because in IPv6, we call netmask as prefix length.
2. It should be better to not accept ipv6 address as the prefix length. In other words, the input as b in step2 should not be allowed.

So change the status from ON_QA to ASSIGNED since there still need some modifications.

Thanks
huiwang

Comment 5 Fabian Deutsch 2013-08-07 12:44:41 UTC
Another patch is introduced to change the wording and to only allow digits as the prefix length.

Comment 7 wanghui 2013-10-10 07:55:41 UTC
Test version:
rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso
ovirt-node-3.0.1-3.el6.noarch

Test steps and results:
1. clear install rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso.
2. Enter Network page configure NIC with ipv6 static mode.
   a. IP Address:   2001:da8::9000::82    Prefix Length :   64             pass
   b. IP Address:   2001:da8::9000::82    Prefix Length :   2001::         fail

So this bug is fixed in rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso. I will recheck it when I get official build.

Comment 8 wanghui 2013-10-18 10:11:51 UTC
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6.noarch

Test steps and results:
1. clear install rhev-hypervisor6-6.5-20131017.0.iso.
2. Enter Network page configure NIC with ipv6 static mode.
   a. IP Address:   2001:da8::9000::82    Prefix Length :   64             pass
   b. IP Address:   2001:da8::9000::82    Prefix Length :   2001::         fail

The bug is fixed in rhev-hypervisor6-6.5-20131017.0.iso. So change the bug's status from ON_QA to VERIFIED.

Comment 10 Cheryn Tan 2013-11-08 00:29:55 UTC
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 12 errata-xmlrpc 2014-01-21 19:44:02 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html