Bug 879142
| Summary: | When passing inst.repo=hd , anaconda shows 'Error setting up software source', but in fact it works fine | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
| Component: | anaconda | Assignee: | Chris Lumens <clumens> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | g.kaviyarasu, jonathan, kparal, pf.rhlists, robatino, sbueno, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | anaconda-18.35-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-06 07:28:50 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 752661 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Williamson
2012-11-22 07:48:27 UTC
When you got the error triangle, did you go into the spoke to see if there was a more verbose error message? Also, can you attach the usual log files? I don't recall. I'll try and re-test and provide the logs. Okay, I reproduced this, just as before. Remember, the message says 'Error setting up software source' but there is *not* an error triangle. Entering the spoke I see the 'ISO file' radio button selected, and the 'Device:' dropdown is set to 'Virtio Block Device (9999 MB)', with a very small box between that dropdown and the Verify button, which doesn't look like it contains anything. There is no error message. On the Installation Destination screen, I can pick the 10GB disk which the ISO is on, and no warning or error is shown, and the Installation Source spoke does not enter any error condition. When I do that, though, it looks like it doesn't actually format or create any partitions on vdb, so that's okay, I guess. /dev/vdb1 is mounted on /run/install/isodir . I'll attach the logs from a completed install when it's done. Created attachment 654850 [details]
all typical logs pasted together
attaching all the logs in one file for convenience. note that unmounting the repo fails at the end of install, after a while it times out and shows the 'complete' message.
Note this bug is the same in final-smoke1 (using anaconda 18.32). Bug confirmed. We might want to argue whether this is just a cosmetic problem or a blocker: The installer must be able to use all supported local and remote package source options. http://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria Helps if we look in the right directory for a mounted image. pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.35-1.fc18 Package pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pykickstart-1.99.22-1.fc18 anaconda-18.35-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.35-1.fc18 then log in and leave karma (feedback). pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. This works in anaconda 18.36. |