"bug" in service module: failing to disable (enabled=no) legacy sysv services on systemd target

[Nusenu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I'm not entirely sure whether this should be considered an ansible or
systemctl bug.
This email mainly targets of making others aware of this problem.

If you want to disable (enabled=no) a service on a systemd host which
is still using legacy sysv init.d scripts, ansible will fail to do so.
Systemd in general has a certain degree of backwards compatibility for
such services.

I had a short look in service.py (ansible v1.9.0.1-1).
The module executes
systemctl is-enabled <service>
in line 486 to

I you do this for a legacy service you will get:

"Failed to get unit file state for FOO.service: No such file or director
y"
(retval=1)

I guess this is why ansible believes the service is disabled already,
if it would actually run 'systemctl disable' on this service it would
achieve what one would expect: (manually invoked)

systemctl disable tor
Synchronizing state for tor.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d tor defaults
Executing /usr/sbin/update-rc.d tor disable
insserv: warning: current start runlevel(s) (empty) of script `tor'
overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
`tor' overrides LSB defaults (0 1 6).

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVKtS/AAoJEFv7XvVCELh0RKEP+wVkktwXamUplXUyrvOgVDhm
yJdID4jBtvdEXfjWdCXzH7duia5L5PvNXPRo9VLTh2fKYMoPB/ouN4d+wfP+Hu2c
aJEjCROgeYgdOlhMj4FcHOfSCy0pAFid0Xgl6+venAptHORSuhJEOQC3cMs9wY1m
fVlpiqjloAQU7j0wBDF/SuCpueLEz3sSz4Qd+AABnMQyXneEdg0MDzfC5gnYQ2L4
jkl4rFU63NY9p/5IJPPNd7mPkVkcXWD3NrRSFGF4bCOBObkbBEn0iQBqFcEhnLxM
1iHculRb0aU6DZ7Zu0a28Mx3umkmfDTgQSrdKxBJHOizYVow9l9U5PFmgN9HC/mK
iR6jyxKwGWaE4i1qJjYH5i4/9kpch5A58BMbzlHMbqMRQ0TYC3O8tVoA2LCE90PH
GlnwhvhamvcZhjMWpWzx/qIcABJuuACgbS51q79DM5hxfwmP8LoFSjqWIXgSUCBR
qxTxfZcKYAXm+KC/Q3FwqnlPKWb4PojZmFDPK+A6EN4vdQ0FZfuy7rw+CE+X9Ifp
LS42bmNKBhEtSSgyYQd+x0qfwE+LwR/7DJ2DrC3/qqwDXfsTWHWEUsZM5Myq/UO/
Bn6Sz/+DQ6KavXDq47zl2HTUGa++r0kMOqIiLy4j0JpAQ0gcY7LkfaMwYYurscrU
RNXYQhqzhvPZzggmWVSL
=71On
-----END PGP SIGNATURE-----

[Nusenu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I asked systemd-devel about is-enabled support for legacy services:

http://lists.freedesktop.org/archives/systemd-devel/2015-April/030652.ht
ml
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVKt2bAAoJEFv7XvVCELh0u8oQAKW4BGaeGDhjKc21TeQiXuqZ
lyUVxk0WQ7JdgngX2c34fuq5ey2c/F4wJrtsn8O4jg4hZIXpFKaN73mcqyCpjqpD
Uv5FKOdzi119TxXZpLfVPrBywrXBWZe4Sr+Vr7FrD8tIPt5Kf3heOKIBXJlHb6VB
ZH+/ay3O2mgVw2jqsq7W6W0vhNDQjjFnqJIF1M83TK5YVyPPFIuU9Vgp4f0XQkom
lP/7KppW7v5p6Z7KAyDaM2qILx7LTcQ8gtsG3oqDMEVy3vJxNoQnRr3Jv2o/xcYi
GKjzx4pgWGwCYkFBmYIxxiy2lSVU11lTysFvi/AjZ4z3IKzoKqO5DhoNgksB/Unv
Z48YUmmMjnilH5eFoIrpdRd2SKW0XP6lv635s+pP4uCu05lE9SKaBhAyTOiNYQmA
Hd6BTsij2wdbQY+YZLhoaXGAy+Ko1egRDtwleBOLDQ/y5ad6aZXUEyfIvNF4FBoc
mOQn+bga2ojQ+zhGK42VOzpEAknpUpZtLR11ne4/ozT/Uidu3dTL+Te1mmH6ZGWe
MTBRLPMnovbdyv/oJZTDfIZ3FaDfkZ2Vgxy7cJzxKmVVq8XaNAsozxbdx/iRS1mt
EEuWnX2aLlu1xUNodkUgYYNkZEGHc2+DMw4CTbtjAkws2MRL5TZCZZIEC9oBMZNJ
Idt3EpP/YmUd4x0J4CaJ
=HfuM
-----END PGP SIGNATURE-----

[Nusenu]

for the record, this is a known debian systemd bug that affects
ansible's service module:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751638

[Nusenu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> for the record, this is a known debian systemd bug that affects
> ansible's service module:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751638

https://github.com/ansible/ansible-modules-core/issues/915
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVK4G4AAoJEFv7XvVCELh00wYP/3LKOclS++qbyy/eOA/rhj5h
4/Is6gH7Q+f16Pdf13/dNOy1ZC39lLAI9jRb5habwKNWVZZJ1vUkl8vdX9CNqpnv
1kvAjupx53eHykD3LPUrDZ9cng0WGTNCyOzFqes23i/D55TjYnt3zhqwVQsetpRA
WofLS6/r3hljwtwbxsO1/D80f4fsukA9fZsPNhSzgwJnML0CbcHVFiFEjxP81jxL
FlQRDeC1RLdL1cnZJNcDZTsqWzaudRtbUd6xVkHIduiA4xymTDIJqHNMxmCbydmX
JNa+/6CO4QA/aWtP0hQbH5ZrJhYgWf+/eOu1Nz+4trga8816mDK081+6kMSUJF7+
egzG6V8Ce0uEtcfT3LByLBL8RP3meLLgAV4xGs2BsBt/A61zjO9/6Mf3pnB4g9bo
a5581TWzISLIMQLncXzZTmJDi7XRA6R6udm0u9K2fKsGWYRcJmsAYzbTEXq4QvMJ
HbrgOD9IWww4dF7qYWBZcYRvnGHPQbgoA5kXlSFlurtSuS0nf0aNmAd8YaDhpmSt
9beDG7vONUNzC+qXo0oLbRYz/NdWFxCBjpAvZYFMXJt8K5ER40rF6XQYptFyx7bT
sIp468gNrLKx4/JsWtpJU5lRtezUWrEROg+Ku9Ymof1EZWrUjABi58e/w8ul+ABW
d+Tru6iyF3HXNU2Zynvq
=jXN3
-----END PGP SIGNATURE-----

[nusenu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

just in case other are also stumbling over this debian systemd bug,
this was my temporary workaround until debian fixes this issue:


https://github.com/nusenu/ansible-relayor/commit/efabec452f715b884528e70
a9b1e012051692acd


if you want to track the debian bug entries:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705254
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751638

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVQTdDAAoJEFv7XvVCELh0Q5QP/jcVBc4oKG/eWtdtzsMDAIDx
eep0BVYTAvbJT/MkQzqxwIgrbOStruO+6GYyFT3udDJJBCl8jRJ9MQ1CY/Cf07Rp
Gj5+lb8FJNYkX6sZgMxzXIgbfNz8Z5sYKGAgoGOtxboQqINVVtCUkuzdcEwPwnTj
CMp6q6gC+8EkOLlpV3XR7VGL1WSBoQQlP9oauPg/54suD85v3WTC05iDFIkBChYU
CTy2PT7AzWwsVQ58dOQQe5wr8f8jhpiG9pmDIFscj07D89I8UajSyNEfjucXaFSw
YrqMI6pnsP5kYBZCcvAxel3cjNtGRO87udFMFQbnTbgC1R780xChmdwqIHXMDlyj
lshQHAtzTnViK43jQzavp7JK2spoZFbhK6GcJul2v3SeAztR81Hc4pq8sMb4C1BL
CLhKuRdi2n9rzh60VtTwQ4VQMwaI3Mnqu+uv7XcYPe0ZvHYxtBX+AafbPLfawrkd
jq5Z+EtLoeHpQqRczAHuuUH4nIORYvc5Kb/s0OCYYql7sJKJx0WGyF9QaoYmabr0
6iNH9TmVygsCehB1Ms5uQ4GFY3IKPtmrqmzti/zbFrLVtHssj2eXu+JeWOBv1n3u
CNHuzzI5ZzxOI4K+sFeABNVWBQ8hNJWBH/mJvNJnSDtIR11LFS9jaaNogJjN0gxP
pjTetPC/D8hwkjVN/0JF
=frbo
-----END PGP SIGNATURE-----