Bug 892994
| Summary: | Running fedup from behind a proxy when upgrading from F17 to F18 fails | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Per Arnold Blåsmo <per.arnold> |
| Component: | fedup | Assignee: | Will Woods <wwoods> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | david, jrincayc, robin, scott.davis, tflink, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | fedup-0.7.3-5.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-15 03:29:25 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: | |||
|
Description
Per Arnold Blåsmo
2013-01-08 12:22:02 UTC
Just tried with curl to eliminate problems there.
Curl seems to work OK.
running : curl -v -o index.html --proxy-any www.bbc.co.uk 2> /tmp/curl.txt
gives:
* About to connect() to proxy squid.<xxx>.com port 3128 (#0)
* Trying 10.191.254.115...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* connected
* Connected to squid.<xxx>.com (10.191.254.115) port 3128 (#0)
> GET HTTP://www.bbc.co.uk HTTP/1.1
> User-Agent: curl/7.24.0 (x86_64-redhat-linux-gnu) libcurl/7.24.0 NSS/3.13.5.0 zlib/1.2.5 libidn/1.24 libssh2/1.4.1
> Host: www.bbc.co.uk
> Accept: */*
> Proxy-Connection: Keep-Alive
>
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Server: Apache
< Cache-Control: private, max-age=60
< Content-Type: text/html
< Expires: Tue, 08 Jan 2013 12:58:29 GMT
< ETag: "aa71c2b1659bc6f81578b27c34c2719f-e8d6e5777428a2a2055f02a9018413b3"
< X-PAL-Host: pal043.cwwtf.bbc.co.uk:80
< Content-Length: 101336
< Date: Tue, 08 Jan 2013 12:58:05 GMT
< Set-Cookie: BBC-UID=8540de8cc147ad2d9af32e67a13e11c1b57bda8cf40441be7af1549468f4a2d00curl/7.24.0%20(x86_64-redhat-linux-gnu)%20libcurl/7.24.0%20NSS/3.13.5.0%20zlib/1.2.5%20libidn/1.24%20libssh2/1.4.1; expires=Sat, 07-Jan-17 12:58:05 GMT; path=/; domain=bbc.co.uk
< X-Cache-Action: PASS (non-cacheable)
< X-Cache-Age: 36
< Vary: X-CDN
< X-Cache: MISS from squid
< X-Cache-Lookup: MISS from squid:3128
< Via: 1.0 squid:3128 (squid/2.6.STABLE18)
* HTTP/1.0 proxy connection set to keep alive!
< Proxy-Connection: keep-alive
<
{ [data not shown]
^M100 98k 100 98k 0 0 326k 0 --:--:-- --:--:-- --:--:-- 329k
* Connection #0 to host squid.<xxx>.com left intact
* Closing connection #0
Git commit 4e1ca1e should make fedup use the proxy config in yum.conf for instrepo and other commandline-added repos: https://github.com/wgwoods/fedup/commit/4e1ca1e Can you check out the latest fedup from git and confirm this? (A simple 'make && sudo make install' should work fine to install it) I have checked, and it works! Thanks for fast response. A new build would be great, especially for those of us behind the firewalls at hand :) The error was slightly different without using --instrepo, but the problem cause seems to be the same (pasting this so that maybe other people will find this bug report faster): % sudo fedup-cli --network 18 --debuglog fedupdebug.log --verbose --debug fedup INFO: /bin/fedup-cli starting at Mon Jan 28 16:54:11 2013 setting up repos... fedup DEBUG: setup_downloader(version=18, repos=[]) fedup.yum INFO: FedupDownloader(version=18, cachedir=/var/tmp/fedora-upgrade) fedup.yum DEBUG: prerepoconf.cache=0 fedup.yum INFO: checking repos fedup.yum DEBUG: conf.cache=0 fedup.yum INFO: repo adobe-linux-x86_64 seems OK fedup.yum INFO: can't find valid repo metadata for default-installrepo fedup.yum INFO: repo fedora seems OK fedup.yum INFO: repo rpmfusion-free seems OK fedup.yum INFO: repo rpmfusion-free-updates seems OK fedup.yum INFO: repo updates seems OK fedup.yum DEBUG: repos.cache=0 Error: can't get boot images. The installation repo isn't available. You need to specify one with --instrepo. fedup INFO: /bin/fedup-cli exiting at Mon Jan 28 16:54:30 2013 Any plans for a new release landing in updates-testing? I'll push something to updates-testing once I'm sure I've got all the bugfixes I want for 0.7.3. In the meantime, here's a test build: http://koji.fedoraproject.org/koji/buildinfo?buildID=381043 fedup-0.7.3-0.git20130128.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-0.git20130128.fc17 I did `yum --enablerepo=updates-testing install fedup`, which installed 0.7.3-0.git20130128.fc17, and I could upgrade successfully. So +1 from here. Is there any reason this hasn't been pushed to stable yet? The update system says it can be. Because I'm not comfortable pushing a half-finished snapshot stable. There should be a new build Very Soon that will have this bugfix and many others; when that build clears testing, it will go to stable. fedup-0.7.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-1.fc17 Package fedup-0.7.3-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.7.3-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3956/fedup-0.7.3-1.fc17 then log in and leave karma (feedback). fedup-0.7.3-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc18 fedup-0.7.3-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc17 fedup-0.7.3-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc17 fedup-0.7.3-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc18 fedup-0.7.3-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc19 fedup-0.7.3-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. For the last 3 weeks, people behind a proxy have been able to upgrade FROM Fedora 18 using Fedup, but we cannot yet upgrade TO Fedora 18, as a version of fedup has not yet been released to updates for people behind proxies with corporate policy not to use packages from *testing, only from stable updates. Is there any hope for a patch for this bug being released for FC17? This bug being fixed for Fedora 17 is currently waiting on Bug 958586, which has a fix in git, but a update has not been submitted. Removing the bug dependency - this bug is not related to the other bug. An update will be available for F17 shortly. fedup-0.7.3-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-5.fc17 fedup-0.7.3-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. fedup-0.7.3-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. (In reply to Scott Davis from comment #19) > For the last 3 weeks, people behind a proxy have been able to upgrade FROM > Fedora 18 using Fedup, but we cannot yet upgrade TO Fedora 18, as a version > of fedup has not yet been released to updates for people behind proxies with > corporate policy not to use packages from *testing, only from stable updates. > > Is there any hope for a patch for this bug being released for FC17? The update was pushed out over the weekend, and I can confirm that it worked for me, my computer is running the current version of Fedora (for a week or two, anyway!) :-) Thank you to Will and others involved in fixing it. |