Fixes for Compute Admin - #112
Merged
Merged
Conversation
|
@MatthewMcGlynn, |
Contributor
Author
|
Also included is handling Azure Stack module 1.2.8 and 1.2.9 for Compute Admin |
Contributor
Author
|
Validation Confirmed - Merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
a. I found the reason that Set-AzureRMBlobContent was faster. It turns out that the latter method leaves the VHD as dynamic when it makes its way into the PIR. This can cause a number of issues later on with VM lifecycle operations since CRP does not support dynamic disks. Add-AzureRMVHD implicitly makes it fixed by turning into a Page Blob.
a. This helps us prevent users from getting too far before we catch simple issues like ARM Endpoint parameters and creds mistakes
a. Tokens refresh every 5 minutes on the download
a. Check for the existence of the VHD – this suggests that the last state was a download or upload error (skip VHD creation)
b. Check for the existence of the VM Image – this suggests the VM Image made its way into the PIR, but that the Marketplace item component failed (skip VHD creation and upload/download)