Skip to content
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

Closed
pdzionek opened this issue Apr 30, 2019 · 5 comments
Closed

Invalid PVE ticket renewal #77

pdzionek opened this issue Apr 30, 2019 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@pdzionek
Copy link

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.

@tristanrobert tristanrobert added the enhancement New feature or request label Apr 30, 2019
@tristanrobert tristanrobert added this to To do in ForemanFogProxmox plugin via automation Apr 30, 2019
@tristanrobert tristanrobert added this to the 0.8.0 milestone Apr 30, 2019
@tristanrobert tristanrobert modified the milestones: 0.8.0, 0.9.0 May 8, 2019
@Yamakasi
Copy link

Yamakasi commented May 8, 2019

I hope to have this seen in 0.8.0

Is it a complex issue ?

@tristanrobert
Copy link
Collaborator

tristanrobert commented May 9, 2019

It is indeed a Fog-Proxmox bug. I release now 0.8.0 and this bug will be fixed in a 0.8.1.

@tristanrobert tristanrobert modified the milestones: 0.9.0, 0.8.0 May 9, 2019
@tristanrobert tristanrobert added bug Something isn't working and removed enhancement New feature or request labels May 9, 2019
@tristanrobert tristanrobert modified the milestones: 0.8.0, 0.8.1 May 10, 2019
@TekunoKage
Copy link

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.

@pdzionek
Copy link
Author

pdzionek commented Jul 4, 2019

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.

@TekunoKage
Copy link

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,

@tristanrobert tristanrobert moved this from To do to In progress in ForemanFogProxmox plugin Aug 3, 2019
ForemanFogProxmox plugin automation moved this from In progress to Done Nov 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

4 participants