check if there attributes to set

[pc-explore]

Add fix for issue 76727: check if there attributes to set before attempting to set them

SUMMARY

When there are no attributes to be set, the command 'chattr' will fail with 'Operation not supported' when setting the attributes of the backupfile.
Fixes #76727

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

lib/ansible/module_utils/basic.py b/lib/ansible/module_utils/basic.py

ADDITIONAL INFORMATION

Error before change:
_Error while setting attributes: ./test-76727.txt.3395762.2022-09-04@19:05:40~: Operation not supported_

[lancedikson]

Just encountered a similar issue and the PR seems potentially could work in my case. I'm trying to edit the /etc/resolv.conf which is a symlink and it doesn't get through

    - name: Set ndots to 5 in resolv.conf
      lineinfile:
        path: /etc/resolv.conf
        regexp: '^options.*'
        line: '{{ (item|regex_replace("^options", "")|trim + " ndots:5") if item is search("ndots:") else "options ndots:5" }}'
        backup: no
      loop: "{{ lookup('file', '/etc/resolv.conf').splitlines() }}"
      tags:
        - ndots

And get the exception:

The full traceback is:
Traceback (most recent call last):
  File "/tmp/ansible_lineinfile_payload_vvsy6qs8/ansible_lineinfile_payload.zip/ansible/module_utils/basic.py", line 1003, in set_attributes_if_different
    raise Exception("Error while setting attributes: %s" % (out + err))
Exception: Error while setting attributes: /etc/resolv.conf.2644211.2023-04-16@08:57:43~: Operation not supported

failed: [server-0] (item=#) => {
    "ansible_loop_var": "item",
    "changed": false,
    "details": "Error while setting attributes: /etc/resolv.conf.2644211.2023-04-16@08:57:43~: Operation not supported\n",
    "gid": 103,
    "group": "systemd-resolve",
    "invocation": {
        "module_args": {
            "attributes": null,
            "backrefs": false,
            "backup": true,
            "create": false,
            "firstmatch": false,
            "group": null,
            "insertafter": null,
            "insertbefore": null,
            "line": "options ndots:5",
            "mode": null,
            "owner": null,
            "path": "/etc/resolv.conf",
            "regexp": "^options.*",
            "search_string": null,
            "selevel": null,
            "serole": null,
            "setype": null,
            "seuser": null,
            "state": "present",
            "unsafe_writes": false,
            "validate": null
        }
    },
    "item": "#",
    "mode": "0644",
    "msg": "chattr failed",
    "owner": "systemd-resolve",
    "path": "/etc/resolv.conf.2644211.2023-04-16@08:57:43~",
    "size": 920,
    "state": "file",
    "uid": 102
}

[lancedikson]

Just tried the fix on ansible [core 2.14.3] — seems working for me! 👍

[webknjaz]

The branch is too old for the CI to pick it up. This needs a rebase.

[Akasurde]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).