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

user password and tags always being applied even if there were no actual changes in pillar #46

Open
kirill-aga opened this issue May 24, 2017 · 1 comment

Comments

@kirill-aga
Copy link

I've got following section in my pillar (there is nothing else related to rabbitmq):

  rabbitmq:
  enabled: True
  running: True
  vhost:
    vh_name: 'rcce_vhost'
  user:
    rcce_rabbit:
      - password: '*my*secure*password*'
      - force: True
      - tags: monitoring, user
      - perms:
        - '/':
          - '.*'
          - '.*'
          - '.*'

state file for the minion uses the rabbitmq-formula only once, calling 'main' state. Issuing 'state.apply' command brings every time the same message as if the new user has been created, despite no actual changes in pillar:

          ID: rabbitmq_user_rcce_rabbit
    Function: rabbitmq_user.present
        Name: rcce_rabbit
      Result: True
     Comment: 'rcce_rabbit' was configured.
     Started: 06:48:57.213331
    Duration: 1850.237 ms
     Changes:   
              ----------
              password:
                  ----------
                  new:
                      Set password.
                  old:
              tags:
                  ----------
                  new:
                      - monitoring,
                      - user
                  old:
                      - monitoring
                      - user

@EvaSDK
Copy link

EvaSDK commented May 14, 2018

Afaik the problem is in rabbitmq tools not allowing this information to be queried to avoid re-applying it. The salt module then has no choice but to apply your state over and over again. This is extremely annoying for this kind of automation but this needs some discussion with upstream I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants