migration 30 -> 31 (031_stack_lock) fails
Bug #1261605 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld |
Bug Description
2013-12-17 02:51:05.951 1911 INFO migrate.
2013-12-17 02:51:06.313 1911 INFO migrate.
2013-12-17 02:51:06.313 1911 INFO migrate.
2013-12-17 02:51:06.498 1911 INFO migrate.
2013-12-17 02:51:06.498 1911 INFO migrate.
ERROR: (OperationalError) (1005, "Can't create table 'heat.stack_lock' (errno: 150)") '\nCREATE TABLE stack_lock (\n\tstack_id VARCHAR(36) NOT NULL, \n\tcreated_at DATETIME, \n\tupdated_at DATETIME, \n\tengine_id VARCHAR(36), \n\tPRIMARY KEY (stack_id), \n\tFOREIGN KEY(stack_id) REFERENCES stack (id)\n)
Changed in heat: | |
status: | New → Triaged |
milestone: | none → icehouse-2 |
importance: | Undecided → Critical |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
CREATE TABLE stack_lock (
stack_id VARCHAR(36) NOT NULL,
created_at DATETIME,
updated_at DATETIME,
engine_id VARCHAR(36),
PRIMARY KEY (stack_id),
FOREIGN KEY(stack_id) REFERENCES stack (id)
)ENGINE=InnoDB CHARSET=utf8