tover99 a9fd9f8982 added handling of zypper exitcode 102: ZYPPER_EXIT_INF_REBOOT_NEEDED (#6534) ... * added handling of zypper exitcode 102: ZYPPER_EXIT_INF_REBOOT_NEEDED - Returned after a successful installation of a patch which requires reboot of computer. The exitcode 102 will be treated exactly like 0 by the module internally now, and the changed status will be reported correctly. However, since I preserve the rc 102 in the retvals to allow the playbook to react to the requested reboot, the task must still include a "failed_when: zypper_cmd.rc not in [0, 102]" to not fail in this case. * removed trailing whitespaces * added changelogs fragment * Fix typo. Co-authored-by: Alex <alexgubin@gmx.de> * Add URL. --------- Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Alex <alexgubin@gmx.de>		2023-05-22 06:24:53 +02:00
..
.keep	Rename changelogs/fragments/.empty -> changelogs/fragments/.keep	2020-08-07 08:17:57 +02:00
6527-nmcli-bond-fix-xmit_hash_policy.yml	nmcli: Fix bond option xmit_hash_policy (#6527)	2023-05-21 17:03:38 +02:00
6534-zypper-exitcode-102-handled.yaml	added handling of zypper exitcode 102: ZYPPER_EXIT_INF_REBOOT_NEEDED (#6534)	2023-05-22 06:24:53 +02:00
6539-semantic-markup.yml	Enable using semantic markup (#6539)	2023-05-20 13:05:44 +02:00
6548-portage-changed_use-newuse.yml	portage: fix changed_use and newuse not triggering rebuilds (#6008) (#6548)	2023-05-21 21:36:46 +02:00