datasource add/delete not effected until next sync
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
congress |
Fix Released
|
High
|
Masahito Muroi |
Bug Description
If the API is deployed on a separate node from the datasources:
When the API node processes datasource add/delete, it modifies the database and returns success, even though the datasource service has not been created or removed. We give a strange user experience that after adding a datasource returns success, the newly added datasource does not exist or have status until the next periodic sync (default 30 seconds?).
Proposed fix:
add a new datasource_manager service that is automatically started on the dse_node that hosts the datasource services.
On the datasource_model api, instead of calling self.bus.
Consider backporting fix to Newton.
Changed in congress: | |
status: | New → Confirmed |
assignee: | nobody → Masahito Muroi (muroi-masahito) |
Fix proposed to branch: master /review. openstack. org/397096
Review: https:/