|
Bugzilla – Full Text Bug Listing |
| Summary: | Internet test is OK, but failure to refresh repos | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Marius Tomaschewski <mt> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | ma |
| Version: | Milestone 5 | ||
| Target Milestone: | Milestone 8 | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2logs | ||
It was also quite difficult to skip the refesh. Please take a look. The failure message "Failed to establish connection, cause: Keine Route zum Zielrechner' means no route to the destination host. xanthos:~ # ip -4 r s 172.16.0.0/24 dev eth1 proto kernel scope link src 172.16.0.1 169.254.0.0/16 dev eth1 scope link 127.0.0.0/8 dev lo scope link default via 172.16.0.254 dev eth1 xanthos:~ # ip -6 r s fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 xanthos:~ # grep -v ^# /etc/resolv.conf search mat-home.net nameserver 172.16.0.254 nameserver 213.251.167.68 xanthos:~ # What is "unusual" in this installation is, that I've disabled the broken adding of the hostname to /etc/hosts (WRITE_HOSTNAME_TO_HOSTS="no") and update of the hostname via dhcp (DHCLIENT_SET_HOSTNAME="no"). Network was fine, I was able to ping by hostname (google) and AFAIR also to download.opensuse.org. One problem is that the refresh failed for some reason -- this may be some temporary problem with download.opensuse.org or some mirrors or maybe some problem in zypp. It would make sense to review the logs to see what the reason exactly was. The main problem was, that I was unable to skip/abort it. Every time I've hit the skip or abort button, it come up again and again without any end. When I remember correctly, it was just the update run after installation, so it is not required even when it fails. It is generally an exhausting problem to abort any installation loop. It didn't happen in later Milestones any more. |
Created attachment 312973 [details] y2logs The internet test was OK, I was able to ping by name, but the repo refresh failed.