Closed abednarik closed 5 years ago
This might be a version issue.
After it worked fine in centos 7 I decided to check ubuntu. 14.04 didn't work however if i uninstalled the python-augeas
ubuntu package. Than forced setuptools and wheel to upgrade.. and installed gcc, python-dev and libffi-dev. I could pip install python-augeas
. After all that it worked correctly in ubuntu 14.04.
ubuntu 16.04 didn't have the problem and worked with the package installed by the os.
zd-2891
Thanks for the quick response @whytewolf !
Will try that, as a workaround, until this issue is fixed. Will let you now how this one goes.
Cheers.
Did that and worked. We have time to wait for a real fix.
Thanks.
Closing this out, if the problem persists please comment & we'll re-open the issue or feel free to open a new issue.
Hi @garethgreenaway
What we did was a hack. Ideally salt should work with python-augeas provides by the OS or either when you bootstrap salt, that version should be installed.
Cheers.
@abednarik Did you get a chance to try PR #50690?
Yeah, I can try that. Not sure which version of salt contains that fix @garethgreenaway
@abednarik unfortunately the fix is not in a released version yet so would need to manually patch it or download the file from GitHub, from the 2018.3 branch. It will be available once we released the next minor version of 2018.3 though.
Thanks @garethgreenaway . At point, I;m super busy with work things, Will see what I can do in the future. For sure once new salt version based on branch 2018.3 is released will upgrade and check this.
Thanks.
Description of Issue/Question
We have a state to update /etc/service and include a new entry. After applying that state, we don't the change in configuration file.
BTW This is working with salt 2017.7.5 but not in 2018.3.2
Setup
Here is a sample state file
Here is the relevant part of the log
and this is salt output
Steps to Reproduce Issue
Just create a state like the one posted above and run it. Check /etc/service and find out that the file does not include the new entry
Versions Report
Not sure if this could be related to unicode change