Comment 14 for bug 1730931
Revision history for this message
| Sagi (Sergey) Shnaidman (sshnaidm) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
For downloading a specific RPM we'd better use repoquery, then wget, curl, etc.
But it won't solve the problem with resolving that happens in openstack infrastructure, because we use unbound for resolving which is set by infra. So either problem is with unbound (unlikely), or with forwarders in infra, maybe they can't accept all requests.
Also there are few workaround that could help:
1) We can resolve github.com in the beginning of the job (by ping, wget, whatever), if unbound is configured properly by infra, it should cache the result until job ends. In case of fail, we can repeat it until it resolves, because if it doesn't, it doesn't make sense to continue job.
2) We can add some of public DNS in addition to 127.0.0.1 for resolving in case of unbound failure.