Fuel tries to continue deployment when nova-manage db sync failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Mitaka |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Newton |
Confirmed
|
Medium
|
Fuel Sustaining |
Bug Description
nova-{api,
The error message is (from /var/log/
2016-11-11 14:38:57.074 21442 ERROR oslo_service.
2016-11-11 14:38:57.074 21442 ERROR oslo_service.
2016-11-11 14:38:57.453 4895 INFO oslo_service.
root@node-1:~# apt-cache policy nova-api
nova-api:
Installed: 2:13.1.
Candidate: 2:13.1.
Version table:
*** 2:13.1.
1050 http://
100 /var/lib/
2:
1050 http://
1:
500 http://
1:
500 http://
1:
500 http://
Setting importance to Critical since this breaks the deployment (100% reproducible)
summary: |
- nova-{api,scheduler,cert,consoleauth} service fail to start due to a - wrong SQL request (or a wrong DB schema?) + Fuel tries to continue deployment when nova-manage db-sync failed |
Changed in fuel: | |
status: | New → Invalid |
Changed in fuel: | |
status: | Invalid → New |
Changed in fuel: | |
status: | New → Invalid |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 9.2 → 11.0 |
importance: | High → Medium |
mysql> describe services; ------- ----+-- ------- -----+- -----+- ----+-- ------- +------ ------- ---+ ------- ----+-- ------- -----+- -----+- ----+-- ------- +------ ------- ---+ ------- ----+-- ------- -----+- -----+- ----+-- ------- +------ ------- ---+
+------
| Field | Type | Null | Key | Default | Extra |
+------
| created_at | datetime | YES | | NULL | |
| updated_at | datetime | YES | | NULL | |
| deleted_at | datetime | YES | | NULL | |
| id | int(11) | NO | PRI | NULL | auto_increment |
| host | varchar(255) | YES | MUL | NULL | |
| binary | varchar(255) | YES | | NULL | |
| topic | varchar(255) | YES | | NULL | |
| report_count | int(11) | NO | | NULL | |
| disabled | tinyint(1) | YES | | NULL | |
| deleted | int(11) | YES | | NULL | |
| disabled_reason | varchar(255) | YES | | NULL | |
+------
11 rows in set (0.00 sec)
There are no `last_seen_up' field in the `services' database.