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

roachtest: multitenant-upgrade failed #94748

Closed
cockroach-teamcity opened this issue Jan 5, 2023 · 5 comments · Fixed by #94947
Closed

roachtest: multitenant-upgrade failed #94748

cockroach-teamcity opened this issue Jan 5, 2023 · 5 comments · Fixed by #94947
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-multitenant Issues owned by the multi-tenant virtual team
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jan 5, 2023

roachtest.multitenant-upgrade failed with artifacts on master @ d1233022fc2f67a3901c0be08ec71abb13b1e8fe:

test artifacts and logs in: /artifacts/multitenant-upgrade/run_1
(sql_runner.go:154).ExpectErr: expected error 'pq: preventing tenant upgrade from running as the host cluster has not yet been upgraded: host cluster version = 22.2, tenant cluster version = 22.2', got: pq: preventing tenant upgrade from running as the storage cluster has not yet been upgraded: storage cluster version = 22.2, tenant cluster version = 22.2
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

/cc @cockroachdb/multi-tenant

This test on roachdash | Improve this report!

Jira issue: CRDB-23118

Epic CRDB-27931

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-multitenant Issues owned by the multi-tenant virtual team labels Jan 5, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Jan 5, 2023
@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant-upgrade failed with artifacts on master @ 642afd6e8c8d1f967da4aa0c3c08e2bdc0495100:

test artifacts and logs in: /artifacts/multitenant-upgrade/run_1
(sql_runner.go:154).ExpectErr: expected error 'pq: preventing tenant upgrade from running as the host cluster has not yet been upgraded: host cluster version = 22.2, tenant cluster version = 22.2', got: pq: preventing tenant upgrade from running as the storage cluster has not yet been upgraded: storage cluster version = 22.2, tenant cluster version = 22.2
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant-upgrade failed with artifacts on master @ 7594fb2d1438dd5ed8f80a887b8d60b6cdd296ed:

test artifacts and logs in: /artifacts/multitenant-upgrade/run_1
(sql_runner.go:154).ExpectErr: expected error 'pq: preventing tenant upgrade from running as the host cluster has not yet been upgraded: host cluster version = 22.2, tenant cluster version = 22.2', got: pq: preventing tenant upgrade from running as the storage cluster has not yet been upgraded: storage cluster version = 22.2, tenant cluster version = 22.2
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant-upgrade failed with artifacts on master @ 9b567e3439e49c109e5204c9d0afec49c1a3169b:

test artifacts and logs in: /artifacts/multitenant-upgrade/run_1
(sql_runner.go:154).ExpectErr: expected error 'pq: preventing tenant upgrade from running as the host cluster has not yet been upgraded: host cluster version = 22.2, tenant cluster version = 22.2', got: pq: preventing tenant upgrade from running as the storage cluster has not yet been upgraded: storage cluster version = 22.2, tenant cluster version = 22.2
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant-upgrade failed with artifacts on master @ 27ebfa830ac7122fc3b286136158fef615b20b8f:

test artifacts and logs in: /artifacts/multitenant-upgrade/run_1
(sql_runner.go:154).ExpectErr: expected error 'pq: preventing tenant upgrade from running as the host cluster has not yet been upgraded: host cluster version = 22.2, tenant cluster version = 22.2', got: pq: preventing tenant upgrade from running as the storage cluster has not yet been upgraded: storage cluster version = 22.2, tenant cluster version = 22.2
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant-upgrade failed with artifacts on master @ b5cffc06bf36ce42b601d3307a1e38f933be40c4:

test artifacts and logs in: /artifacts/multitenant-upgrade/run_1
(sql_runner.go:154).ExpectErr: expected error 'pq: preventing tenant upgrade from running as the host cluster has not yet been upgraded: host cluster version = 22.2, tenant cluster version = 22.2', got: pq: preventing tenant upgrade from running as the storage cluster has not yet been upgraded: storage cluster version = 22.2, tenant cluster version = 22.2
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled
(cluster.go:1933).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

craig bot pushed a commit that referenced this issue Jan 11, 2023
94947: roachtest: fix multitenant-upgrade expected error r=healthy-pod a=healthy-pod

In #94669, we changed usages of `host cluster` to
`storage cluster` because `host cluster` is specific to `CC Serverless`.

This change updates the expected
error in `multitenant-upgrade` and some other usages of `host cluster`.

Epic: none
Release note: None

Closes #94748

Co-authored-by: healthy-pod <[email protected]>
@craig craig bot closed this as completed in cb89b66 Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-multitenant Issues owned by the multi-tenant virtual team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants