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

quads-cli --host <hostname> --date <some date> sometimes has incorrect result #285

Closed
kambiz-aghaiepour opened this issue Sep 26, 2019 · 1 comment

Comments

@kambiz-aghaiepour
Copy link
Contributor

commented Sep 26, 2019

If a host has an active schedule that expires in the future, the expected result of:

   quads-cli --host <some host> --date "<some future date when schedule expires>"

should be:

  cloud01

but instead quads-cli reports back the current cloud, despite the fact that the schedule will expire sending the host back to cloud01. For example:

# quads-cli --host somehost.example.com
cloud05
# quads-cli --host somehost.example.com --ls-schedule
Default cloud: cloud01
Current cloud: cloud05
Current schedule: 6
2| start=2019-07-30 02:00, end=2019-08-01 16:00, cloud=cloud27
4| start=2019-08-01 16:00, end=2019-09-01 22:00, cloud=cloud16
5| start=2019-09-05 08:10, end=2019-09-06 11:56, cloud=cloud29
6| start=2019-09-08 22:00, end=2019-10-06 22:00, cloud=cloud05
7| start=2019-09-06 12:53, end=2019-09-07 22:00, cloud=cloud29
# quads-cli --host somehost.example.com --date '2019-10-06 22:01'
cloud05
@sadsfae sadsfae changed the title quads --host <hostname> --date <some date> sometimes has incorrect result quads-cli --host <hostname> --date <some date> sometimes has incorrect result Sep 27, 2019
@grafuls grafuls self-assigned this Oct 8, 2019
@grafuls

This comment has been minimized.

@sadsfae sadsfae closed this in ece5fef Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.