saltstack / saltstack/salt

ERROR! No Top file or master_tops data matches found when i try to run jobs using gitfs.

Open
#67,036 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hello everyone,

I've been working on setting up Salt and would like to start with a straightforward topology: Master => Syndic => Windows Minion. Managing SLS files via GitHub and executing jobs through this configuration is essential for my setup. However, I’ve encountered an error, which I described on the header. Additionally, I’m sharing my configuration files below to provide better context.

Thank you in advance for your assistance.

Salt Version: 3006.9

Master:
/etc/salt/master

user: salt
fileserver_backend:
  - git
gitfs_provider: pygit2
gitfs_remotes:
  - https://github.com/birkanthedev/salt.git
order_masters: True

Syndic:
/etc/salt/master

user: salt
fileserver_backend:
  - git
gitfs_provider: pygit2
gitfs_remotes:
  - https://github.com/birkanthedev/salt.git
syndic_master: <masterip>

I can succesfully ping the windows minion.
image

When i run the command salt '*' state.apply , I get an error.
image

Thank you!

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 with the /etc/salt/master configurations and the GitHub repository used by gitfs, then run salt '*' state.apply while checking how the Master and Syndic resolve the top file. Compare the reported error and screenshots with the repository contents; done means the missing top-file or master_tops cause is identified and the job can resolve its SLS target.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.