Bug 490794
| Summary: | RFE: Kickstart to configure/setup ipv6 addresses on network devices. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Wade Mealing <wmealing> | ||||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.0 | CC: | atodorov, borgan, dcbw, ddumas, jkachuck, peter.tiggerdine, syeghiay, tao | ||||||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | anaconda-13.21.60-1 | Doc Type: | Enhancement | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | |||||||||||
| : | 609570 609576 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2010-11-10 19:36:36 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 609570 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Wade Mealing
2009-03-18 03:33:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Event posted on 06-08-2009 07:56am EDT by Glen Johnson ------- Comment From gongjie.com 2009-06-07 23:15 EDT------- Dear Red Hat Engineer, As I mentioned previously, with the anaconda update image, updates-2.img.gz, anaconda supports IPv6 but kickstart not. This is inconsistent. I think we should fix them at the same time. And Joe Kachuck said that fix this problem for RHEL5 could cause issue to the stage 2 loader. Does it mean fix this problem for RHEL5 will cause unwanted side effect and we cannot fix it at all? Installing Linux on a system with multiple network interfaces and manually specified IPv6 addresses is a rarely used function. And we have work around method. I think this is not an urgent problem. We may defer this bug to RHEL6 until we can fix it completely. To work around this problem, set NETWORKING_IPV6 to "yes" in /etc/sysconfig/network. Then, restart network connection with command "service network restart". Thanks Jie Gong This event sent from IssueTracker by jkachuck issue 140830 Event posted on 10-12-2009 03:53am EDT by Glen Johnson
------- Comment From gongjie.com 2009-10-12 03:47 EDT-------
There is no place to configure IPv6 in the anaconda of RHEL6
pre-Alpha2-1006. Neither in the text installation user interface nor the
graphical user interface. I cannot even configure the network interfaces
other than the one I used to doing the network installation.
Is it a ``feature''? Or the network configuration interface has missed
from the installation procedure.
~~~snip~~~
Welcome to Red Hat Enterprise Linux 6 for ppc64
?????????????????? Installation Method ??????????????????
??? ???
??? What type of media contains ???
??? the installation image? ???
??? ???
??? Local CD/DVD ???
??? Hard drive ???
??? NFS directory ???
??? URL ???
??? ???
??? ?????????????????? ???????????????????????? ???
??? ??? OK ??? ??? Back ??? ???
??? ?????????????????? ???????????????????????? ???
??? ???
??? ???
???????????????????????????????????????????????????????????????????????????????????????????????????
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
Welcome to Red Hat Enterprise Linux 6 for ppc64
?????????????????????????????????????????????????????? Networking Device
??????????????????????????????????????????????????????
??? ???
??? You have multiple network devices on this system. ???
??? Which would you like to install through? ???
??? ???
??? eth0 - Ethernet device eth0 - 00:1a:64:3b:18:ae ???
??? eth1 - Ethernet device eth1 - 00:1a:64:28:20:23 ???
??? eth2 - Ethernet device eth2 - 00:1a:64:28:20:33 ???
??? eth3 - Ethernet device eth3 - 00:14:5e:b8:08:37 ???
??? ???
??? ?????????????????? ????????????????????????????????????
???????????????????????? ???
??? ??? OK ??? ??? Identify ??? ??? Back ??? ???
??? ?????????????????? ????????????????????????????????????
???????????????????????? ???
??? ???
??? ???
?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
Welcome to Red Hat Enterprise Linux 6 for ppc64
?????????????????????????????????????????? Configure TCP/IP
??????????????????????????????????????????
??? ???
??? [*] Enable IPv4 support ???
??? ( ) Dynamic IP configuration (DHCP) ???
??? (*) Manual configuration ???
??? ???
??? ?????????????????? ????????????????????????
???
??? ??? OK ??? ??? Back ??? ???
??? ?????????????????? ????????????????????????
???
??? ???
??? ???
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
Welcome to Red Hat Enterprise Linux 6 for ppc64
???????????????????????????????????????????????? Manual TCP/IP
Configuration ???????????????????????????????????????????????????
??? ???
??? Enter the IPv4 and/or the IPv6 address and prefix ???
??? (address / prefix). For IPv4, the dotted-quad netmask ???
??? or the CIDR-style prefix are acceptable. The gateway and ???
??? name server fields must be valid IPv4 or IPv6 addresses. ???
??? ???
??? IPv4 address: 9.3.111.192_____ / 255.255.255.0___ ???
??? Gateway: 9.3.111.1________________________________ ???
??? Name Server: 9.3.121.18_______________________________ ???
??? ???
??? ??????????????????
???????????????????????? ???
??? ??? OK ??? ??? Back ??? ???
??? ??????????????????
???????????????????????? ???
??? ???
??? ???
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
Welcome to Red Hat Enterprise Linux 6 for ppc64
?????????????????????????????????????????????????????????????????????????????????
NFS Setup
????????????????????????????????????????????????????????????????????????????????????
??? ???
??? Please enter the server name and path to your Red Hat ???
??? Enterprise Linux 6 installation image. ???
??? ???
??? NFS server name: 9.3.117.7_______________ ???
??? Red Hat Enterprise Linux 6 directory: /distros/rhel6__________ ???
??? ???
??? ??????????????????
???????????????????????? ???
??? ??? OK ??? ??? Back ???
???
??? ??????????????????
???????????????????????? ???
??? ???
??? ???
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
~~~snip~~~
This event sent from IssueTracker by jkachuck
issue 140830
(In reply to comment #7) > ------- Comment From gongjie.com 2009-10-12 03:47 EDT------- > There is no place to configure IPv6 in the anaconda of RHEL6 > pre-Alpha2-1006. Neither in the text installation user interface nor the > graphical user interface. I cannot even configure the network interfaces > other than the one I used to doing the network installation. Correct. As previously mentioned, what is still lacking here is complete support for IPv6 in NetworkManager. anaconda has switched to using NM to do all network configuration in RHEL6 as that's the same thing the rest of the system uses. However since it does not yet fully support IPv6, neither does anaconda. When it grows that support, we can re-enable the dialogs in anaconda. This should be fixed in the next build of anaconda for RHEL6, which I am referencing in the Fixed In Version: field above. I am currently working on getting this build done, and it should be completed by the end of this week. Event posted on 01-15-2010 10:00am EST by Glen Johnson ?????? Installation Method ?????? ? ? ? What type of media contains ? ? the installation image? ? ? ? ? Local CD/DVD ? ? Hard drive ? ? NFS directory ? ? URL ? ? ? ? ?????? ???????? ? ? ? OK ? ? Back ? ? ? ?????? ???????? ? ? ? ? ? ????????????????????????????????? ?????????????????? Networking Device ?????????????????? ? ? ? You have multiple network devices on this system. ? ? Which would you like to install through? ? ? ? ? eth0 - Ethernet device eth0 - 00:1a:64:3b:18:ae ? ? eth1 - Ethernet device eth1 - 00:1a:64:28:20:23 ? ? eth2 - Ethernet device eth2 - 00:1a:64:28:20:33 ? ? eth3 - Ethernet device eth3 - 00:14:5e:b8:08:37 ? ? ? ? ?????? ???????????? ???????? ? ? ? OK ? ? Identify ? ? Back ? ? ? ?????? ???????????? ???????? ? ? ? ? ? ??????????????????????????????????????????????????????? ?????????????? Configure TCP/IP ?????????????? ? ? ? [*] Enable IPv4 support ? ? ( ) Dynamic IP configuration (DHCP) ? ? (*) Manual configuration ? ? ? ? ?????? ???????? ? ? ? OK ? ? Back ? ? ? ?????? ???????? ? ? ? ? ? ?????????????????????????????????????????????? ???????????????? Manual TCP/IP Configuration ????????????????? ? ? ? Enter the IPv4 and/or the IPv6 address and prefix ? ? (address / prefix). For IPv4, the dotted-quad netmask ? ? or the CIDR-style prefix are acceptable. The gateway and ? ? name server fields must be valid IPv4 or IPv6 addresses. ? ? ? ? IPv4 address: 9.3.111.192_____ / 255.255.255.0___ ? ? Gateway: 9.3.111.1________________________________ ? ? Name Server: 9.3.121.18_______________________________ ? ? ? ? ?????? ???????? ? ? ? OK ? ? Back ? ? ? ?????? ???????? ? ? ? ? ? ?????????????????????????????????????????????????????????????? ??????????????????????????? NFS Setup ???????????????????????????? ? ? ? Please enter the server name and path to your Red Hat ? ? Enterprise Linux 6 installation image. ? ? ? ? NFS server name: 9.3.117.7_______________ ? ? Red Hat Enterprise Linux 6 directory: /distros/rhel6__________ ? ? ? ? ?????? ???????? ? ? ? OK ? ? Back ? ? ? ?????? ???????? ? ? ? ? ? ?????????????????????????????????????????????????????????????????? This event sent from IssueTracker by jkachuck issue 140830 Can you please verify the version of anaconda you have in your tree? A test I just did with anaconda-13.21.0-1 shows that the Configure TCP/IP screen has options for both IPv4 and IPv6. Created attachment 414851 [details]
IPv4 / IPv6 selection in loader
Created attachment 414854 [details]
manual IPv4/IPv6 configuration screen in loader
Created attachment 414855 [details]
Networking settings in stage2 - IPv6 tab
Hi Chris, I've tested with anaconda-13.21.39-1.el6. IPv6 configuration options have been enabled in the UI, see attached screenshots. Can you please clarify my questions below. This bug talks about kickstart but is assigned to anaconda. Is there a pykickstart bug for the --ipv6 option or we'll track this one here? In loader when I'm at the IPv4/IPv6 manual settings screen and I press back the previous screen defaults to DHCP/Automatic, it doesn't remember my previous selection manual/manual. Should this be considered bug and reported separately? In loader when I select IPv4/DHCP and IPv6/Manual and press Next loader gets an IPv4 address and continues to stage2. It doesn't ask me for manual configuration. In stage2 the default setting for IPv6 is Automatic not manual. What is the desired behavior and which is the faulty component here, anaconda or NM? > This bug talks about kickstart but is assigned to anaconda. Is there a > pykickstart bug for the --ipv6 option or we'll track this one here? --ipv6= was added in F8, so it should be in RHEL6. Is anaconda not paying attention to it, or are you seeing a parse error? > In loader when I'm at the IPv4/IPv6 manual settings screen and I press back the > previous screen defaults to DHCP/Automatic, it doesn't remember my previous > selection manual/manual. Should this be considered bug and reported separately? > > In loader when I select IPv4/DHCP and IPv6/Manual and press Next loader gets an > IPv4 address and continues to stage2. It doesn't ask me for manual > configuration. In stage2 the default setting for IPv6 is Automatic not manual. > What is the desired behavior and which is the faulty component here, anaconda > or NM? These both sound like separate bugs. They also both sound like they should be investigated on the anaconda side first. (In reply to comment #19) > > This bug talks about kickstart but is assigned to anaconda. Is there a > > pykickstart bug for the --ipv6 option or we'll track this one here? > > --ipv6= was added in F8, so it should be in RHEL6. Is anaconda not paying > attention to it, or are you seeing a parse error? > With a ks.cfg that has the line network --device eth0 --bootproto dhcp --ipv6=auto ksvalidator reports no errors while anaconda (stage1) says: Bad argument to kickstart network command: Unknown option --ipv6=auto. This is with anaconda-13.21.56-1.el6. Moving back to ASSIGNED. The curse of the kickstart networking command is that it requires changes to pykicsktart, anaconda, AND loader. This should be fixed in anaconda-13.21.60-1. Kickstart command network --ipv6 should work, and network --gateway can be given ipv6 address now. anaconda-13.21.60 didn't report unknown option as in comment #20. eth0 was assigned IPv6 address. Moving to VERIFIED. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |