bdrx312

During the gather-facts stage of running ansible-playbook, I get a similar error stack trace as #645 on ansible 2.7.5 rhel 7.7 using python2-mitogen 0.2.8. Are there any work arounds or...

I believe changing https://github.com/saltstack/salt/blame/5d86ead778983fd87e074a2093abe002e244aab8/salt/modules/yumpkg.py#L1456-L1457 to ```python version = kwargs.get("version") if version is not None: kwargs["version"] = str(version) ``` would fix the issue; a quick simple 2 line change. I will...

> > Ive been thinking about potential workarounds for this. > > Maybe some alternative from/import functions which could allow an alternative python library path to search in? > >...

> @bdrx312 Please retry the issue with the latest 3006.2, a number of fixes have been made since 3006.0 was released. I did not realize that 3006.2 was out already....

> @bdrx312 Tried this with Salt 3005.1 classic packaging and it failed, wondering if there is something missing in the instructions I added the salt minion configuration `/etc/salt/minion` to set...

> @bdrx312 Even in masterless with file_client local, I am still unale to reproduce this with Salt 3006.1, and do not see a SaltRenderError in the logs: > > ```...

I just tried also on a fresh `bento/ubuntu-22.04` vagrant vm and experienced the same behavior. Try manually clearing your cache with `salt-call --local saltutil.clear_cache` and then re-run the `state.apply` ```...

Being able to see in the report that tests were skipped because they were ignored or disabled would also be useful for us. It doesn't matter for us if the...

Is there any chance this was fixed in a new version or is going to be fixed? We still experience this bug with version 2.2.8.

> Could we get a test for this please? Added