When lvextend is called without any changes actually taking place, exit code is 5, indicating an error or failure
Issue
- If
lvextendis executed (for example, via Ansible scripts), and no actual resize takes place (i.e. no actual changes were done), the exit status is returned as5(EIO).- On previous RHEL versions the exit status is returned as '0' - indicating no errors.
- One of the impacts of this is that Ansible playbooks previously working successfully on RHEL7 and RHEL8, fail on RHEL9.
Environment
- Red Hat Enterprise Linux 9
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
