-
Notifications
You must be signed in to change notification settings - Fork 391
Re-enable extension policy tests in daily runbook #3607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,15 +1,13 @@ | ||
| # | ||
| # The test suite verifies that disallowed extensions are not processed, but the agent should still report status. | ||
| # | ||
| # TODO: This test suite takes ~30 minutes to run. This should be optimized to reduce impact to pipeline run times. | ||
| name: "ExtensionPolicy" | ||
| tests: | ||
| - "ext_policy/ext_policy.py" | ||
| images: | ||
| - "endorsed" | ||
| - "random(endorsed,10)" # TODO: Remove randomization and run on all endorsed images once the test suite is optimized to reduce runtime. | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I made the decision to limit this scenario to 10 random endorsed images per day, in addition to all 6 cvm-endorsed images. That gives us coverage across 16 images per daily run. I made this change because each run of this suite takes ~30 minutes (primarily due to the delete scenario waiting on 15min CRP timeout). If this test runs on all 30 endorsed images, most of the 32 available lisa runners will be stuck on the environments with this scenario, preventing us from processing other environments, and we get pipeline timeouts. I've added a TODO to optimize this test, but in the meantime, I think it's appropriate to only run on 10 of the endorsed images and all of the cvm-endorsed images. If we want more coverage, we can extend the pipeline timeout instead as a temporary measure until the test is optimized. |
||
| - "cvm-endorsed" | ||
| # This test is executed in southcentralus as a workaround for recurring fabric "ServiceUnavailableFault" issues observed in westus2. | ||
| locations: "AzureCloud:southcentralus" | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Previously this ran on southcentralus when we only ran on 'endorsed' images, but the CVM sku we're using is not available in southcentralus. Instead of updating the location for the entire test suite to westeurope (where the CVM sku is available), I just updated the CVM image definitions in images.yml to list the regions it is available in. Now, this suite will run on the default location (westus2) for the 'endorsed' images and westeurope for the 'cvm-endorsed' images (since that is the first region listed in the image.yml definitions for those cvm images). This reduces the # of environments created per test run |
||
| # TODO: This test is currently failing on usgov cloud due to an issue with the GuestConfig extension. Re-enable once the extension fix has been rolled out. | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I checked and I'm not seeing that issue in USGov anymore, the test is passing there. There are GuestConfig ext failures in China cloud now though, but only on the debian_11 image, so I am skipping that one only |
||
| skip_on_clouds: | ||
| - "AzureUSGovernment" | ||
| owns_vm: false | ||
| skip_on_images: | ||
| - "AzureChinaCloud:debian_11" # The ConfigurationforLinux-1.26.109 extension is failing on Debian 11 in China cloud only; skip this image until the issue in the extension is fixed | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,11 +4,11 @@ | |
| name: "ExtPolicyWithDependencies" | ||
| tests: | ||
| - "ext_policy/ext_policy_with_dependencies.py" | ||
| images: "endorsed" | ||
| images: | ||
| - "endorsed" | ||
| - "cvm-endorsed" | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After reading this comment, I confirmed that the CVM VMSS are being created with the default sku (Standard_D2s_v3) instead of the CVM sku from the images.yml (Standard_DC2ads_v5): Good catch by Copilot :) I'll fix it
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed |
||
| executes_on_scale_set: true | ||
| owns_vm: false | ||
| # This test is executed in southcentralus as a workaround for recurring fabric "ServiceUnavailableFault" issues observed in westus2. | ||
| locations: "AzureCloud:southcentralus" | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same reasoning for removing the location here as the ext_policy scenario |
||
|
|
||
| # TODO: Currently AlmaLinux is not available for scale sets; enable this image when it is available. | ||
| skip_on_images: | ||
|
|
@@ -18,4 +18,4 @@ skip_on_images: | |
|
|
||
| # TODO: The current deployment of VmAccess 1.5.22 prevents the extension from uninstalling; enable this test when the issue is fixed | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nora confirmed v1.5.24 of VMaccess with the fix for this will hit USGov regions by end of this week, so we should be able to remove this soon |
||
| skip_on_clouds: | ||
| - "AzureUSGovernment" | ||
| - "AzureUSGovernment" | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,7 +7,6 @@ tests: | |
| # Extension signature is sent by CRP only for CVMs, so this test suite should run exclusively on CVMs. | ||
| images: "cvm-endorsed" | ||
| # Extension signatures are currently only available in the public cloud, so we skip this test on other clouds. | ||
| locations: "AzureCloud:westeurope" | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We specified the location for this suite, since there the CVM sku we're using is only available in certain regions. I updated the CVM image definitions in images.yml with the locations they are able to be used on, so this is no longer necessary. |
||
| skip_on_clouds: | ||
| - "AzureChinaCloud" | ||
| - "AzureUSGovernment" | ||
|
|
||

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, we were depending on LISA to correctly deploy VMs with the 'ConfidentialVM' security type when using our *_cvm image definitions (even though those images can be used for TrustedLaunch or Standard VMs).
Now, we explicitly tell lisa to deploy CVMs when using those images instead of relying on their selection logic.