GBP Service chaining errors are are not vsible to the user because of not having status attribute

Bug #1479706 reported by Magesh GV
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy
Confirmed
High
Magesh GV

Bug Description

GBP Resources (PTG and Servicechain instance) are missing status option due to which some errors are not vsible to the user.

In service chain instance create, most of the drivers perform asynchronous activities like VM launch, deploying a heat template etc. Here, we cannot block until the activity is completed. User will not know of any error occuring after the api call has returned.

We should have a status field for PTG and Service chain instance.

Changed in group-based-policy:
milestone: none → next
assignee: nobody → Magesh GV (magesh-gv)
importance: Undecided → High
status: New → Confirmed
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.