On Wed, 4 Apr 2018, 18:52 Kevin Fenzi, <kevin(a)scrye.com> wrote:
On 04/04/2018 10:46 AM, Kevin Fenzi wrote:
> On 04/04/2018 09:21 AM, James Hogarth wrote:
>> Can we please get some consistency here?
>> I noted today that firewalld has dropped python2-firewall but of course
>> ansible isn't switching to py3 for the controller (and therefore local)
>> until F29 and not all python modules are py3 compatible yet... and of
>> course we ship firewalld as our firewall in fedora.
>> This means that in F28 you can't just `yum install ansible
>> python-firewall` and do ansible localhost -m firewalld and have it work.
> Yeah, you would need to set ansible_python_interpreter for localhost,
> which you could add to your command line with -e...
> -e 'ansible_python_interpreter=/usr/bin/python3'
yum install ansible-python3 python-firewall
ansible localhost -m firewalld
(since ansible-python3 defaults to python3 for the control host/localhost)
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
You're right that solves the issue for the control host, assuming
everything else you are doing on there is fine with py3, but doesn't solve
F28 target systems.
It is also unexpected and not in and changes notes or common issues (yet)
What happens to systems that currently have the library during an upgrade?
It was just dropped from the spec (As many will be) rather than formally
retired so it's not added to the "this is dead" super obsoleting package.
Even if we don't get a change per library (which I agree would be too much)
can we please get something clear for the F28 (and later F29) release ...
we should be able to quickly generate it with dnf list