-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Watcher: Mysterious rolling upgrade failure #33185
Copy link
Copy link
Closed
Labels
Description
This rolling upgrade build failed fairly mysteriously. This is what the failure looks like:
15:24:46 1> [2018-08-26T15:24:37,459][INFO ][o.e.u.UpgradeClusterClientYamlTestSuiteIT] [test] Stash dump on test failure [{
15:24:46 1> "stash" : {
15:24:46 1> "record_id" : "my_watch_0be15ae1-d0c1-4516-b2fc-7291a51c00a6-2018-08-26T15:24:37.281Z",
15:24:46 1> "body" : {
15:24:46 1> "_id" : "my_watch_0be15ae1-d0c1-4516-b2fc-7291a51c00a6-2018-08-26T15:24:37.281Z",
15:24:46 1> "watch_record" : {
15:24:46 1> "watch_id" : "my_watch",
15:24:46 1> "node" : "j6O-Ii5MRcuZismjV2mJPA",
15:24:46 1> "state" : "failed",
15:24:46 1> "user" : "test_user",
15:24:46 1> "status" : {
15:24:46 1> "state" : {
15:24:46 1> "active" : true,
15:24:46 1> "timestamp" : "2018-08-26T15:24:36.992Z"
15:24:46 1> },
15:24:46 1> "actions" : {
15:24:46 1> "logging" : {
15:24:46 1> "ack" : {
15:24:46 1> "timestamp" : "2018-08-26T15:24:36.992Z",
15:24:46 1> "state" : "awaits_successful_execution"
15:24:46 1> }
15:24:46 1> }
15:24:46 1> },
15:24:46 1> "execution_state" : "failed",
15:24:46 1> "version" : 1
15:24:46 1> },
15:24:46 1> "trigger_event" : {
15:24:46 1> "type" : "manual",
15:24:46 1> "triggered_time" : "2018-08-26T15:24:37.279Z",
15:24:46 1> "manual" : {
15:24:46 1> "schedule" : {
15:24:46 1> "scheduled_time" : "2018-08-26T15:24:37.279Z"
15:24:46 1> }
15:24:46 1> }
15:24:46 1> },
15:24:46 1> "input" : {
15:24:46 1> "simple" : { }
15:24:46 1> },
15:24:46 1> "condition" : {
15:24:46 1> "always" : { }
15:24:46 1> },
15:24:46 1> "result" : {
15:24:46 1> "execution_time" : "2018-08-26T15:24:37.281Z",
15:24:46 1> "execution_duration" : 1535297077283,
15:24:46 1> "actions" : [ ]
15:24:46 1> },
15:24:46 1> "exception" : {
15:24:46 1> "type" : "illegal_state_exception",
15:24:46 1> "reason" : "could not register execution [my_watch]. current executions are sealed and forbid registrations of additional executions."
15:24:46 1> }
15:24:46 1> }
15:24:46 1> }
15:24:46 1> }
15:24:46 1> }]
15:24:46 1> [2018-08-26T15:24:37,502][INFO ][o.e.u.UpgradeClusterClientYamlTestSuiteIT] [test] [p0=old_cluster/60_watcher/CRUD watch APIs] after test
15:24:46 FAILURE 0.96s | UpgradeClusterClientYamlTestSuiteIT.test {p0=old_cluster/60_watcher/CRUD watch APIs} <<< FAILURES!
15:24:46 > Throwable #1: java.lang.AssertionError: Failure at [old_cluster/60_watcher:43]: watch_record.state didn't match expected value:
15:24:46 > watch_record.state: expected [executed] but was [failed]
This is in the "old" cluster so the cluster state is empty, but we still get an error as though the watch was running.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Fields
Give feedbackNo fields configured for issues without a type.