Ignore repeat/reboot on dry run commands for Zypper #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the package manager returns code 102 (
REBOOT_REQUIRED
) or 103 (ZYPPER_UPDATED
, will need to repeat last patch installation) from a dry run command, it will get stuck in a loop. It gets stuck in a loop because although the dry run command returns a non-zero exit code indicating that a specific action needs to be taken, this action will only need to be taken once the command is actually run and does not apply for the dry run command. The dry run command is a preview of what would happen when the command is run.For code
REBOOT_REQUIRED
, it breaks out of the loop because the maintenance window is exceeded.For code
ZYPPER_UPDATED
, it breaks out of the loop on the second attempt because of this code:This PR fixes this problem by not taking any specific actions when these exit codes are returned. If one of these exit codes is returned on a dry run command, it's logged, and execution continues normally without repeating installation/rebooting.