Compatiblity issue with ansible.netcommon 5.0.0?

[boneyard]

Due to a new Check Point Ansible mgmt collection version coming up I was looking into upgrading collections with ansible-galaxy.

I tested with the ansible.netcommon which was 4.1.0 on my system and I upgraded to 5.0.0.

Afterwards I couldn't run any playbooks on Check Point SMS (R81.10), they ended at the first step. Looking at the api.elg log I saw a login attempt which returned a 415 and no real cause.

Once I downgraded to 4.1.0 all was well again. I did not make any other changes.

Is there a known issue with ansible.netcommon version 5.0.0 and Check Point mgmt (and possibly gaia, didnt test) collection?

[PhoneBoy]

Just to be clear, you updated another module and it broke our mgmt collection?

[boneyard]

Yes, after the upgrade of the ansible.netcommon collection (which is used to connect to the SMS I assume) I can't run anyone of the mgmt collection tasks anymore. They exit with a HTTP 415 response during the login action.

For reference this the API log with the upgraded ansible.netcommon. With just going back to 4.1.0 it works again.

2023-04-12 09:53:13,280  INFO org.apache.cxf.interceptor.LoggingInInterceptor.log:250 [qtp1210870650-145] - Inbound Message
----------------------------
ID: 1484
Address: http://127.0.0.1:60307/web_api/login
Encoding: ISO-8859-1
Http-Method: POST
Content-Type: application/x-www-form-urlencoded
Headers: {accept-encoding=[identity], Authorization=[Basic <removed>], connection=[keep-alive], Content-Length=[73], content-type=[application/x-www-form-urlencoded], Host=[127.0.0.1:60307], User-Agent=[Python-urllib/3.9], X-Forwarded-For=[10.10.32.16], X-Forwarded-Host=[hostname.domain.ext:443], X-Forwarded-Host-Port=[443], X-Forwarded-Server=[192.168.4.2]}
--------------------------------------
2023-04-12 09:53:13,281  INFO org.apache.cxf.interceptor.LoggingOutInterceptor.log:250 [qtp1210870650-145] - Outbound Message
---------------------------
ID: 1484
Response-Code: 415
Content-Type:
Headers: {Date=[Wed, 12 Apr 2023 07:53:13 GMT], Content-Length=[0]}
--------------------------------------

[PhoneBoy]

@chkp-royl Can you comment on this?

[Eden_Brillant · Accepted solution]

Hi,
Ansible support team explained to us that it was another manifestation of ansible-collections/ansible.netcommon#524.
Issue was fixed in their new version 5.1.0.

Regards,

Eden