Erik Olof Gunnar Andersson 1924abff40 Add unique constraint to service_statuses ... In the current implementation, if for any reason a duplicate service entry gets created, the call to update that service will fail endlessly, and instead cause the service to create new entries everytime update_service_status gets called. Causing it to fill the database with duplicate entries. This patch adds a unique constraint to the service_statuses table based on the service_name and hostname, to ensure that this cannot happen. In addition we add a new test to the storage driver and further expanded the central service test coverage. Change-Id: I307a8f7dd8b8a83effa447a846db3288efa32dba Closes-Bug: #1768824		2018-05-20 12:41:21 -07:00
..
notes	Add unique constraint to service_statuses	2018-05-20 12:41:21 -07:00
source	Imported Translations from Zanata	2018-03-11 07:07:58 +00:00