-
Notifications
You must be signed in to change notification settings - Fork 53
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
only set randompasswd in graphics template if it's true #535
Conversation
older OpenNebula versions (like 5.12) interpret the `RANDOM_PASSWORD` as truthy if its value is not empty and therefore try to generate a password, which when using VNC will not be truncated due to another bug that's already been fixed in the latest release (yes, I know, we should really update our setup ...)
Hi @frousselet, the readme mentions that OpenNebula But the bug fixed by this PR also affects at least |
My bad, I misread 😬 |
This pull request is stale because it has been open for 30 days with no activity and it is not in a milestone. Remove 'status: stale' label or comment, or this will be closed in 5 days. |
Hi @frousselet, looks like this PR was "forgotten" - would you be so kind and reopen it, thx! |
hi, sorry for the late reply, instead of modifying the default behavior for all the releases, could you check the version instead and add an if - else to handle your specific case ? Here's an example: https://github.com/OpenNebula/terraform-provider-opennebula/blob/master/opennebula/resource_opennebula_marketplace_app.go#L180 Then rebase your PR, add a line in the CHANGELOG and I'll review it |
This pull request is stale because it has been open for 30 days with no activity and it is not in a milestone. Remove 'status: stale' label or comment, or this will be closed in 5 days. |
I remove the stale label to let it open some more days as it took me a bit of time to review it |
Tested for OpenNebula versions >5.12. For these versions, setting RANDOM_PASSWD = "NO" is completely equivalent to not setting it. LGTM, merging. |
Community Note
Description
older OpenNebula versions (like 5.12) interpret the
RANDOM_PASSWORD
as truthy if its value is not empty and therefore try to generate a password, which when using VNC will be too long and not truncated due to another bug that's already been fixed in the latest release.(yes, I know, we should really update our setup ...)
References
New or Affected Resource(s)
Checklist
References
go fmt
)