Scale-in with deletion-policy and the criteria is OLDEST_FIRST failed
Bug #1614450 reported by
RUIJIE YUAN
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
senlin |
Fix Released
|
High
|
RUIJIE YUAN |
Bug Description
What I have done is:
1. Create a cluster and the desired capacity is 0
2. Bind a deletion-policy to the cluster -- the criteria is OLDEST_FIRST
3. Do CLUSTER_RESIZE action to scale-out to 5 nodes -- one failed
4. Do CLUSTER_RECOVER to recover the cluster
Then I got an exception which is None type cannot compare to datetime.datetime in ScaleUtil.py
How to produce the situation again:
Create a node and then turn the senlin-engine off, the status of the action will be FAILED, and the create_at will
be None
Changed in senlin: | |
assignee: | nobody → RUIJIE YUAN (cnjie0616) |
Changed in senlin: | |
status: | New → Confirmed |
Changed in senlin: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
milestone: | none → newton-rc1 |
Changed in senlin: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Hi, Ruijie, thanks a lot for reporting the bug. We met similar issue before and the following is the corresponding bug report:
https:/ /bugs.launchpad .net/senlin/ +bug/1594352
But we haven't found a good way to fix this issue...