2.4.10 soup caused permanent highstate #12824
Replies: 2 comments 2 replies
-
Is this an ISO install? If not what OS are you using? What version of salt is installed? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
SO 2.4.10 soft-broke after running
sudo soup
. We originally wanted to restart the system due to Kibana web services not responding, however, we were advised to run soup prior to that. Upon soup finishing,init 6
andreboot
wouldn't restart the system and ended up usingsystemctl reboot -i
.Receiving the below when running
sudo salt-call state.highstate
. We even let the server sit for a full day and received the following response fromsudo so-status
, "System appears to be starting. No highstate has completed since the system was restarted."The /opt/so/log/salt/master log doesn't show anything interesting. However, we're noticing that elastic is showing 85% full errors.
I even gave soup another shot and now it wants to upgrade from 2.4.10 to 2.4.60, but refuses due to the highstate issue.
Anybody have any clues to look for any root or underlying issues? Better yet, anyone know how to get back to functional?
Beta Was this translation helpful? Give feedback.
All reactions