We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It appears our wiki generation is showing incorrect cloud expiration times:
[root@quads2-stage quads]# quads --ls-schedule --host f36-h21-000-r640.example.com Default cloud: cloud01 Current cloud: cloud05 Current schedule: 168 168| start=2024-06-18T10:45, end=2024-07-02T22:00, cloud=cloud05
[root@quads2-stage quads]# quads --ls-schedule --host f18-h31-000-1029p.example.com Default cloud: cloud01 Current cloud: cloud05 Current schedule: 169 169| start=2024-06-18T10:45, end=2024-06-29T22:00, cloud=cloud05
I would expect for all systems to show 2024-07-02 except for the f18-h31 host which had their schedule manually reduced to 2024-06-29 22:00
It also appears (on the wiki side) that VLAN ownership isn't being updated properly
[root@quads2-stage quads]# quads --ls-vlan 619: cloud05 620: Free
The text was updated successfully, but these errors were encountered:
fix: cloud expiration on wiki
cfac27b
fix: vlan ownership on wiki closes: #493 Change-Id: I7e183846e516c44e3b3b25844557849713c61314
https://review.gerrithub.io/c/redhat-performance/quads/+/1196428
Sorry, something went wrong.
grafuls
No branches or pull requests
It appears our wiki generation is showing incorrect cloud expiration times:
I would expect for all systems to show 2024-07-02 except for the f18-h31 host which had their schedule manually reduced to 2024-06-29 22:00
It also appears (on the wiki side) that VLAN ownership isn't being updated properly
The text was updated successfully, but these errors were encountered: