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

ccl/backupccl: TestBackupRestoreSystemUsers failed #123931

Closed
cockroach-teamcity opened this issue May 10, 2024 · 2 comments
Closed

ccl/backupccl: TestBackupRestoreSystemUsers failed #123931

cockroach-teamcity opened this issue May 10, 2024 · 2 comments
Assignees
Labels
branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-1 Issues/test failures with a fix SLA of 1 month T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 10, 2024

ccl/backupccl.TestBackupRestoreSystemUsers failed on release-24.1 @ 7c483c276934758d4bf736b40594d4541377d526:

=== RUN   TestBackupRestoreSystemUsers
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestBackupRestoreSystemUsers2190553932
    test_log_scope.go:81: use -show-logs to present logs inline
    test_server_shim.go:157: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
    test_server_shim.go:157: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
    test_server_shim.go:157: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
    test_server_shim.go:157: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
    testutils.go:290: no Invalid Descriptors
    testutils.go:290: no Invalid Descriptors
    testutils.go:290: no Invalid Descriptors
    testutils.go:290: no Invalid Descriptors
    backup_test.go:10077: -- test log scope end --
test logs left over in: outputs.zip/logTestBackupRestoreSystemUsers2190553932
--- FAIL: TestBackupRestoreSystemUsers (144.95s)
=== RUN   TestBackupRestoreSystemUsers/restore-from-backup-with-existing-user
    backup_test.go:10058: query 'SELECT * FROM system.users': expected:
        admin, , true, 2
        app, NULL, false, 101
        app_role, NULL, true, 102
        root, , false, 1
        test, NULL, false, 103
        test_role, NULL, true, 104
        testuser, NULL, false, 100
        
        got:
        admin, , true, 2
        app, NULL, false, 103
        app_role, NULL, true, 104
        root, , false, 1
        test, NULL, false, 105
        test_role, NULL, true, 106
        testuser, NULL, false, 102
        
    --- FAIL: TestBackupRestoreSystemUsers/restore-from-backup-with-existing-user (30.25s)

Parameters:

  • attempt=1
  • race=true
  • run=1
  • shard=23
Help

See also: How To Investigate a Go Test Failure (internal)

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-38608

@cockroach-teamcity cockroach-teamcity added branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-test-failure Broken test (automatically or manually discovered). 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-disaster-recovery labels May 10, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone May 10, 2024
@msbutler
Copy link
Collaborator

well this certainly assumed some hard corded id's. removing release blocker.

@msbutler msbutler added P-1 Issues/test failures with a fix SLA of 1 month and removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels May 10, 2024
@msbutler
Copy link
Collaborator

fixed by #124063

Disaster Recovery Backlog automation moved this from Backlog to Done May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-1 Issues/test failures with a fix SLA of 1 month T-disaster-recovery
Development

No branches or pull requests

2 participants