Fix issue with timezones when adding new schedule #952
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.
When adding a new automate task schedule the value for time zones are decoded, then if a time zone contains an ampersand (like
Eastern (US & Canada
) the value is split on the ampersand. This change leaves the time zone encoded when sent to the server.https://bugzilla.redhat.com/show_bug.cgi?id=1435735
This bug also exists in Fine and Euwe
@miq-bot add_label bug, fine/yes, euwe/yes
/cc @h-kataria