Add gate test for bay deletion from others

Bug #1564032 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
In Progress
Low
Vipul Nayyar

Bug Description

Test a scenario that a user can delete a bay created by another user under the same tenant. This is for addressing @Kai Qiang comment in this patch: https://review.openstack.org/#/c/293371/

Tags: tech-debt
hongbin (hongbin034)
tags: added: tech-debt
Changed in magnum:
assignee: nobody → Vipul Nayyar (vipulnayyar)
Revision history for this message
Vipul Nayyar (vipulnayyar) wrote :

Hey hongbin, can you explain a little, what more addition is required to the tests already written? What do you mean by funcitonal testing?

Revision history for this message
hongbin (hongbin034) wrote :

Here is my thought: Have two users: user A and user B. Have user A to create a bay, let user B to delete the bay and verify it succeeds.

Changed in magnum:
status: New → In Progress
Revision history for this message
Vipul Nayyar (vipulnayyar) wrote :

Hey hongbin, do you think that we need a Tempest scenario test for this or a normal functional test would do. I was having a look at the functional testing bootstrapping code. It accepts single user credentials only from config and accordingly creates clients for it. I can probably tinker with this, but I believe that there should be a scalable testing framework for this kind of multi-user scenarios.

Is using Tempest Scenarios the answer? Else, do I need to create a module from scratch for this custom scenario to authenticate 2 clients and validate the bay delete behavior??

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/348758

hongbin (hongbin034)
Changed in magnum:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

Change abandoned by Vipul Nayyar (<email address hidden>) on branch: master
Review: https://review.openstack.org/348758
Reason: Abandoned for now

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.