instance should to be set to RESTART_REQUIRED status absolutely when we unassgin configuration from it

Bug #1471312 reported by octopuszhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Expired
Undecided
Unassigned

Bug Description

When we detach a configuration from an instance, the overrides.cnf gets deleted and the instance is set to RESTART_REQUIRED status before (which is by design).

But since change https://review.openstack.org/#/c/162354/ ,

we don’t allways delete overrides.cnf, we use update_overrides method to manage overrides.cnf. If the overrides.cnf contains any configurations that needs restart , the instance will be set RESTART_REQUIRED in update_overrides methods. So we should not set it to RESTART_REQUIRED status everytime we unassign a configration absolutely.

Changed in trove:
assignee: nobody → octopuszhang (1004988384-n)
summary: - instance should to be set to RESTART_REQUIRED status absolutely assign
- we unassgin configuration from it
+ instance should to be set to RESTART_REQUIRED status absolutely when we
+ unassgin configuration from it
Amrith Kumar (amrith)
Changed in trove:
assignee: octopuszhang (1004988384-n) → nobody
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack DBaaS (Trove) because there has been no activity for 60 days.]

Changed in trove:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.