-
Notifications
You must be signed in to change notification settings - Fork 45
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
Support salt 3000.2 #650
Comments
If we do this, I'd suggest we don't just "support" 2019.2.0, because in the end we (currently) own the whole stack, but go all the way and deploy those versions of master and minion as well. |
Agreed, I'll also go further and deploy Python 3 versions as well (which in turn implies packaging of some dependencies, e.g. |
Update: using Salt 2019.2.0 is currently blocked due to saltstack/salt#51869 It seems using Python 3 does not raise this bug, however it implies large amounts of packaging for dependencies missing in EPEL/Salt repository (in particular for the Thus, we will wait for a fix upstream and let the minions run in Python2, until #626 and #691 move all packaging needs to the Salt-master container only. |
Would it make sense to monkey-patch around this issue as hinted at in saltstack/salt#51869 (comment), or alternatively copy a 'fixed' version of the module/procedure in an extmod we ship? I'd like to move forward with 2019.2 without waiting for 2019.2.1 being released, if possible... |
I guess we can use the monkey-patch, since we already have our own |
Exactly. At the same time, whenever we copy some code from Salt I failed to do so in the past myself, will do so in two places at least. Let's discuss to find a proper common format for this. |
HI Nicolas/Team, ./upgrade[2019-08-01 11:51:47+01:00] Update modules ... OK where as all my minions are up |
Hello @shqnayaz, Thanks for reaching out. Your question relates to the installation/upgrade of Scality RING, which is a product not related to MetalK8s, the open-source project backed by Scality developed in this repository. Please refer to the Scality RING documentation and the support channels available to you as a Scality customer so we can help you further. Thank you, Nicolas |
The blocker is now fixed in upstream Salt releases v2019.2.1 and v2019.2.2. |
Sometimes we use a complex structure as an interpolated value in an SLS file. Whilst this works, this is merely by accident, and Salt 2019.2 changes the behaviour: complex values would be spliced in using their `unicode` representation, including `u""` markers. As such, use a proper `tojson` filter in the Jinja templates instead. See: #650 See: #650 See: https://docs.saltstack.com/en/latest/topics/releases/2019.2.0.html#non-backward-compatible-change-to-yaml-renderer
Change salt-master image to salt 3000.2 and download salt-minion version 3000.2 Fixes: #650
Change salt-master image to salt 3000.2 and download salt-minion version 3000.2 Fixes: #650
Sometimes we use a complex structure as an interpolated value in an SLS file. Whilst this works, this is merely by accident, and Salt 2019.2 changes the behaviour: complex values would be spliced in using their `unicode` representation, including `u""` markers. As such, use a proper `tojson` filter in the Jinja templates instead. See: #650 See: #650 See: https://docs.saltstack.com/en/latest/topics/releases/2019.2.0.html#non-backward-compatible-change-to-yaml-renderer (cherry picked from commit 0dbcbd1)
Change salt-master image to salt 3000.2 and download salt-minion version 3000.2 Fixes: #650
Change salt-master image to salt 3000.2 and download salt-minion version 3000.2 Fixes: #650
…lt-3000' into w/2.1/improvement/GH-650-upgrade-to-salt-3000
…/octopus/w/2.3/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.4/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.4/improvement/GH-650-upgrade-to-salt-3000
Change salt-master image to salt 3000.2 and download salt-minion version 3000.2 Fixes: #650
…lt-3000' into w/2.1/improvement/GH-650-upgrade-to-salt-3000
…/octopus/w/2.3/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.4/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.5/improvement/GH-650-upgrade-to-salt-3000
…/octopus/w/2.5/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.5/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.6/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.5/improvement/GH-650-upgrade-to-salt-3000
…-to-salt-3000' into w/2.6/improvement/GH-650-upgrade-to-salt-3000
…/octopus/w/2.2/improvement/GH-650-upgrade-to-salt-3000
…/2504/2.5/improvement/GH-650-upgrade-to-salt-3000' into tmp/octopus/q/2.6
Currently salt 2019.2.0 is not supported as we use yaml information directly.
So unicode instead of string
https://docs.saltstack.com/en/latest/topics/releases/2019.2.0.html#non-backward-compatible-change-to-yaml-renderer
The text was updated successfully, but these errors were encountered: