roachtest: backup-restore/round-trip failed [schemachange foreign key violation]

[cockroach-teamcity]

roachtest.backup-restore/round-trip failed with artifacts on master @ a36097be277adef635f55d317579ca79b450bfef:

(monitor.go:153).Wait: monitor failure: full command output in run_070617.273464343_n4_COCKROACHRANDOMSEED5.log: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/backup-restore/round-trip/run_1

Parameters:

• ROACHTEST_arch=amd64
• ROACHTEST_cloud=gce
• ROACHTEST_coverageBuild=false
• ROACHTEST_cpu=4
• ROACHTEST_encrypted=true
• ROACHTEST_metamorphicBuild=false
• ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-36172

[stevendanna]

The schemachange workload itself failed:

  |   | Error: ***UNEXPECTED ERROR; Received an unexpected execution error.: ERROR: insert on table "table_w2_351" violates foreign key constraint "table_w2_351_col3�51_w2_366_table_w2_351_col351_w2_352_fk" (SQLSTATE 23503)

My suspicion is that this is a small bug in how inserts are generated in the schemachange workload and doesn't represent a real problem. I'm removing release-blocker, marking as P-3, and tagging T-sql-foundations in case they want to take a look.

Full log from the workload here:

https://teamcity.cockroachdb.com/repository/download/Cockroach_Nightlies_RoachtestNightlyGceBazel/14071859:id/backup-restore/round-trip/run_1/artifacts.zip!/run_070617.273464343_n4_COCKROACHRANDOMSEED5.log

[fqazi]

@annrpom This is related to the workload failing into insert rows because of a FK violation

[rafiss]

foreign keys are being disabled in #120575 until they are fixed in the schemachange workload. keeping #119288 open as the tracking issue for the problem.