salt-call schedule.list doesn't work when minion not running

[OrangeDog]

Description of Issue

This may be expected behaviour?

# systemctl stop salt-minion
# salt-call schedule.list
local:
    ----------
    schedule:
        ----------
# systemctl start salt-minion
# salt-call schedule.list
local:
    schedule:
      enabled: true
      highstate:
        enabled: true
        function: state.apply
        jid_include: true
        kwargs:
          saltenv: base
        maxrunning: 1
        minutes: 15
        name: highstate
        returner: zabbix
        run_on_start: true
        splay: 60

https://gist.github.com/OrangeDog/fd08470a682752347efd52fe7a5b830d

[garethgreenaway]

@OrangeDog Thanks for the report. This is actually expected behavior, in order to get the schedule items and ensure they are current, we use the event bus system. If the minion isn't running then the event bus is also not running. For things like schedule.list though we could maybe fall back and pull the results out of the saved configuration.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[waynew]

@garethgreenaway so would that make this a feature request, then?

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[OrangeDog]

Unstale

…

On 6 Feb 2020, at 22:36, stale[bot] ***@***.***> wrote: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[OrangeDog]

unstale

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[OrangeDog]

unstale

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[garethgreenaway]

The PR that allowed offline use of the schedule module has been merged, so closing this one out.