v1.6.24

• Includes bugfixes for IO errors originating in the extension handler
• Includes mitigation for Azure agent updates not creating the events folder
• Includes improvements and fixes in the auto-assessment code for Azure - updates to LifecycleManager to incorporate even more concurrent instances.
• Fix for IO errors in bad FileLogger close calls
• Support for healthStoreId and updated maintenancerunid contract

v1.6.23

• updated automaticOsPatchState property to automaticOSPatchState as new new spec
• Updated internal references of autoOSPatchState to follow the same convention

v1.6.22

This version contains:

• Bug fix for summaries from previous operation not preserved after auto assessment in status file. For eg: if the operation order was ConfigurePatching followed by Auto Assessment, status file after Auto Assessment should contain PatchAssessmentSummary (refreshed by Auto Assessment) and ConfigurePatchingSummary. Included unit tests to cover this usecase

• Bug fix for main/outer operation name overwritten to Assessment by Auto Assessment. For eg: if the operation order was ConfigurePatching followed by Auto Assessment, operation name in status file after Auto Assessment should be 'ConfigurePatching' Included unit test to cover this

• Bug fix for reading boolean string values correctly. bool() which was used earlier, will always return True, even for bool('False')

• Bug fix for reading 'processIds' from CoreState.json. Were using the wrong key earlier

• Syntax corrections in many places as per standard practice

• Tests were taking longer to execute due to IMDS connection retries and were initializing LifecycleManagerArc for Azure tests. Fixed by mocking connection to set cloud type as Azure

• Added additional logging in a few places

• Added unit test for ConfigurePatching with different configs for patchMode and assessmentMode

• Adding zypper process tree on package manager failures to telemetry

v1.6.21

This release includes changes to:

• determine VM Cloud Type : Azure or Arc
• When running on Arc, the extension is able to determine state of arc extension and follow one of these paths: If arc extension is not running when auto assessment is triggered by timer, the auto assessment continues its execution. If arc extension is running in parallel, the auto assessment logs error message and exits execution.

v1.6.20

This release includes:

• Configure patching support
• Fix for patch install marked failed before implicit assessment
• fix for SSL certificate expired on RedHat
• auto-assessment support
• mitigation for reboot always covering multiple reboots

v1.6.19

This version contains bug fixes for:

• Telemetry error - 'Execution could not complete. Internal reporting error' exception
• Core unable to execute sudo commands, mostly seen in RHEL 7.2
• Updating Installation substatus only after implicit assessment is completed.
• Updates to error message reported when agent does not support telemetry
• Installation should surface if operation exits due to assessment failures
• Adding error details in substatus, when failure occurs during core setup

v1.6.18

This release includes:
• Bug fix for frequent reboots in RHEL due to an extra reboot check
• Fix for sys.version_info not containing attribute 'major' in python 2.6
• Fix for python 2.6 not containing total_seconds() in datetime
• Change to install all available patches on CentOS for an Auto Patching request
- Unit test to verify the functionality in CentOS
- Unit test to verify Redhat machines are not affected by this change.

v1.6.17

Release 1.6.17 includes:

• Fix for unit tests failing in python3
• Bug fix for telemetry event count throttle
• Additional logging for telemetry writer events
• Bug fix for core not working in python 3
• Fix for list index out of range exception

v1.6.16

This version includes

• Telemetry added in core
• Refactoring telemetry in handler to make it similar to core

v1.6.15

Includes:

• Reverting changes from previous version which was used for testing preview mode telemetry in agent
• Telemetry added in handler
• Execution stopped in core if telemetry is not enabled