ovb-3ctlr_1comp_1supp-featureset039 failing overcloud deploy "Failed to connect to NOVA_API database "
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Martin Schuppert |
Bug Description
in periodic-
2019-05-16 11:43:54 | "stdout: Failed to connect to NOVA_API database",
2019-05-16 11:43:54 | "ERROR 1045 (28000): Access denied for user 'nova_api'
2019-05-16 11:43:54 | "Failed to connect to PLACEMENT database",
2019-05-16 11:43:54 | "ERROR 1045 (28000): Access denied for user 'placement'
2019-05-16 11:43:54 | "Unable to proceed without connection to nova database",
NOTE: AFAICS this does not block promotions since we don't have it in criteria [3] it is already commented out
[1] https:/
[2] http://
[3] https:/
Changed in tripleo: | |
assignee: | nobody → Martin Schuppert (mschuppert) |
Changed in tripleo: | |
milestone: | none → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
the issue us that in tls-everywhere scenario we don't have a mysql.cnf, which has a [client] section which tells the mysql client triggered in /usr/share/ placement/ mysql-migrate- db.sh [1] to use ssl.
After initial discussion, seems we should add a [client] section to either triplo.cnf or another mysql config file to let the client know ssl needs to be used.
[1] https:/ /github. com/openstack/ tripleo- heat-templates/ blob/master/ deployment/ placement/ placement- api-container- puppet. yaml#L247