saltstack / saltstack/salt

[BUG] [3001] No matching sls found for ... in env base

Open
#57,716 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug severity-medium
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

Description
salt-master need to be restarted after calling a script with salt 3001.
This script is committing /pushing my git remote fs code and is clearing cache, synchronizing module, functions... My code clear_all.sh, is available here.

If I don't restart the master I get the message No matching sls found for 'XXX' in env 'base' for every states (which are actually presents).

On the target side, I tested minion in 3001 and other versions, I still have the same error.

Setup

salt-call --versions-report
Salt Version:
           Salt: 3001
 
Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 2.6.1
      docker-py: Not Installed
          gitdb: 2.0.3
      gitpython: 2.1.8
         Jinja2: 2.10
        libgit2: Not Installed
       M2Crypto: Not Installed
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.5.6
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
   pycryptodome: 3.4.7
         pygit2: Not Installed
         Python: 3.6.9 (default, Apr 18 2020, 01:56:04)
   python-gnupg: 0.4.1
         PyYAML: 3.12
          PyZMQ: 17.1.2
          smmap: 2.0.3
        timelib: Not Installed
        Tornado: 4.5.3
            ZMQ: 4.2.5
 
System Versions:
           dist: ubuntu 18.04 Bionic Beaver
         locale: UTF-8
        machine: x86_64
        release: 4.15.0-50-generic
         system: Linux
        version: Ubuntu 18.04 Bionic Beaver

Steps to Reproduce the behavior
Upgrade master to 3001, then launch clear_all.sh -g=y, then try to deploy a state.

Expected behavior
Having no issue with No matching sls..., and restarting salt-master should not be mandatory.

Versions Report
See above.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with salt-master 3001 and clear_all.sh -g=y, then inspect the master’s cache and state synchronization behavior around the reported 'No matching sls found' error. Done means states remain available after the script runs and restarting salt-master is no longer required.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.