Bug 1514754
Summary: | Offline update fails due to cache synchronization failure for “updates” repo | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martin Ueding <mu> |
Component: | dnf-plugins-extras | Assignee: | rpm-software-management |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | alexvillacislasso, brice.taillefer4, dmach, extras-orphan, ignatenko, jkadlcik, jmracek, John_Sauter, mblaha, misc, paul, rpm-software-management, vmukhame |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-30 09:51:41 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
Martin Ueding
2017-11-18 10:29:45 UTC
I have got the same, the exact message in English is: dnf[1726]: Error: Failed to synchronize cache for repo 'updates' The exact same and I'm french. I'm willing to help on this bug but I never developped on a linux system. I can try whatever is suggested though. In /var/log//dnf.log I found messages like: 2017-11-19T13:42:27Z DEBUG Cannot download 'http://linuxdownload.adobe.com/linux/x86_64/': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml [Could not resolve proxy: proxy.internaldomain.org]. So I disabled all third paty repos, and reran: dnf -v system-upgrade download --releasever=27 dnf system-upgrade reboot After that it worked. On this system I had changed /etc/dnf/dnf.conf: metadata_expire=7200 #metadata_expire=86400 I am wondering if it has something to do with that as I am using a very slow ADSL line... I doubt that your internet connection is to blame. I tried the upgrade with my 16 MBit/s ADSL2 connection at home and the 100 MBit/s university access. Every time I got the same error. Trying without third-party repositories is an idea, though. I am not sure how metadata_expire exactly works, but the total download took more than 2 hours (7200 s) on my link. I also noticed messages like: 2017-11-19T09:13:21Z DEBUG virtualbox: using metadata from Wed 18 Oct 2017 16:02:06 BST. 2017-11-19T10:31:57Z DDEBUG repo: downloading from remote: virtualbox, _Handle: metalnk: None, mlist: None, urls ['http://download.virtualbox.org/virtualbox/rpm/fedora/27/x86_64']. 2017-11-19T10:31:57Z DEBUG Cannot download 'http://download.virtualbox.org/virtualbox/rpm/fedora/27/x86_64': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried. 2017-11-19T10:31:57Z WARNING Failed to synchronize cache for repo 'virtualbox', disabling. Not sure if this is related though, as I upgraded another system with virtualbox without any problems. Looking through my proxy logs I can see that yesterday virtualbox.org gave a 404, but this morning a 200 when repomd.xml was requested. I have tried with third party repositories disabled, that did not change anything. Seems we have different issues... Have you seen these? https://bugzilla.redhat.com/show_bug.cgi?id=1513111 https://github.com/rpm-software-management/dnf-plugin-system-upgrade/issues/58 I disabled third party repos ans it worked. I was having the exact same log as Martin Ueding. What I did : Dnf repolist Dnf --disablerepo [repo without stars] Dnf repolist (check if only star repo) Dnf update Thème follow what's described in fedora magazine article for upgrading from 26 to 27. Worked like a charm. Can't edit, here's the code (was on phone sorry) sudo dnf repolist sudo dnf config-manager --set-disabled [repo name without stars] sudo dnf repolist /!\(check if only star repo)/!\ sudo dnf update Can one of the reporter try to set "check_config_file_age = false" in the main section of /etc/dnf/dnf.conf and try the upgrade ? I did debug the problem as explained on https://bugzilla.redhat.com/show_bug.cgi?id=1514877 but as I did found another work around, I can't test easily now :/ I have just added this to the configuration and then ran: dnf system-upgrade download --releasever=27 --allowerasing --refresh -y dnf system-upgrade reboot It still did not work, the logs the same failure to update cache for “updates”. *** This bug has been marked as a duplicate of bug 1492036 *** |