saltstack / saltstack/salt

state.event runner does not display events if using eauth.

Open
#53,174 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description of Issue/Question

Set up eauth and use the state.event runner to try showing the events coming through the master.

The command will run and display nothing. Other runners work fine.

Setup

I setup master stats and the status beacon so I would have an almost constant stream of events.
and then ran salt-run -a pam state.event pretty=true and waiting. nothing ever showed up. Was asked to log in and then no output.

When run without -a pam events start pouring in without much wait.

Steps to Reproduce Issue
  • Setup eauth
  • make sure events are being generated.
  • salt-run -a pam state.event pretty=true and wait for an event
Versions Report
[root@salt00 salt]# salt --versions
Salt Version:
           Salt: 2019.2.0

Dependency Versions:
           cffi: 1.11.5
       cherrypy: Not Installed
       dateutil: 1.5
      docker-py: Not Installed
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
         Jinja2: 2.7.2
        libgit2: Not Installed
        libnacl: 1.6.1
       M2Crypto: Not Installed
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.5.6
   mysql-python: Not Installed
      pycparser: 2.14
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.5 (default, Apr  9 2019, 14:30:50)
   python-gnupg: Not Installed
         PyYAML: 3.13
          PyZMQ: 15.3.0
           RAET: Not Installed
          smmap: Not Installed
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4

System Versions:
           dist: centos 7.6.1810 Core
         locale: UTF-8
        machine: x86_64
        release: 3.10.0-957.12.1.el7.x86_64
         system: Linux
        version: CentOS Linux 7.6.1810 Core

Again also happens in 2018.3 so also not a regression. or a very old one.

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 issue with the state.event runner and salt-run -a pam state.event pretty=true, using the eauth and status-beacon setup described. Trace the eauth execution path and compare it with unauthenticated state.event; done means events are displayed when authentication is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.