Skip to content
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

Failing test(s): TestAccComposer1Environment_withNodeConfig #14375

Comments

@SarahFrench
Copy link
Member

SarahFrench commented Apr 20, 2023

Failure rates

  • 42% since test added on 13th April 2023 (3/7 runs)

Impacted tests

  • TestAccComposer1Environment_withNodeConfig

Affected Resource(s)

  • google_composer_environment

Nightly build test history

Message(s)

vcr_utils.go:144: Step 1/3 error: Error running apply: exit status 1
Error: Error waiting to create Environment: Error waiting for Creating Environment: Error code 9, message: Failed to create environment, but no error was surfaced. This can be caused by a lack of proper permissions. Check if this environment's service account tf-test-517893798866630840@[PROJECT_ID].iam.gserviceaccount.com has the 'roles/composer.worker' role and there is no firewall inhibiting internal communications set. In case, it is a Compute default service account it should have Editor permissions. For the required permissions information, please, refer to https://cloud.google.com/composer/docs/how-to/access-control  https://cloud.google.com/composer/docs/troubleshooting-environment-creation page contains more troubleshooting instructions
Couldn't bring up ['airflow-worker'] in time.
Essential objects couldn't be created: ['airflow-worker']
with google_composer_environment.test,
on terraform_plugin_test.tf line 4, in resource "google_composer_environment" "test":
4: resource "google_composer_environment" "test" {
--- FAIL: TestAccComposer1Environment_withNodeConfig (2744.88s)
FAIL

The permission the error mentioned is in place, but maybe could benefit from an explicit dependency set via depends_on

------- Stdout: -------
=== RUN   TestAccComposer1Environment_withNodeConfig
=== PAUSE TestAccComposer1Environment_withNodeConfig
=== CONT  TestAccComposer1Environment_withNodeConfig
    vcr_utils.go:152: Step 1/3 error: Error running apply: exit status 1
        Error: Error waiting to create Environment: Error waiting for Creating Environment: Error code 9, message: Some of the GKE pods failed to become healthy. Please check the GKE logs for details, and retry the operation.
          with google_composer_environment.test,
          on terraform_plugin_test.tf line 4, in resource "google_composer_environment" "test":
           4: resource "google_composer_environment" "test" {
--- FAIL: TestAccComposer1Environment_withNodeConfig (2779.82s)
FAIL

b/299600609

@rileykarson rileykarson added this to the Goals milestone Apr 24, 2023
@github-actions github-actions bot added service/composer forward/review In review; remove label to forward labels Aug 17, 2023
@melinath melinath removed the forward/review In review; remove label to forward label Sep 7, 2023
@melinath
Copy link
Collaborator

melinath commented Oct 6, 2023

New failure message:

Error: Error waiting to create Environment: Error waiting for Creating Environment: Error code 9, message: Some of the GKE pods failed to become healthy. Please check the GKE logs for details, and retry the operation.

@PeWu
Copy link
Contributor

PeWu commented Oct 10, 2023

These are flaky tests. This issue can be closed.

@melinath
Copy link
Collaborator

The idea would be to fix the flakiness - leaving open.

@SarahFrench
Copy link
Member Author

I've added another error seen for this test to the issue description - Error code 9, message: Some of the GKE pods failed to become healthy. Please check the GKE logs for details, and retry the operation..

I don't have access to the test environment but it'd be interesting if someone could look at those logs.

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.