kube-manager namespace tests do not include checks for all related resources

Bug #1703839 reported by Artur Dębski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
Undecided
Artur Dębski
OpenContrail
New
Undecided
Artur Dębski

Bug Description

In kube-manager test cases for namespaces, test tests do not include checks for all namespace related resources in Contrail.

For namespace, we need to check existence of a Project and Virtual Network.
Project resource must be checked in all test scenarios.
Virtual Network creation only happens in namespace isolation.

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/33563
Submitter: Artur Debski (<email address hidden>)

Changed in opencontrail:
assignee: nobody → Artur Dębski (artur-debski)
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/33563
Committed: http://github.com/Juniper/contrail-controller/commit/908ed6876e2b538dc900235ac84dfdbabf44cb5e
Submitter: Zuul (<email address hidden>)
Branch: master

commit 908ed6876e2b538dc900235ac84dfdbabf44cb5e
Author: Artur Dębski <email address hidden>
Date: Wed Jul 12 15:46:42 2017 +0200

Add additional resource checks in namespace tests

Testing code for namespaces must check for existence of Project resource
in every test scenario. This is not reflected in the code.
Also, in namespace isolation scenario, there are no checks for creation
of isolated Virtual Network.
Add missing resource checks.
Also, simplify test code - no need for double namespace object creation
in the tests.
Additionally, pylint the code.

Change-Id: I182971b04bd7c8d54cb123c011420e55dbd5ac92
Closes-Bug: #1703839

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.