Jobs always says "no minions"

[pckroon]

Hello hello!
My job page correctly lists all salt jobs, but under the details it lists "no minions" for all jobs. When I "show details" for a specific job, it shows "minion list is missing in the result, thus cannot determine missing output" with the yellow warning symbol.
It's probably a config issue on my side, but I'm not sure where to look. Any help would be much appreciated!

[erwindon]

Peter,
The warning icon was added to confirm that this is a known situation.
But as far as I know it is not caused by SaltGUI (you can verify that by looking at a job that was not started from SaltGUI).
The (only) previous observation for this was from a user that uses a database as backing store for the jobs database.
This causes saltstack to 'forget' this data.
In #399, you can see that the "Minions" field is not stored.

This is a known issue at saltstack, see also saltstack/salt#61242.

[pckroon]

Wow you're fast :)
It's indeed the same (underlying) issue, with the only difference I'm using a pgjsonb returner. That seemed like a good idea at the time, but maybe it isn't?
I'll dig a little bit more, but I think this closes this issue. Thanks for the quick reply!

[erwindon]

I might contribute to the saltstack issue and cause this information to be stored also in the database.
Can you easily provide the data-model of the database? (e.g. an export with only the table structures)

[pckroon]

I basically followed this: https://docs.saltproject.io/en/latest/ref/returners/all/salt.returners.pgjsonb.html I guess that should contain the information you need. If it doesn't I can try a bit harder to get the export you need, but I'm no database hero.

[erwindon]

thx, that was exactly what I needed...
I had to choose postgres instead of pgjsonb, but the effect you described did not occur yet.
did you configure anything else except the returner and its database?
was there any special configuration on the minions?
did the problem occur for recent job data, older job data or both?

note:
I made the changes for #399 based on data supplied by the issue owner and just used that data as simulated response from salt.
That's why this is the first time I set up a salt system like this.

[pckroon]

did the problem occur for recent job data, older job data or both?

Both, but it started bothering me recently.

was there any special configuration on the minions?

No? Not that I'm aware of, anyway.

did you configure anything else except the returner and its database?

There is more config in my master conf, but this is all that seems relevant to the returner and saltgui.

root@salt:/etc/salt# grep pgjsonb master
#event_return: [pgjsonb]
master_job_cache: pgjsonb
#return: pgjsonb
returner.pgjsonb.host: '127.0.0.1'
returner.pgjsonb.user: REDACTED
returner.pgjsonb.pass: REDACTED
returner.pgjsonb.db: 'salt'
returner.pgjsonb.port: 5432
returner.pgjsonb.sslmode: 'require'
#returner.pgjsonb.ssl_ca: 
returner.pgjsonb.sslcert: '/etc/salt/pki/tls/certs/localhost.crt'
returner.pgjsonb.sslkey: '/etc/salt/pki/tls/certs/localhost.key'

root@salt:/etc/salt# cat master.d/*
rest_cherrypy:
  port: 8080
  host: 192.168.12.56
  debug: False
  ssl_crt: /etc/salt/pki/tls/certs/localhost.crt
  ssl_key: /etc/salt/pki/tls/certs/localhost.key
  log.error_file: /var/log/salt/api.error
  log.access_file: /var/log/salt/api.access
  collect_stats: False
  app: /srv/SaltGUI/saltgui/index.html
  static: /srv/SaltGUI/saltgui/static
  static_path: /static
saltgui_output_formats: highstate,yaml
saltgui_datetime_fraction_digits: 0
saltgui_preview_grains:
  - "$.fqdn_ip4[0]"
  - productname

Let me know if you need more, I'm happy to help :)

[erwindon]

at least one more person is also using saltgui_preview_grains :-)
both returners are commented out here. I assume that we are discussing a case where at least return: pgjsonb is set?
otherwise no surprises here, and I'll try to reproduce using pgjsonb...