Bug 880482
| Summary: | --proxy option does not work for "url" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ken Dreyer <ktdreyer> | ||||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | anaconda-maint-list, Bert.Deknuydt, g.kaviyarasu, jonathan, sbueno, smitna, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | anaconda-19.25-1.fc19 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-05-15 17:29:49 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: |
|
||||||||
Can you also attach /tmp/anaconda.log and /tmp/packaging.log? Thanks. (In reply to comment #1) > Can you also attach /tmp/anaconda.log and /tmp/packaging.log? Thanks. I have encountered this bug independently of the original poster (Ken Dreyer). At that time, I was using the Fedora 18 x86_64 release netinst iso image (anaconda version 18.37.11). For this bug report, I am using Ken's kickstart but with a few minor modifications: 1. Currently, all URLs from Ken's kickstart either do not resolve via DNS or return http code 404, so except for proxy server values, I have substituted with URLs that are publicly reachable. 2. I have commented out all repo statements; otherwise, dependency errors are reported during installation, and I decided that they might obscure the issue at hand. Note, however, that my observations regarding URLs from 'repo' statements are consistent with Ken's; in particular, unlike 'url' statements, proxy values are honored. When the "Begin Installation" button was ready to accept input, I switched to vt2 and sent anaconda an USR2 signal. Attached is the only resulting non-empty /tmp/anaconda-tb-* file. It should contain all the information you require. Created attachment 693647 [details]
log generated by sending USR2 signal to anaconda
This should be fixed post-F18. There's been some work done around proxy support. If you can retest with F19 alpha and let us know, it would be very helpful. Thanks. anaconda-19.25-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/anaconda-19.25-1.fc19 Package anaconda-19.25-1.fc19, python-blivet-0.13-1.fc19, pykickstart-1.99.30-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.25-1.fc19 python-blivet-0.13-1.fc19 pykickstart-1.99.30-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7834/python-blivet-0.13-1.fc19,pykickstart-1.99.30-1.fc19,anaconda-19.25-1.fc19 then log in and leave karma (feedback). anaconda-19.25-1.fc19, python-blivet-0.13-1.fc19, pykickstart-1.99.30-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. I can confirm that this is fixed in F19 final TC3. Thanks all. |
Created attachment 652498 [details] kickstart with --proxy Description of problem: Anaconda ignores the "--proxy" option when applied to a "url". I can successfully set a global proxy by using the "proxy" parameter on the command-line. Also, --proxy appears to work for "repo" sections (at least anaconda loads the packages through the proxy). Version-Release number of selected component (if applicable): Anaconda 18.28 How reproducible: Every time Steps to Reproduce: 1. Use a kickstart file with --proxy on the "url" option. 2. When the installer gets to the main screen, check the UI to see that there is no proxy set for the installation source. 3. Watch the proxy access logs, or sniff the traffic with Wireshark to see that Anaconda is not using the proxy for the main repository packages. I'm attaching the kickstart file that I used to install F18.