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

State stuck in test mode #7788

Closed
marccardinal opened this issue Oct 12, 2013 · 4 comments · Fixed by #8141
Closed

State stuck in test mode #7788

marccardinal opened this issue Oct 12, 2013 · 4 comments · Fixed by #8141
Assignees
Labels
Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix severity-low 4th level, cosemtic problems, work around exists

Comments

@marccardinal
Copy link
Contributor

Here are my versions-report values:

Master:

           Salt: 0.17.0rc1
         Python: 2.7.3 (default, Aug  1 2012, 05:14:39)
         Jinja2: 2.7.1
       M2Crypto: 0.21.1
 msgpack-python: 0.1.10
   msgpack-pure: Not Installed
       pycrypto: 2.4.1
         PyYAML: 3.10
          PyZMQ: 13.0.0
            ZMQ: 3.2.2

Minion:

           Salt: 0.17.0
         Python: 2.7.3 (default, Sep 26 2013, 20:03:06)
         Jinja2: 2.6
       M2Crypto: 0.21.1
 msgpack-python: 0.1.10
   msgpack-pure: Not Installed
       pycrypto: 2.4.1
         PyYAML: 3.10
          PyZMQ: 13.0.0
            ZMQ: 3.2.2

In my minion configuration I have "test: True" and when I run the following on my master: salt "*" state.highstate test=False mystate

I get results in yellow counted under "Not run" like so:

Summary
-------------
Succeeded: 20
Failed:     0
Not Run:    2
-------------
Total:     22

Am I doing something wrong?

@basepi
Copy link
Contributor

basepi commented Oct 15, 2013

What OSs are you using? There is a bug in 0.17.0 in Windows where it can get stuck in test mode.

@marccardinal
Copy link
Contributor Author

I am running Ubuntu 12.04.2 LTS

@basepi
Copy link
Contributor

basepi commented Oct 16, 2013

OK, then it's probably not the same issue. Thanks for giving us the heads up, this should be fairly simple to resolve.

@cachedout
Copy link
Contributor

Good catch, @marccardinal. The above fix should do it.

s0undt3ch added a commit that referenced this issue Oct 28, 2013
Correctly evaluate the test kwarg when running a state.
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 fixed-pls-verify fix is linked, bug author to confirm fix severity-low 4th level, cosemtic problems, work around exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants