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
After upgrading from SO2.3.2 to SO2.3.10, the docker containers on my sensor nodes were not updated (still 2.3.2).
The init.sls files describing all of these containers clearly state that the containers should have the tag {{ VERSION }}, which is the global variable "soversion". This "soversion" in my config file is "2.3.10".
Manually deleting all containers and their respective images on the sensor, and reapplying highstate was my to go fix, but did not work.
This didn't work because highstate failed due to salt (on the sensor) was not updated to the right version, which in turn was caused by a yum issue.
Maybe important to know: I use my manager node as proxy for package updates.
The issue with yum was yum not being able to connect to the repositories, because it could not verify SSL certs.
I resolved this yum issue by adding sslverify=false to /etc/yum.conf.
Then I fixed the outdated salt issue by running /usr/sbin/bootstrap-salt.sh.
Once salt was updated, the salt-minion service would not start.
Rebooting the sensor resolved this, but did not allow me to apply highstate.
The fix to this was simply waiting a while, and then salt fixed itself!
Now my containers are up to date, and the custom line in /etc/yum.conf was removed by salt highstate.
I think this issue will reappear when salt gets updated again.
EDIT:
Only a single sensor suffered from this problem
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After upgrading from SO2.3.2 to SO2.3.10, the docker containers on my sensor nodes were not updated (still 2.3.2).
The init.sls files describing all of these containers clearly state that the containers should have the tag {{ VERSION }}, which is the global variable "soversion". This "soversion" in my config file is "2.3.10".
Manually deleting all containers and their respective images on the sensor, and reapplying highstate was my to go fix, but did not work.
This didn't work because highstate failed due to salt (on the sensor) was not updated to the right version, which in turn was caused by a yum issue.
Maybe important to know: I use my manager node as proxy for package updates.
The issue with yum was yum not being able to connect to the repositories, because it could not verify SSL certs.
I resolved this yum issue by adding
sslverify=false
to /etc/yum.conf.Then I fixed the outdated salt issue by running
/usr/sbin/bootstrap-salt.sh
.Once salt was updated, the salt-minion service would not start.
Rebooting the sensor resolved this, but did not allow me to apply highstate.
The fix to this was simply waiting a while, and then salt fixed itself!
Now my containers are up to date, and the custom line in /etc/yum.conf was removed by salt highstate.
I think this issue will reappear when salt gets updated again.
EDIT:
Only a single sensor suffered from this problem
Beta Was this translation helpful? Give feedback.
All reactions