You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When creating or changing a beacon using pillar definitions, after appling changes on the Master and refreshing the pillars, the new beacon definition is ok when running beacons.list, but it only starts running accordingly after restarting the minion. The behavior of beacons.list was fixed in the context of #42676, but the changes didn't fix the behavior of the running beacons.
Setup
1 Master and 1 Minion both running salt 3005.1 on Ubuntu 22.04
Please be as specific as possible and give set-up details.
used bootstrap to install
Steps to Reproduce the behavior
Description of Issue/Question
When creating or changing a beacon using pillar definitions, after appling changes on the Master and refreshing the pillars, the new beacon definition is ok when running beacons.list, but it only starts running accordingly after restarting the minion. The behavior of beacons.list was fixed in the context of #42676, but the changes didn't fix the behavior of the running beacons.
Setup
1 Master and 1 Minion both running salt 3005.1 on Ubuntu 22.04
Steps to Reproduce Issue
Start master
Start the minion with trace log level to see details of beacons execution salt-minion -l trace
Confirm in the logs that there is no beacon running. Running salt '*' beacons.list also returns an empty list.
Running salt '*' beacons.list returns empty, but then running salt '*' saltutil.refresh_pillar makes it return the correct beacon definitions, including the load beacon.
Confirm in the logs that the minion remains without any beacon running
Restart the minion keeping trace logging and confirm that the new beacon is running
Expected behavior
After changing beacons definitions in pillar data, when beacons.list returns up-to-date definition, the beacons should be running according to what is defined.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
Salt Version:
Salt: 3005.1Dependency Versions:
cffi: Not Installedcherrypy: Not Installeddateutil: 2.8.1docker-py: Not Installedgitdb: 4.0.9gitpython: 3.1.24Jinja2: 3.0.3libgit2: Not InstalledM2Crypto: Not InstalledMako: 1.1.3msgpack: 1.0.3msgpack-pure: Not Installedmysql-python: Not Installedpycparser: Not Installedpycrypto: Not Installedpycryptodome: 3.11.0pygit2: Not InstalledPython: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0]python-gnupg: 0.4.8PyYAML: 5.4.1PyZMQ: 22.3.0smmap: 5.0.0timelib: Not InstalledTornado: 4.5.3ZMQ: 4.3.4System Versions:
dist: ubuntu 22.04 Jammy Jellyfishlocale: utf-8machine: x86_64release: 5.15.0-58-genericsystem: Linuxversion: Ubuntu 22.04 Jammy Jellyfish
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
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 saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!
Description
When creating or changing a beacon using pillar definitions, after appling changes on the Master and refreshing the pillars, the new beacon definition is ok when running
beacons.list
, but it only starts running accordingly after restarting the minion. The behavior ofbeacons.list
was fixed in the context of #42676, but the changes didn't fix the behavior of the running beacons.Setup
1 Master and 1 Minion both running salt 3005.1 on Ubuntu 22.04
Please be as specific as possible and give set-up details.
Steps to Reproduce the behavior
Description of Issue/Question
When creating or changing a beacon using pillar definitions, after appling changes on the Master and refreshing the pillars, the new beacon definition is ok when running
beacons.list
, but it only starts running accordingly after restarting the minion. The behavior ofbeacons.list
was fixed in the context of #42676, but the changes didn't fix the behavior of the running beacons.Setup
1 Master and 1 Minion both running salt 3005.1 on Ubuntu 22.04
Steps to Reproduce Issue
Start master
Start the minion with trace log level to see details of beacons execution
salt-minion -l trace
Confirm in the logs that there is no beacon running. Running
salt '*' beacons.list
also returns an empty list.Setup the beacon on the Master:
Master /srv/pillar/top.sls
Master /srv/pillar/load_beacon.sls
Running
salt '*' beacons.list
returns empty, but then runningsalt '*' saltutil.refresh_pillar
makes it return the correct beacon definitions, including the load beacon.Confirm in the logs that the minion remains without any beacon running
Restart the minion keeping trace logging and confirm that the new beacon is running
Expected behavior
After changing beacons definitions in pillar data, when
beacons.list
returns up-to-date definition, the beacons should be running according to what is defined.Screenshots
If applicable, add screenshots to help explain your problem.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: