Open TeddyAndrieux opened 3 years ago
Issue about salt-api get fixed in the branch just by mounting the salt cache directory in salt-api container
Still another issue about salt-ssh 3003 https://github.com/saltstack/salt/issues/60620 to be investigated if it can be workarouned easily
Issue https://github.com/saltstack/salt/issues/60620 still there with salt-ssh 3004
Branch with 3004 https://github.com/scality/metalk8s/compare/improvement/salt-3004
Issue https://github.com/saltstack/salt/issues/60620 still there with salt-ssh 3005.1 (but seems fixed in 3006, which means we need to move to onedir deployment)
Branch with 3005.1 https://github.com/scality/metalk8s/compare/improvement/bump-salt-3005
Component:
'salt'
Why this is needed:
To follow new Salt versions
What should be done:
Upgrade Salt to the latest version (3003.1 when this ticket get opened)
Implementation proposal (strongly recommended):
This branch https://github.com/scality/metalk8s/compare/improvement/salt-3003
May need some more investigation, An issue with Salt-API for the storage operator, I don't know if it's a bug in the new Salt version or if it's just something that changed in Salt-API (did not see anything related to this in Salt changelog).
When the storage operator tries to get the device name of a device the salt API return is wrong.
Manual tests output:
Salt API (existing device):
Salt call (existing device)
Salt call (device that does not exist)