Skip to content

Update VMSS pool to one with vs16.7p2 - #851

Merged
Stephan T. Lavavej (StephanTLavavej) merged 4 commits into
microsoft:masterfrom
cbezault:update-to-16.7p1
Jun 20, 2020
Merged

Stephan T. Lavavej (StephanTLavavej) merged 4 commits into
microsoft:masterfrom
cbezault:update-to-16.7p1

Conversation

@cbezault

Copy link
Copy Markdown
Contributor

No description provided.

@cbezault Curtis J Bezault (cbezault) added the infrastructure Related to repository automation label May 20, 2020
@cbezault
Curtis J Bezault (cbezault) requested a review from a team as a code owner May 20, 2020 21:46
@cbezault

Copy link
Copy Markdown
Contributor Author

I have no idea why edg isn't getting found :(.

@StephanTLavavej Stephan T. Lavavej (StephanTLavavej) added the help wanted Extra attention is needed label May 27, 2020
@StephanTLavavej

Copy link
Copy Markdown
Member

I guess the next step to investigate is to prepare a VM with the script, and manually try to invoke cl /BE and see what happens?

@cbezault

Copy link
Copy Markdown
Contributor Author

Yup that would do it. You could also fuss around with making commits to this PR to do some debugging.

@AlexGuteniev

Copy link
Copy Markdown
Contributor

As there's p2 already, can you just try again with p2?

@cbezault

Copy link
Copy Markdown
Contributor Author

Sure

@cbezault Curtis J Bezault (cbezault) changed the title Update VMSS pool to one with vs16.7p1 Update VMSS pool to one with vs16.7p2 Jun 3, 2020
@cbezault

Copy link
Copy Markdown
Contributor Author

Same problem

@cbezault

Copy link
Copy Markdown
Contributor Author

Looks like the CoreIde component doesn't exist anymore and we're silently failing when we provision the machines.
image

@StephanTLavavej

Copy link
Copy Markdown
Member

To make investigations easier in the future, when command-line install fails like this, are logs emitted anywhere (or can we add an option to request them)? I guess we could reproduce this at will any time by attempting to install a nonexistent component.

@cbezault

Copy link
Copy Markdown
Contributor Author

I think the problem with this one is that we need to pass --quiet to the VS installer in order to make it run unattended but when that happens no logs or other indicators are emitted. All we could do is check the installed packages after the fact and make sure they match what we expect.

Also Lukasz notes that this is probably due to us using the Build Tools SKU and it was just working by luck previously.

@StephanTLavavej

Copy link
Copy Markdown
Member

Use command-line parameters to install Visual Studio - Error codes says:

Each operation generates several log files in the %TEMP% directory that indicate the progress of the installation. Sort the folder by date and look for files that begin with dd_bootstrapper, dd_client, and dd_setup for the bootstrapper, the installer app, and the setup engine, respectively.

and doesn't say that --quiet suppresses them. Are log files being emitted there? If so, could we make the script echo them?

@BillyONeal

Copy link
Copy Markdown
Member

It doesn't matter if the script could echo them because we don't get any output from the script when run through Invoke-AzVmRunCommand

@BillyONeal

Billy O'Neal (BillyONeal) commented Jun 10, 2020 •

Copy link
Copy Markdown
Member

(I debugged issues like this by running the script in a (local) VM)

@StephanTLavavej
Stephan T. Lavavej (StephanTLavavej) merged commit 42a8271 into microsoft:master Jun 20, 2020
@StephanTLavavej

Copy link
Copy Markdown
Member

Thanks for taking care of this update! I'll have to learn how to do the next one. 😸

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

high priority Important! infrastructure Related to repository automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants