| Summary: | Network configuration screen configure-button needs to be selected twice | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | A.J. Werkman <aj.werkman> | ||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | amulhern, anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, rvykydal, sbueno, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pykickstart-1.99.46-1.fc20 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1019775 (view as bug list) | Environment: | |||||
| Last Closed: | 2013-11-24 04:01:18 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: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1019775 | ||||||
| Attachments: |
|
||||||
|
Description
A.J. Werkman
2013-10-12 09:50:04 UTC
Here is updates image for 20-Beta-TC2 with a patch that should fix the issue: http://rvykydal.fedorapeople.org/updates.configure.img Created attachment 812118 [details]
Anaconda.log
Patch works, but with this patch static ip adresses are not accepted, as Anaconda did without the patch.
I test this on a network segment, without DHCP. I add the IPv4 and IPv6 addresses in the network configuration form.
Before the patch Addresssing was not accepted, only after I toggled the NIC on/of switch. With this patch switching the NIC off and on again has no effect. Status stays 'Connecting...' In the log I see that anaconda want to switch back to DHCP. But of course this does not give an address as DHCP is not active.
Thank you for testing and the catch, fixed version of the patch (where swithching NIC on and off should work again) is in this updates image: http://rvykydal.fedorapeople.org/updates.configure2.img updates.configure2.img works. But the NIC stays in 'Connecting...' state after configuration. I still have to toggle the on/off switch to get it in 'Conntected'-state. Should I file a seperate bug or is this related to this bug? (In reply to A.J. Werkman from comment #4) > updates.configure2.img works. But the NIC stays in 'Connecting...' state > after configuration. I still have to toggle the on/off switch to get it in > 'Conntected'-state. > > Should I file a seperate bug or is this related to this bug? I think it is the issue of bug #1018471 filed by you. anaconda-20.25.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.2-1.fc20 Package anaconda-20.25.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.25.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19692/anaconda-20.25.2-1.fc20 then log in and leave karma (feedback). anaconda-20.25.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.8-1.fc20 pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20, anaconda-20.25.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |