Update Update-AzVmssInstance.md #25627
Draft
Conversation
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
This change is proposed due to a change request by a customer from a case that I worked on as the Microsoft Azure Support Engineer. The customer submitted was VMSS update failure case to Azure Support. The case included an error message that stated that there was a "Conflict with concurrent request". The Cx used the parameters in this document to apply the updates to their VMSS instances. After some technical analysis with their cloud solution architect, it was the discovered that the -AsJob parameter in their commands was causing this error since the jobs were being asynchronously executed as background jobs and throws this concurrent request conflict error. I believe it would be good to state this in this documentation to help other Azure users prevent this error from occurring and resulting in an unhealthy VMSS instance. The customer also made this document update request.
Here is a sample of the command that the customer was running:
$VMSS = Get-AzVmssVM -ResourceGroupName "myResourceGroup" -VmScaleSetName "myScaleSet"
foreach ($bi in $VMSS)
{
Update-AzVmssInstance -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "myInstanceID" -AsJob | Out-Null
}
Thanks!
microsoftuser64
requested review from
bilaakpan-ms,
Sandido,
haagha and
grizzlytheodore
as code owners
🔄Az.Compute
|
|
Thank you for your contribution microsoftuser64! We will review the pull request and get back to you soon. |
|
@microsoft-github-policy-service agree company="Microsoft"
…________________________________
From: microsoft-github-policy-service[bot] ***@***.***>
Sent: Wednesday, July 24, 2024 3:05:11 AM
To: Azure/azure-powershell ***@***.***>
Cc: Urinrin Omughelli ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/azure-powershell] Update Update-AzVmssInstance.md (PR #25627)
@microsoftuser64<https://github.com/microsoftuser64> please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
* (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
* (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
1. Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org<http://www.opensource.org/>).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
* Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
* Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
* Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
1. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
3. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub<#25627 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDUA5HJGIXTUBYITWLLTO2TZN5N3PAVCNFSM6AAAAABLL5YRUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBXGE3DMMZWGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
#sign-off |
|
Is this issue caused by a service limitation? If so, we'd better add an explanation for the limitation in https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/, since the issue potentially happens in any clients except for Azure PowerShell. |
|
how it's showing in MD file: |
|
Will discuss with the team |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@microsoftuser64 The content of the document you added breaks static analysis and I try to move it to "Notes" section and it still fails. You have to remove some markdown labels to pass to static analysis. It may due to PlatyPS' limitation. |
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
|
Hi @microsoftuser64, Please join your github account to Azure org.
|
YanaXu
reviewed
Jan 7, 2025
| <br> | ||
| An example of where the "-AsJob" is used in the foreach loop is shown below: | ||
|
|
||
| ```powershell |
There was a problem hiding this comment.
Update this part to
<pre><code>
$VMSS = Get-AzVmssVM -ResourceGroupName "myResourceGroup" -VmScaleSetName "myScaleSet"
foreach ($bi in $VMSS)
{
Update-AzVmssInstance -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "myInstanceID" -AsJob
}
</code></pre>
|
@microsoftuser64 I am converting this PR as draft since it has no progress for long time. Please mark it as ready for review once the comments have been addressed. Thank you for your contribution! |
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.
This change is proposed due to a change request by a customer from a case that I worked on as the Microsoft Azure Support Engineer. The customer submitted was VMSS update failure case to Azure Support. The case included an error message that stated that there was a "Conflict with concurrent request". The Cx used the parameters in this document to apply the updates to their VMSS instances. After some technical analysis with their cloud solution architect, it was the discovered that the -AsJob parameter in their commands was causing this error since the jobs were being asynchronously executed as background jobs and throws this concurrent request conflict error. I believe it would be good to state this in this documentation to help other Azure users prevent this error from occurring and resulting in an unhealthy VMSS instance. The customer also made this document update request.
Here is a sample of the command that the customer was running:
$VMSS = Get-AzVmssVM -ResourceGroupName "myResourceGroup" -VmScaleSetName "myScaleSet" foreach ($bi in $VMSS)
{
Update-AzVmssInstance -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "myInstanceID" -AsJob | Out-Null
}
Thanks!
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.