You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This Bug Report affects these Traffic Control components:
Traffic Ops
Current behavior:
This issue is similar to #4984 . When running postinstall twice when using the Postgres backend for Traffic Vault, the load_schema operation for Traffic Vault causes an error. The command db/admin --trafficvault -env=production load_schema is executed by the postinstall. The error is as follows:
ALTER TABLE ONLY dnssec
ADD CONSTRAINT dnssec_pkey PRIMARY KEY (cdn);
ERROR: multiple primary keys for table "dnssec" are not allowed
Can't create database tables
Expected behavior:
As per #4984, running postinstall twice should be possible without errors.
Steps to reproduce:
Run Postinstall with postgres being used for the Traffic Vault backend.
Run Postinstall again with the same input
This Bug Report affects these Traffic Control components:
Current behavior:
This issue is similar to #4984 . When running postinstall twice when using the Postgres backend for Traffic Vault, the load_schema operation for Traffic Vault causes an error. The command db/admin --trafficvault -env=production load_schema is executed by the postinstall. The error is as follows:
Expected behavior:
As per #4984, running postinstall twice should be possible without errors.
Steps to reproduce:
Run Postinstall with postgres being used for the Traffic Vault backend.
Run Postinstall again with the same input