[mig] Error when configuring the database

RESOLVED FIXED

Status

Enterprise Information Security
MIG
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: netantho, Unassigned)

Tracking

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140917194002

Steps to reproduce:

Step 15 : RUN service postgresql start && sh /go/src/github.com/mozilla/mig/doc/.files/createdb.sh



Actual results:

 ---> Running in 051d6c76d10b
Starting PostgreSQL 9.4 database server: main.
Created user migadmin with password '_uBpOx0Uf4J8yWEV6OyGcc1YYRX9W-MD'
Created user migapi with password 'e98C0yE6PjfkhdL7YEJLFuxGN8oKOJH6'
Created user migscheduler with password 'D-J_zr77VPZEHdyKbDpPBGKMN0tJZZeF'
psql:/tmp/tmp.PnuQ4vO6nq:124: ERROR:  foreign key constraint "invagtmodperm_investigatorid_fkey" cannot be implemented
DETAIL:  Key columns "investigatorid" and "id" are of incompatible types: numeric and bigint.
psql:/tmp/tmp.PnuQ4vO6nq:133: ERROR:  foreign key constraint "signatures_investigatorid_fkey" cannot be implemented
DETAIL:  Key columns "investigatorid" and "id" are of incompatible types: numeric and bigint.


Expected results:

invagtmodperm_investigatorid_fkey and signatures_investigatorid_fkey foreign keys should have been implemented
(Reporter)

Comment 1

3 years ago
Tested on Debian GNU/Linux testing
Nice! This very problem was fixed earlier today in https://github.com/mozilla/mig/commit/3faab0396801d4296538b2d24effe097f0b71eb8
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED

Updated

3 years ago
Blocks: 896480

Updated

3 years ago
Blocks: 1107108

Updated

3 years ago
No longer blocks: 1107108

Updated

3 years ago
Component: Operations Security (OpSec): General → Operations Security (OpSec): MIG
(Assignee)

Updated

2 years ago
Component: Operations Security (OpSec): MIG → MIG
Product: mozilla.org → Enterprise Information Security
You need to log in before you can comment on or make changes to this bug.