Fix Compute Instance performance monitoring VCR failure - #17887
Conversation
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 231dbb7: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 6 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. |
231dbb7 to
b4eaa08
Compare
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit b4eaa08: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. |
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @malhotrasagar2212, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
8ce500e to
0b0b481
Compare
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 8ce500e: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @Capstan, @malhotrasagar2212 VCR tests complete for 8ce500e! |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 0b0b481: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @Capstan, @malhotrasagar2212 VCR tests complete for 0b0b481! |
|
@malhotrasagar2212 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
malhotrasagar2212
left a comment
There was a problem hiding this comment.
Hi @Capstan, Thanks for the PR.
Could you please take a look at the failing VCR tests and missing test report.
4f38528 to
94c74a9
Compare
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 4f38528: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 4 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @Capstan, @malhotrasagar2212 VCR tests complete for 4f38528! |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 94c74a9: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 4 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @Capstan, @malhotrasagar2212 VCR tests complete for 94c74a9! |
…failure When performance_monitoring_unit is unset in HCL configuration, the Compute Engine API defaults it to 'STANDARD' in remote responses. During VCR replay against older cassettes (where the API returned empty string), acceptance tests fail due to state mismatch. This commit adds a DiffSuppressFunc for performance_monitoring_unit (suppressing diffs between empty string and 'STANDARD') across Compute Instance, Instance Template, Region Instance Template, and Container Node Config to resolve replay mismatches and restore CI stability.
94c74a9 to
197391f
Compare
|
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 197391f: Diff reportYour PR generated the following diffs in downstream repositories:
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
Resource: resource "google_container_cluster" "primary" {
node_pool {
node_config {
advanced_machine_features {
performance_monitoring_unit = # value needed
}
}
}
}
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @Capstan, @malhotrasagar2212 VCR tests complete for 197391f! |
|
@malhotrasagar2212 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
malhotrasagar2212
left a comment
There was a problem hiding this comment.
The failing tests and missing test report are not due to the added PR changes. LGTM, Thanks
cd6fb93
This PR resolves the
TestAccComputeInstance_performanceMonitoringUnitVCR test failure by adding anEmptyOrDefaultStringSuppress("STANDARD")diff suppress function to theperformance_monitoring_unitfield inadvanced_machine_features.The Compute Engine API recently began returning
"STANDARD"as the default value for this field even when it is not explicitly configured, which caused anImportStateVerifydiff mismatch in Terraform.Fixes hashicorp/terraform-provider-google#24761
Release Note Template for Downstream PRs (will be copied)