forked from beam/freenas-proxmox
-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
truenas scale TrueNAS-SCALE-23.10.1 incompatibility #180
Labels
Comments
TheGrandWazoo
added
Question
Further information is requested
Diagnose
Diagnose/Discuss a issue or concern
labels
Mar 22, 2024
Could you post the syslog from the start of the FreeNAS command to its failure. |
TheGrandWazoo
added
User Resolved
User resolved issue due to configuation
and removed
Question
Further information is requested
Diagnose
Diagnose/Discuss a issue or concern
labels
Apr 15, 2024
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A default new install of truenas scale will receive the following errors during a vm create.
Upon further investigation in syslog, I found that it is common to receive either http 302s or 301s and fail as a result. Example follows:
A disk is created on the truenas side but is never accessible due to errors in the above process.
I found a working workaround by executing the following on the truenas scale side:
The text was updated successfully, but these errors were encountered: