-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Open
Labels
Milestone
Description
Description
A schedule job has been created in a multiamster (active/active) minion.
The following occurs when the first master is not available/unreachable,
running schedule.run_job schedule_new_task
throws Job schedule_new_task does not exist.
But the job is present by schedule.list
command
Somehow the job is tied to the first master ?
PS C:\Users\adrian> salt-call schedule.run_job schedule_new_task -l info
[INFO ] Master saltmaster-pip could not be reached, trying next master (if any)
[WARNING ] Master ip address changed from 172.21.0.10 to 172.21.0.11
local:
----------
comment:
Job schedule_new_task does not exist.
result:
False
PS C:\Users\adrian> salt-call schedule.list
[INFO ] Master saltmaster-pip could not be reached, trying next master (if any)
[WARNING ] Master ip address changed from 172.21.0.10 to 172.21.0.11
local:
schedule:
schedule_new_task:
args:
- utils.reboot_system_module
enabled: true
function: state.sls
jid_include: true
maxrunning: 1
name: some.example.statefile
return_job: true
returner: rawfile_json
saved: true
splay: 10
when:
- '2024-07-16 19:56:33'
PS C:\Users\adrian> salt-call schedule.run_job schedule_new_task -l info
[INFO ] Master saltmaster-pip could not be reached, trying next master (if any)
[WARNING ] Master ip address changed from 172.21.0.10 to 172.21.0.11
local:
----------
comment:
Job schedule_new_task does not exist.
result:
False
# using --local triggers the job, but does not complete succesfully given the first master is unreachable
PS C:\Users\adrian> salt-call --local schedule.run_job schedule_new_task -l info
local:
----------
comment:
Scheduling Job schedule_new_task on minion.
result:
True
Setup
3006.x Multimaster minion (active/active) with scheduled job set
The first master is not available/reachable when the commands are executed
Expected behavior
I'd expect the minion to be able to run the scheduled job, despite the first master not being available