Unschedule yast2_lan_restart_devices when Network Manager-2nd try #5788
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.
Unschedule yast2_lan_restart_devices when Network Manager-2nd try. It is a correction for #5780
Similar logic could be:
unless (is_opensuse && !is_leap('>15.0'))
Neither of them is very readable, but unless with negate conditon inside I guess is worst.
I think both cover all products, if it SLE is scheduled, if is opensuse only if is leap <=15.0 so TW (or any opensusue) is excluded which is ok.