Closed Zwordi closed 4 months ago
Thanks for the report @Zwordi. I've identified the problem and it will be fixed in the next release.
Hi, Great to know :) Thanks,
Hi @Zwordi,
The rundeck_exporter v2.7.0 has been released and might fix this problem. If you get a chance, please try the new version and let me know.
Hi,
Will be done this week. I will let you know.
Thanks,
20 avr. 2024 16:25:26 Phillipe Smith @.***>:
Hi @Zwordi[https://github.com/Zwordi],
The rundeck_exporter v2.7.0[https://github.com/phsmith/rundeck_exporter/releases/tag/v2.7.0] has been released and might fix this problem. If you get a chance, please try the new version and let me know.
— Reply to this email directly, view it on GitHub[https://github.com/phsmith/rundeck_exporter/issues/89#issuecomment-2067690228], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACDL2X3WJ5OUKDK52VSP5B3Y6J3E5AVCNFSM6AAAAABGEAIVRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGY4TAMRSHA]. You are receiving this because you were mentioned. [Image de pistage][https://github.com/notifications/beacon/ACDL2X734SKJXTZ35AVA3LDY6J3E5A5CNFSM6AAAAABGEAIVRGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT3HZZPI.gif]
I just deployed your latest version in few VMs no more output about this issue visible. Closing this issue. Thanks,
Hello,
Running 2.6.5 we’re getting this traceback toward rundeck 4.11:
This doesn’t prevent the exporter to run but we would like to share this situation.
Thanks