Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to import image due to DNS resolution failure, but the host appears in DNS #4596

Closed
davepacheco opened this issue Dec 1, 2023 · 1 comment
Milestone

Comments

@davepacheco
Copy link
Collaborator

Working around #4595 I tried to import an image using a URL like this:

dap@ivanova ~ $ echo '{"name": "my-image", "description": "dummy", "os": "debian", "version": "11", "source": { "type": "url", "url": "http://catacomb.eng.oxide.computer/media/cloud/debian-11-genericcloud-amd64.raw", "block_size": 512 } }' | oxide image create --name my-image --description my-description --os debian --version 11 --json-body /dev/stdin
error
Error Response: status: 400 Bad Request; headers: {"content-type": "application/json", "x-request-id": "208426d0-dafd-40ad-94be-2e5566bb2737", "content-length": "380", "date": "Fri, 01 Dec 2023 17:21:52 GMT"}; value: Error { error_code: Some("InvalidValue"), message: "unsupported value for \"url\": error querying url: error sending request for url (http://catacomb.eng.oxide.computer/media/cloud/debian-11-genericcloud-amd64.raw): error trying to connect: dns error: failed to lookup address information: node name or service name not known", request_id: "208426d0-dafd-40ad-94be-2e5566bb2737" }

I assume it's saying that Nexus (or maybe some part of Crucible?) failed to resolve catacomb.eng.oxide.computer in DNS. But it's in the public DNS:

$ dig catacomb.eng.oxide.computer @1.1.1.1 

; <<>> DiG 9.18.19 <<>> catacomb.eng.oxide.computer @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53583
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;catacomb.eng.oxide.computer.	IN	A

;; ANSWER SECTION:
catacomb.eng.oxide.computer. 120 IN	A	172.20.0.5

;; Query time: 74 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Fri Dec 01 09:27:16 PST 2023
;; MSG SIZE  rcvd: 72

I'm wondering if whoever's doing this DNS resolution isn't using the right DNS servers? (But then how does this ever work?)

In case it matters, this system (madrid) was configured with these DNS servers (as in, these were in the rack setup config file I gave to wicket):

dns_servers = [
    "1.1.1.1",
    "9.9.9.9",
]
@morlandi7 morlandi7 added this to the 5 milestone Dec 1, 2023
@askfongjojo askfongjojo modified the milestones: 5, MVP Dec 5, 2023
@davepacheco
Copy link
Collaborator Author

Obsoleted by #2898.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants