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

salt reactor target - targets wrong minions #35250

Closed
msonawane opened this issue Aug 6, 2016 · 2 comments
Closed

salt reactor target - targets wrong minions #35250

msonawane opened this issue Aug 6, 2016 · 2 comments
Labels
cannot-reproduce cannot be replicated with info/context provided info-needed waiting for more info
Milestone

Comments

@msonawane
Copy link

msonawane commented Aug 6, 2016

Description of Issue/Question

salt reactor targets more minions than it should

Setup

following is reactor sls

salt-push:
  local.state.apply:
    - tgt: 'ops-1*'
    - queue: True
    - arg:
        - devops.pull_repo

Steps to Reproduce Issue

when i send an event from ops-2 minion like:
sudo salt-call event.send "devops_repo/updated {orchestrate: refresh}"

this causes action to be taken on both ops-1 and ops-2

Versions Report

ops-2:~$ salt --versions-report
Salt Version:
           Salt: 2016.3.2

Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 2.4.2
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: 0.21.1
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: 1.3.7
      pycparser: Not Installed
       pycrypto: 2.6.1
         pygit2: Not Installed
         Python: 2.7.12 (default, Jul  1 2016, 15:12:24)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: Not Installed
        timelib: Not Installed
        Tornado: 4.4.1
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
        machine: x86_64
        release: 4.4.0-28-generic
         system: Linux
        version: Ubuntu 16.04 xenial
ops1
salt --versions-report
Salt Version:
           Salt: 2016.3.2

Dependency Versions:
           cffi: 1.5.2
       cherrypy: 6.0.1
       dateutil: 2.4.2
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: 0.24.0
        libnacl: Not Installed
       M2Crypto: 0.21.1
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: 1.3.7
      pycparser: 2.14
       pycrypto: 2.6.1
         pygit2: 0.24.0
         Python: 2.7.11+ (default, Apr 17 2016, 14:00:29)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.3
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
        machine: x86_64
        release: 4.4.0-31-generic
         system: Linux
        version: Ubuntu 16.04 xenial
@Ch3LL
Copy link
Contributor

Ch3LL commented Aug 8, 2016

@msonawane i'm having a hard time replicating this with the following reactor sls:

salt-push:
  local.state.apply:
    - tgt: 'ch3ll-minion01*'
    - queue: True
    - arg:
        - test

And the following minions:
ch3ll-minion01
ch3ll-minion02

can you share your master config? And paste anything relevant from the debug logs? Particularly when the reactor is started and where its targeting both minions. Thanks

@Ch3LL Ch3LL added this to the Blocked milestone Aug 8, 2016
@Ch3LL Ch3LL added cannot-reproduce cannot be replicated with info/context provided info-needed waiting for more info labels Aug 8, 2016
@msonawane
Copy link
Author

I removed and added minions back. that solved the problem. closing it for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cannot-reproduce cannot be replicated with info/context provided info-needed waiting for more info
Projects
None yet
Development

No branches or pull requests

2 participants