[Automation] Fixed time zone issue while creating an update deploymen…

…t schedule (Azure#14565) * Bug 9534965: New-AzAutomationSoftwareUpdateConfiguration cmdlet is creating schedule by taking the UTC value as the StartTime instead of local time. * Update ChangeLog.md Updating ChangeLog.md Co-authored-by: Debashish Mohanta <[email protected]>
AzureSDKAutomation · Apr 1, 2021 · 1c7c155 · 1c7c155
1 parent 21a7a7d
commit 1c7c155
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/src/Automation/Automation/ChangeLog.md b/src/Automation/Automation/ChangeLog.md
@@ -22,6 +22,7 @@
 
 ## Version 1.5.2
 * Fixed the issue for starting Python3 runbooks with parameters
+* Fixed time zone issue while creating an update deployment schedule.
 
 ## Version 1.5.1
 * Fixed te issue that complex object cannot be serialized correctly. [#14431]

diff --git a/src/Automation/Automation/Common/AutomationPSClientSoftwareUpdateConfiguration.cs b/src/Automation/Automation/Common/AutomationPSClientSoftwareUpdateConfiguration.cs
@@ -81,8 +81,8 @@ public SoftwareUpdateConfiguration CreateSoftwareUpdateConfiguration(string reso
                 {
                     ScheduleInfo = new Sdk.ScheduleProperties()
                     {
-                        StartTime = configuration.ScheduleConfiguration.StartTime.ToUniversalTime(),
-                        ExpiryTime = configuration.ScheduleConfiguration.ExpiryTime.ToUniversalTime(),
+                        StartTime = configuration.ScheduleConfiguration.StartTime,
+                        ExpiryTime = configuration.ScheduleConfiguration.ExpiryTime,
                         Frequency = configuration.ScheduleConfiguration.Frequency.ToString(),
                         Interval = configuration.ScheduleConfiguration.Interval,
                         IsEnabled = true,