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

[BUG] custom grains not working with salt-call #65873

Closed
2 tasks done
ysagon opened this issue Jan 16, 2024 · 6 comments
Closed
2 tasks done

[BUG] custom grains not working with salt-call #65873

ysagon opened this issue Jan 16, 2024 · 6 comments
Labels
Bug broken, incorrect, or confusing behavior needs-triage

Comments

@ysagon
Copy link

ysagon commented Jan 16, 2024

Description
Since the update to 3006.5 custom grains aren't working with salt-call. They still do work with salt 'my_host'.

Setup
my custom grains are in /srv/salt/state/_grains/

  • on-prem machine
  • onedir packaging

Steps to Reproduce the behavior
No grains returned, launched from admin1.baobab

(baobab)-[root@admin1 state] (master *)$ salt-call grains.get mellanox_card

Grains returned, launched from admin1.baobab

(baobab)-[root@admin1 state] (master *)$ salt 'admin1.baobab'  grains.get mellanox_card
admin1.baobab:
    ConnectX-5

Expected behavior
same grains when using salt and salt-call

I did previously:

salt "admin1.baobab" saltutil.sync_grains

and

salt-call saltutil.sync_grains

Versions Report

salt --versions-report (Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
(baobab)-[root@admin1 state] (master *)$ salt --versions-report
Salt Version:
          Salt: 3006.5

Python Version:
        Python: 3.10.13 (main, Nov 15 2023, 04:34:27) [GCC 11.2.0]

Dependency Versions:
          cffi: 1.14.6
      cherrypy: unknown
      dateutil: 2.8.1
     docker-py: 7.0.0
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 3.1.2
       libgit2: Not Installed
  looseversion: 1.0.2
      M2Crypto: Not Installed
          Mako: Not Installed
       msgpack: 1.0.2
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     packaging: 22.0
     pycparser: 2.21
      pycrypto: Not Installed
  pycryptodome: 3.9.8
        pygit2: Not Installed
  python-gnupg: 0.4.8
        PyYAML: 6.0.1
         PyZMQ: 23.2.0
        relenv: 0.14.2
         smmap: Not Installed
       timelib: 0.2.4
       Tornado: 4.5.3
           ZMQ: 4.3.4

System Versions:
          dist: rocky 8.8 Green Obsidian
        locale: utf-8
       machine: x86_64
       release: 4.18.0-477.27.1.el8_8.x86_64
        system: Linux
       version: Rocky Linux 8.8 Green Obsidian
@ysagon ysagon added Bug broken, incorrect, or confusing behavior needs-triage labels Jan 16, 2024
@ysagon
Copy link
Author

ysagon commented Jan 16, 2024

I tried with our previous version 3006.3 it is working as expected.

@ysagon
Copy link
Author

ysagon commented Jan 16, 2024

I tried to keep salt-master to version 3006.5 and downgrade the minion to 3006.4 and it is working as well.

@max-arnold
Copy link
Contributor

The issue is already tracked here #65027

@ysagon
Copy link
Author

ysagon commented Jan 16, 2024

Or this one? #65692

@Foorack
Copy link
Contributor

Foorack commented Jan 30, 2024

Yup, #65692 and was merged in #65738. Will likely go into next 3006.x, so only solution for now is to downgrade from to 3006.4.

@ysagon
Copy link
Author

ysagon commented Jan 30, 2024

Thanks, I'm closing this issue as it is already tracked.

@ysagon ysagon closed this as completed Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior needs-triage
Projects
None yet
Development

No branches or pull requests

3 participants