Undeletable stack due to DB event integrity error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Crag Wolfe |
Bug Description
I'm seeing this error:
-AllNodesDeploy
I did create a stack then update to a newer version, but the db_sync is up to date AFAICT:
(undercloud) [stack@undercloud ~]$ sudo heat-manage db_version
2017-04-11 10:33:03.066 7587 WARNING oslo_config.cfg [-] Option "db_backend" from group "DEFAULT" is deprecated. Use option "backend" from group "database".
80
(undercloud) [stack@undercloud ~]$ sudo heat-manage db_sync
2017-04-11 10:33:10.496 7595 WARNING oslo_config.cfg [-] Option "db_backend" from group "DEFAULT" is deprecated. Use option "backend" from group "database".
(undercloud) [stack@undercloud ~]$ sudo heat-manage db_version
2017-04-11 10:33:12.960 7607 WARNING oslo_config.cfg [-] Option "db_backend" from group "DEFAULT" is deprecated. Use option "backend" from group "database".
80
I don't see any recent related migrations or changes to the DB model, but I wanted to raise this to see if other folks are seeing similar. I don't yet have a minimal reproducer.
Changed in heat: | |
milestone: | none → pike-2 |
importance: | Undecided → Medium |
Hmm, so it seems that sudo heat-manage migrate_ properties_ data resolves this, so perhaps I missed some recent change - I don't see a pike release note saying that's mandatory?