Can not distinguish private workflow and public workflow with the same name

Bug #1518276 reported by Lingxian Kong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-mistralclient
Fix Released
Medium
Lingxian Kong

Bug Description

steps to reproduce:
1. user1 create a private workflow with name='simple_wf'
2. user2 create a public workflow with name='simple_wf'
3. user1 get all the workflows, there are 2 workflows with the same name, users can not distinguish one from the other.

root@mistral:/vagrant/mistral# mistral workflow-list
+---------------------+--------+------------------------------+---------------------+------------+
| Name | Tags | Input | Created at | Updated at |
+---------------------+--------+------------------------------+---------------------+------------+
| std.create_instance | <none> | name, image_id, flavor_id... | 2015-11-20 03:33:04 | None |
| std.delete_instance | <none> | instance_id | 2015-11-20 03:33:04 | None |
| simple_wf | <none> | | 2015-11-20 03:34:34 | None |
| simple_wf | <none> | | 2015-11-20 03:35:16 | None |
+---------------------+--------+------------------------------+---------------------+------------+

Lingxian Kong (kong)
Changed in python-mistralclient:
assignee: nobody → Lingxian Kong (kong)
Revision history for this message
Lingxian Kong (kong) wrote :
Changed in python-mistralclient:
status: New → In Progress
Revision history for this message
Moshe Elisha (melisha) wrote :

Hi,

Can a user use the workflow ID for operating on the workflow or for creating an execution?
Does exposing the workflow ID helps the user in something beside distinguishing the WFs?

Revision history for this message
Lingxian Kong (kong) wrote :

Hi, Moshe,

Under current design, users can't do anything with workflow ID, except for recognizing different workflows with the same name.

However, what I want to acheieve in Mitaka cycle is, use resource ID in ReST API and use it as the only identifier in Mistral rather than resouce name. I proposed a blueprint here[1] to do that.

[1]: https://blueprints.launchpad.net/mistral/+spec/use-workflow-id-in-rest-api

Changed in python-mistralclient:
milestone: none → 1.2.0
status: In Progress → Fix Committed
importance: Undecided → Medium
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/python-mistralclient 1.2.0

This issue was fixed in the openstack/python-mistralclient 1.2.0 release.

Revision history for this message
Anastasia Kuznetsova (akuznetsova) wrote :

According to previous comment, fix for this bug was included to 1.2.0 release.

Changed in python-mistralclient:
status: Fix Committed → Fix Released
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.