SM mitaka HA R3.1 build 25 provision gets stuck at config_started due to keystone conflict among Openstack nodes
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Fix Committed
|
Critical
|
Dheeraj Gautam | |||
Trunk |
Fix Committed
|
Critical
|
Dheeraj Gautam |
Bug Description
SM mitaka HA R3.1 build 25 provision gets stuck at config_started due to keystone conflict among Openstack nodes
setup
SM : nodej8
Targets : nodeg21,
root@nodej8:~# server-manager show server --select id,roles,
{
"server": [
{
"id": "nodeg21",
]
},
{
"id": "nodec38",
]
},
{
"id": "nodeg17",
]
},
{
"id": "nodec58",
]
},
{
"id": "nodeg33",
]
}
]
}
root@nodej8:~#
cfgm0 node nodeg21 syslog
Aug 14 11:20:29 nodeg21 puppet-
Aug 14 11:20:29 nodeg21 puppet-
Aug 14 11:22:16 nodeg21 kernel: [ 1835.798551] init: supervisor-config main process (6341) killed by TERM signal
Aug 14 11:22:28 nodeg21 puppet-
Aug 14 11:22:28 nodeg21 puppet-
Issue is due to the parameter default_domain_id /etc/keystone/
WorkAround :
1) grep default_domain_id /etc/keystone/
2) make sure all the openstack nodes have same default_domain_id ;
3) Restart the keystone service on all the openstack nodes
3) observe that the provision gets completed succesfully
Review in progress for https:/ /review. opencontrail. org/23294
Submitter: Dheeraj Gautam (<email address hidden>)