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

Minion status through Syndic not reported correctly on Master #63071

Open
jlrcontegix opened this issue Nov 16, 2022 · 2 comments
Open

Minion status through Syndic not reported correctly on Master #63071

jlrcontegix opened this issue Nov 16, 2022 · 2 comments
Labels
Bug broken, incorrect, or confusing behavior needs-triage Salt-Syndic

Comments

@jlrcontegix
Copy link

Description
It appears the bug reported in #25028 has returned in 3005.1. When running 'salt-run manage.status' on the MoM, only "up" minions are displayed, despite multiple down minions behind the Syndic. When run from the Syndic we see multiple minions that are down.

Setup
Single Master-of-Masters and single Syndic both running 3005.1. All minions also running 3005.1.

Steps to Reproduce the behavior
On MoM check status (in this example minion1 and minion2 are connected to the MoM and minion3-5 are connected to the Syndic):

# salt-run manage.status
down:
up:
    - minion1
    - minion2
    - minion4
    - minion5

On Syndic check status:

# salt-run manage.status
down:
    - minion3
up:
    - minion4
    - minion5

Expected behavior
Expect to see the down minions when running manage.status from the MoM.

Versions Report

salt --versions-report
# salt --versions-report
Salt Version:
          Salt: 3005.1

Dependency Versions:
          cffi: Not Installed
      cherrypy: unknown
      dateutil: Not Installed
     docker-py: Not Installed
         gitdb: 0.6.4
     gitpython: 1.0.2
        Jinja2: 2.11.1
       libgit2: Not Installed
      M2Crypto: 0.35.2
          Mako: Not Installed
       msgpack: 0.6.2
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     pycparser: Not Installed
      pycrypto: Not Installed
  pycryptodome: Not Installed
        pygit2: Not Installed
        Python: 3.6.8 (default, Nov 16 2020, 16:55:22)
  python-gnupg: Not Installed
        PyYAML: 3.13
         PyZMQ: 18.0.1
         smmap: 0.9.0
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.1.4

System Versions:
          dist: centos 7 Core
        locale: UTF-8
       machine: x86_64
       release: 3.10.0-1160.76.1.el7.x86_64
        system: Linux
       version: CentOS Linux 7 Core
@jlrcontegix jlrcontegix added Bug broken, incorrect, or confusing behavior needs-triage labels Nov 16, 2022
@welcome
Copy link

welcome bot commented Nov 16, 2022

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!

@OrangeDog
Copy link
Contributor

See also #62577

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 needs-triage Salt-Syndic
Projects
None yet
Development

No branches or pull requests

2 participants