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

e2e: nightly test suite currently failing due to infra build problem #11950

Closed
jrasell opened this issue Jan 27, 2022 · 2 comments · Fixed by #11968
Closed

e2e: nightly test suite currently failing due to infra build problem #11950

jrasell opened this issue Jan 27, 2022 · 2 comments · Fixed by #11968
Assignees
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/e2e type/bug

Comments

@jrasell
Copy link
Member

jrasell commented Jan 27, 2022

The infra build is currently failing:

null_resource.bootstrap_vault (local-exec): Error initializing: Put "https://<ADDR>:8200/v1/sys/init": dial tcp <ADDR>:8200: connect: connection refused
null_resource.bootstrap_nomad_acls (local-exec): Error bootstrapping: Put "https://<ADDR>:4646/v1/acl/bootstrap": dial tcp <ADDR>:4646: connect: connection refused
null_resource.bootstrap_vault (local-exec): Error initializing: Put "https://<ADDR>:8200/v1/sys/init": dial tcp <ADDR>:8200: connect: connection refused
@jrasell jrasell added type/bug stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/e2e labels Jan 27, 2022
@jrasell jrasell added this to Needs Triage in Nomad - Community Issues Triage via automation Jan 27, 2022
@jrasell jrasell moved this from Needs Triage to Needs Roadmapping in Nomad - Community Issues Triage Jan 27, 2022
@jrasell
Copy link
Member Author

jrasell commented Feb 1, 2022

The infra build out problem has now been fixed, which has uncovered failures in the test suites. These all seem to be related to stopping a job:

Failed
=== RUN   TestE2E/Namespaces/*namespaces.NamespacesE2ETest/TestNamespacesFiltering
    namespaces.go:183: 
        	Error Trace:	namespaces.go:183
        	Error:      	Received unexpected error:
        	            	command nomad [job stop -namespace NamespaceA test-namespace-ac40f329] failed: exit status 1
        	            	Output: ==> 2022-02-01T05:36:20Z: Monitoring evaluation "2043867f"
        	            	    2022-02-01T05:36:20Z: Evaluation triggered by job "test-namespace-ac40f329"
        	            	==> 2022-02-01T05:36:21Z: Monitoring evaluation "2043867f"
        	            	    2022-02-01T05:36:21Z: Evaluation within deployment: "959243a3"
        	            	    2022-02-01T05:36:21Z: Evaluation status changed: "pending" -> "complete"
        	            	==> 2022-02-01T05:36:21Z: Evaluation "2043867f" finished with status "complete"
        	            	==> 2022-02-01T05:36:21Z: Monitoring deployment "959243a3"
        	            	    
        	            	2022-02-01T05:36:21Z
        	            	ID          = 959243a3
        	            	Job ID      = test-namespace-ac40f329
        	            	Job Version = 0
        	            	Status      = cancelled
        	            	Description = Cancelled because job is stopped
        	            	
        	            	Deployed
        	            	Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
        	            	group       1        1       0        0          2022-02-01T05:46:17Z
        	Test:       	TestE2E/Namespaces/*namespaces.NamespacesE2ETest/TestNamespacesFiltering
        	Messages:   	could not stop job in namespace

Some investigation has found that #11550 changed the way in which deployment monitoring reports to the CLI, particularly when running job stop. When stopping a job, the deployment becomes cancelled because the job is stopped, and therefore exits with code 1 on the CLI. This will be discussed internally so we can come up with the correct solution.

@jrasell jrasell self-assigned this Feb 1, 2022
@jrasell jrasell moved this from Needs Roadmapping to In Progress in Nomad - Community Issues Triage Feb 1, 2022
Nomad - Community Issues Triage automation moved this from In Progress to Done Feb 1, 2022
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 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 Oct 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/e2e type/bug
Projects
Development

Successfully merging a pull request may close this issue.

1 participant