-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Invalid PVE ticket renewal #77
Comments
I hope to have this seen in 0.8.0 Is it a complex issue ? |
It is indeed a Fog-Proxmox bug. I release now 0.8.0 and this bug will be fixed in a 0.8.1. |
Any hint to workaround this issue, until fix come out? I have PVE 5.4.8 with Foreman 1.22.0 and the plugin 0.8.0 and I'm also confronting the issue. |
Are you sure you have version 0.8 ? If yes this problem shouldn't appear. Probably you are facing following problem #86. If so, please follow instructions from my last post. |
Well unless there is a bug, on the output on About - System Status - Plugin, the indicated version is 0.8.0. Anyway the output on the test is similar to the problem #86. Therefore could be that issue, I will go an fallow that threat. I will let you know there. Thanks, |
Is your feature request related to a problem? Please describe.
Like in the Closed ticket #55
it would be nice to have a automatic ticket renewal mechanism.
Describe the solution you'd like
A soon as the ticket expires, and Proxmox throw the "invalid PVE ticket" exception, plugin should catch this and ask for a new ticket.
Describe alternatives you've considered
I have tried pasting the ticket inside compute resource password field, but it did not help. And I think it will only work for another two hours, please correct me if I am wrong about it.
The text was updated successfully, but these errors were encountered: