cloud-only with date sometimes returns current set of hosts in cloud, if no schedules match the date given #466
Milestone
Comments
sadsfae
pushed a commit
that referenced
this issue
Jan 31, 2024
When calling cli with both --cloud-only and --date, if there are no matching schedules, the current set of hosts is incorrectly returned. Fixes: #466 Change-Id: Ifb7f9da1e899c03829b6e38e1a712b1293898db2
sadsfae
pushed a commit
that referenced
this issue
Feb 8, 2024
When calling cli with both --cloud-only and --date, if there are no matching schedules, the current set of hosts is incorrectly returned. Fixes: #466 Change-Id: Ifb7f9da1e899c03829b6e38e1a712b1293898db2
|
Let's see if we can get a patchset into gerrit for the |
|
@kambiz-aghaiepour can we confirm if this is still an issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rpm -qa | grep quadsand/orquads-cli --version): 1.1.7 gaúchoWhen calling : quads-cli --cloud-only --cloud cloudXX --date
if there are no hosts that match the given date, instead of returning nothing, quads is defaulting to return the current set of hosts in cloudXX
The text was updated successfully, but these errors were encountered: