Should store the actual UUID of obj_id in senlin database in webhook create
Bug #1521049 reported by
junxu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
senlin |
Fix Released
|
High
|
junxu |
Bug Description
1. create a cluster with name "test_cluster", senlin cluster-create -p profile1 -n 2 -m 4 -c 2 test_cluster
2. senlin wenhook-create -c test_cluster -a CLUSTER_SCALING_OUT webhook1
3. create second cluster with same name as first cluster
4. delete first cluster
5. trigger webhook, then the scale_out is on second cluster
Changed in senlin: | |
status: | New → Confirmed |
Changed in senlin: | |
status: | Fix Committed → Fix Released |
importance: | Undecided → High |
assignee: | nobody → junxu (xujun-1) |
milestone: | none → mitaka-2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/251187 /git.openstack. org/cgit/ openstack/ senlin/ commit/ ?id=4e5d76e5c9d f29fe5371a31211 4ac40bbc2b2e39
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4e5d76e5c9df29f e5371a312114ac4 0bbc2b2e39
Author: Jun, Xu <email address hidden>
Date: Mon Nov 30 04:29:37 2015 +0000
Store the actual UUID of obj_id in Senlin database for webhook create
In 'webhook' DB table, it has a field named 'obj_id' to reference a
target which the webhook will act on. Now if we create a webhook
with target name, then it will store the target name in the 'obj_id'
field of 'webhook' table. Triggering this webhook maybe lead to
unexpected result. An example is as following.
1. Create the first cluster named 'cluster1'
2. Create webhook on 'cluster1' with CLUSTER_SCALE_OUT action
3. Delete the cluster1
4. Create a second cluster also names 'cluster1'
5. Trigger the webhook which will result in scaling out the
second cluster.
Change-Id: Idf2d27d7f16535 a52fbf6c59f1c99 7e4e0728c89
Closes-Bug: #1521049