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

Error when status beacon fires (2016.11.0) #37976

Closed
dclfan opened this issue Nov 29, 2016 · 1 comment
Closed

Error when status beacon fires (2016.11.0) #37976

dclfan opened this issue Nov 29, 2016 · 1 comment
Assignees
Labels
Beacon Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt P2 Priority 2 severity-high 2nd top severity, seen by most users, causes major problems
Milestone

Comments

@dclfan
Copy link

dclfan commented Nov 29, 2016

Description of Issue/Question

Trying to setup status beacon in new version running on vagrant. Minion throws an error each time it fires.

[CRITICAL] The beacon errored:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/salt/minion.py", line 2153, in handle_beacons
beacons = self.process_beacons(self.functions)
File "/usr/lib/python2.7/site-packages/salt/minion.py", line 409, in process_beacons
return self.beacons.process(b_conf, self.opts['grains']) # pylint: disable=no-member
File "/usr/lib/python2.7/site-packages/salt/beacons/init.py", line 100, in process
raw = self.beaconsfun_str
File "/usr/lib/python2.7/site-packages/salt/beacons/status.py", line 131, in beacon
ret[func][item] = data[int(item)]
ValueError: invalid literal for int() with base 10: 'a'

Setup

(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)

/etc/salt/minion.d/beacon.conf:

beacons:
  status:
   - interval: 10

I have also tried:

beacons:
  status:
    interval: 10

and:

beacons:
  status: {}

Steps to Reproduce Issue

(Include debug logs if possible and relevant.)

Versions Report

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)

Salt Version:
Salt: 2016.11.0

Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.7.2
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
pygit2: Not Installed
Python: 2.7.5 (default, Sep 15 2016, 22:37:39)
python-gnupg: Not Installed
PyYAML: 3.10
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.2.1511 Core
machine: x86_64
release: 3.10.0-327.36.3.el7.x86_64
system: Linux
version: CentOS Linux 7.2.1511 Core

@Ch3LL
Copy link
Contributor

Ch3LL commented Nov 30, 2016

@t0nyhays looks like I can replicate this.

Here is a docker container for anyone wanting to replicate:

  1. docker run -it -v /home/ch3ll/git/salt/:/testing/ ch3ll/issues:37976 (where /home/ch3ll/git/salt is a local clone git salt repo)
  2. salt-master -d
  3. salt-minion -ldebug and you will see the error in the foreground.

Looks like we need to get this fixed up thanks

@Ch3LL Ch3LL added Beacon Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt P2 Priority 2 severity-high 2nd top severity, seen by most users, causes major problems labels Nov 30, 2016
@Ch3LL Ch3LL added this to the Approved milestone Nov 30, 2016
@meggiebot meggiebot modified the milestones: Nitrogen 1, Approved Nov 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Beacon Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt P2 Priority 2 severity-high 2nd top severity, seen by most users, causes major problems
Projects
None yet
Development

No branches or pull requests

4 participants