-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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: rust-postgres failed [scheduled backups fail] #96799
Comments
roachtest.rust-postgres failed with artifacts on master @ 09188370d82e163ff1d44c62fe611104502c548d:
Parameters: |
roachtest.rust-postgres failed with artifacts on master @ e51ffa013c81212870891001f0328912550fa75d:
Parameters: |
cc @msbutler something seems off with the scheduled backups here, but i can't tell why this test is affected. |
cc @cockroachdb/disaster-recovery |
I think I know where the problem is. When the single node initially starts up, it successfully creates a backup schedule, but when it's restarted with a new port for the rust orm, the schedule backup cmd fails. I confirmed the new port seems to be the problem by commenting this line out and rerunning the test a few times, and the 2nd schedule backup cmd invoction works fine. roachprod is naive to this port change, as the cockroach port is hardcoded at cluster creation, via setting this field: I suspect that any sql cmd executed via roachprod's sql interface will fail after this port change. I think the easiest fix here is to replace I'm unsure why i didn't catch this in my roachtest nightly run. |
Turning off backups for this test sgtm! Thanks for looking at this. |
96881: servercontroller: serve http from default tenant on error r=aadityasondhi a=dhartunian Previously, when an HTTP request arrived with a tenant cookie attached, we would attempt to connect to that tenant and fail if the tenant couldn't be started or if it didn't exist. This causes a bad user-facing experience when someone's browser contains stale tenant cookies and they attempt to load DB Console. The error returns a 500 to the browser and user sees no UI, can't try and login again, and is basically stuck until they clear their cookies. This change falls back to serving HTTP from the default tenant when the requested one can't be reached. This ensures that *something* is served to ensure that unauthenticated endpoints can still be loaded in these scenarios and users can attempt to login again. Epic: CRDB-12100 Release note: None 96947: kvserver: fix rebalance obj test on arm mac r=pavelkalinnikov a=kvoli Previosly,`TestRebalanceObjectiveManager` and `TestLoadBasedRebalancingObjective` would assert assuming that it was possible for the test host to use `grunning`, however this is not true for ARM Mac. This patch ammends these tests to test a subset of behavior when `grunning` isn't supported and then exit. Fixes: #96934 Release note: None 96957: sql: fix SHOW GRANTS FOR public r=ecwall a=rafiss fixes #96948 Release note (bug fix): Fixed the `SHOW GRANTS FOR public` command so it works correctly. Previously, this would return an error saying that the `public` role does not exist. 96964: roachtest: set range tombstones flag accordingly r=jbowens,msbutler a=nicktrav Fix a bug in the `import-cancellation` roachtest whereby range tombstones are always disabled. Release note: None. Epic: CRDB-20465 96985: roachtest: disable scheduled backup in rust-postgres node restart r=rafiss a=msbutler Fixes #96799 Release note: None Co-authored-by: David Hartunian <[email protected]> Co-authored-by: Austen McClernon <[email protected]> Co-authored-by: Rafi Shamim <[email protected]> Co-authored-by: Nick Travers <[email protected]> Co-authored-by: Michael Butler <[email protected]>
roachtest.rust-postgres failed with artifacts on master @ ff67a4ba86d710db090ce700f229020365851183:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=16
,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!
Jira issue: CRDB-24340
The text was updated successfully, but these errors were encountered: