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
Unable to find the target id when creating new vm #87
Comments
HI @xn4p4lm When I get a chance I will see what I can do to replicate the issue in the lab. |
I've tried it with HTTPS redirect enabled and disabled in TrueNAS. Also with API use SSL checked and unchecked in Proxmox and still get a 302 redirect. These logs are with both use API use SSL unchecked in proxmox and the HTTPS redirect unchecked in TrueNAS.
Side note: if you curl the TrueNAS server from Proxmox it gets a 302 redirect:
|
I'm seeing a similar thing, but without the 302 redirects.
When I look at the truenas server, I can find the /dev/zvol/nvme/vm-114-disk-0 link. It does create the the vm-114-disk-0 zvol in the nvme pool on the truenas gui. The iscsi target is available : 192.168.200.2:3260,-1 iqn.2005-10.org.freenas.ctl:nvme-zfs This is using the stable branch of the .deb file, latest TrueNAS (non-enterprise) and latest Proxmox (non-enterprise). Is there additional information I can provide? |
Interestingly enough... When I try to add a disk to another host on a different machine in the cluster, I DO get the 302 redirects.
Creating a disk for a host on the first proxmox server in the cluster still doesn't work, but also doesn't give the 302 redirect:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello,
I've been having issues with setting up ZFS over iSCSI and can't seem to isolate the issue. Below is the configuration and logs, please let me know if there are any other logs needed.
Versions:
Proxmox Configuration:
GUI:
Text:
TrueNAS Configuration:
In TrueNAS i've setup the iscsi target manually and using the wizard with the same result.
iscsiadm discovery scan:
Attempts so far to fix
Error
When creating a VM it successfully creates the disk in the ZFS pool, but fails at the target ID:
Output of pveversion -v:
The text was updated successfully, but these errors were encountered: