Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
salt-cloud grains inheritance from provider to profile (2018 vs 2016) #49226
Description of Issue/Question
After upgrading salt-cloud from 2016.11.6 to 2018.3.2 we've been observing a situation when provider-specific grains have not been applied to the target instance.
Excerpt from our initial configuration that was working fine with 2016.11.6:
Target instance launched with 2016.11.6 contained all the grains merged in a proper way, i.e.:
Target instance launched with 2018.3.2 contained just the grains from profile:
We finally managed to get it working by changing provider configuration to the following:
However, documentation examples still contain older (legacy?) syntax:
My questions so far:
@gtmanfred I've been running all tests on 2018.3.3 branch in fact, sorry for not mentioning it. I searched for similar issues, found #45125 and realized that packaged salt-common 2018.3.2 does not contain changes from #47655, so I switched to git repository for tests and picked 2018.3.3 branch.
@gtmanfred I've just removed all .pyc files within salt directory, returned provider configuration to the initial format:
and checked with launching new instance from that profile - provider's grains are missing.
Let me know if I can provide anything else to help with investigating this one.
@defanator yes, our process is to label the ticket with the releases and this is also labeled with