Skip to content

Warn about refreshing grains after upgrading master to 3008.x #88

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.

Sign up for GitHub

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

Merged
twangboy merged 1 commit into from
Jul 10, 2026
Merged

Warn about refreshing grains after upgrading master to 3008.x #88

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/topics/upgrade.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,18 @@ To upgrade Salt:
#. With Salt now updated, verify your configuration is correct and restore it
if necessary.

.. Warning::
If you are upgrading a Salt master from 3006.x or 3007.x to 3008.x,
Salt 3008.0 restructured the master's minion data cache so that
grains are stored in a dedicated cache bank instead of a combined
per-minion blob. Cached grains data from a pre-3008 master is not
automatically migrated, which can cause grain-based targeting
(``-G``), ``mine.get``, and cached pillar/grains lookups to return
stale or empty results on the master. After upgrading the master,
run ``salt '*' saltutil.refresh_grains`` on minions (or wait for
their next scheduled pillar/highstate refresh) to repopulate the
master's grains cache.

If you stopped the daemon(s) prior to upgrading, you will need to restart the
daemons. See `Restart and upgrade minions used in state runs`_ for more information.

Expand Down
Loading