XOA / NFS ISO - Unable to create on IPv6 NAS
-
Good afternoon,
I am unable to define an NFS ISO store on a NAS with an IPv6 address. However, I am able to create NFS SRs using the same IPv6 address.
Configuration:
- XCP-ng fresh install of version 8.3 (with the latest patches applied)
- Xen Orchestra - commit 6c258
- NAS with IPv6 net
Walkthrough:
The 'Create a new SR' in Xen Orchestra works fine, I can put an IPv6 address in for the option 'server' and then I am able to select a path from a discovery of the nas options.
When I then press the 'Create' button, an error occurs.sr.createIso { "host": "8f38dc4c-e980-4064-bcf4-f66afc168c68", "nameLabel": "ISO Library", "nameDescription": "ISO Library on TrueNAS", "path": "2a10:3781:2ad:f5:92e2:baff:fe31:5b80:/mnt/Venus/ISO_Library", "type": "nfs" } { "code": "SR_BACKEND_FAILURE_140", "params": [ "", "Incorrect DNS name, unable to resolve.", "" ], "call": { "method": "SR.create", "params": [ "OpaqueRef:6c9261aa-9998-b6a9-7b08-540b0fde105b", { "location": "2a10:3781:2ad:f5:92e2:baff:fe31:5b80:/mnt/Venus/ISO_Library" }, 0, "ISO Library", "ISO Library on TrueNAS", "iso", "iso", true, {} ] }, "message": "SR_BACKEND_FAILURE_140(, Incorrect DNS name, unable to resolve., )", "name": "XapiError", "stack": "XapiError: SR_BACKEND_FAILURE_140(, Incorrect DNS name, unable to resolve., ) at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202410020907/packages/xen-api/_XapiError.mjs:16:12) at file:///opt/xo/xo-builds/xen-orchestra-202410020907/packages/xen-api/transports/json-rpc.mjs:38:21 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at process.callbackTrampoline (node:internal/async_hooks:130:17)" }Kind regards,
Pim Aarts
-
Does it work for a regular SR or it's the same result regardless ISO & regular SR?
-
@PimAarts hi!
"path": "2a10:3781:2ad:f5:92e2:baff:fe31:5b80:/mnt/Venus/ISO_Library"Should be
"path": "[2a10:3781:2ad:f5:92e2:baff:fe31:5b80]:/mnt/Venus/ISO_Library"with brackets around the IPv6. -
-
I tried to fill in the IP address with brackets, but then the discovery of the NFS shares fails.
With regular SRs, it works fine without using brackets.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login