Bug 187331
Summary: | Error: Cannot find a valid baseurl for repo: core | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Blomgren <blomgren.peter> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | aldyh, katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-19 20:44:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Blomgren
2006-03-30 04:50:25 UTC
I have a similar problem. I found that the failures started after the updates that were available on 28 March. nscd is the only one that seemed related to this problem. Anyhow, I found that on system where yum fails, wget, using the URL from the ym.repos.d files, also fails with a "no find" on the IP address (such as "download.fedora.redhat.com"). Firefox resolves that URL, and substiuting the numeric IP also causes yum to work. Of 4 machines on the same subnetwork, 3 fail and one works after the same update set on 28 March. One correction to my comment above: The systems were running FC4 with all current updates, not FC5. So, this bug report should also be considered for FC4. Michael OK, let me "Me three!" on my own bug... After seeing Michael's comments, I checked on the status of my remaining FC4 system. Indeed, it displays the same problem; and it started after the updates on March 28: Packages Updated: glibc-devel.i386 2.3.6-3 mtr-gtk.i386 2:0.71-0.FC4.1 perl.i386 3:5.8.6-24 glibc-headers.i386 2.3.6-3 glibc-profile.i386 2.3.6-3 glibc-utils.i386 2.3.6-3 glibc-common.i386 2.3.6-3 glibc.i686 2.3.6-3 nscd.i386 2.3.6-3 mtr.i386 2:0.71-0.FC4.1 ... and, yeah, it's the address resolution that fails; not yum per se. See glibc bugs 186592, and 187320 Minimum necessary modification: in /etc/nsswitch.conf change the line hosts: files nisplus dns to hosts: files dns nisplus ... and the problems go away! You are right. Just figured that out. It is unclear how/when nsswitch.conf got changed. I am looking into that. Also, depending on configureation, hosts: files dns is safe. This problem also comes up if you have a http_proxy defined in the environment. Even if the http_proxy host works fine with a browser. Gives a 502 error. The solution of course is to "unset http_proxy". |