search

saltstack-formulas / php-formula

http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
Other
57 stars 232 forks source link

Passed invalid arguments to state.apply: 'NoneType' object is not iterable - on php.ng.fpm.pools #147

Open arthurzenika opened 6 years ago

arthurzenika commented 6 years ago

When using salt target state.apply php.ng.fpm.pools with no pillars, we get : 

    Passed invalid arguments to state.apply: 'NoneType' object is not iterable

In our case, the php.ng.fpm.pools is included in the top.sls and so no states are applied which is a problem. 

    Salt Version:
               Salt: 2017.7.4

    Dependency Versions:
               cffi: Not Installed
           cherrypy: Not Installed
           dateutil: 2.5.3
          docker-py: Not Installed
              gitdb: Not Installed
          gitpython: Not Installed
              ioflo: Not Installed
             Jinja2: 2.9.4
            libgit2: Not Installed
            libnacl: Not Installed
           M2Crypto: Not Installed
               Mako: Not Installed
       msgpack-pure: Not Installed
     msgpack-python: 0.4.8
       mysql-python: Not Installed
          pycparser: Not Installed
           pycrypto: 2.6.1
       pycryptodome: Not Installed
             pygit2: Not Installed
             Python: 2.7.13 (default, Nov 24 2017, 17:33:09)
       python-gnupg: Not Installed
             PyYAML: 3.12
              PyZMQ: 16.0.2
               RAET: Not Installed
              smmap: Not Installed
            timelib: Not Installed
            Tornado: 4.4.3
                ZMQ: 4.2.1

    System Versions:
               dist: debian 9.4 
             locale: UTF-8
            machine: x86_64
            release: 4.9.0-5-amd64
             system: Linux
            version: debian 9.4
n-rodriguez commented 5 years ago

@myii I think we can close this one

myii commented 5 years ago

Thanks for the heads-up, @n-rodriguez.

@arthurlogilab I've just tested with the latest version and php.fpm.pools (after the ng deprecation) and I can't reproduce this. Can you confirm if it is still a problem at your end?