Fix functional test for k8s resource list api
Bug #1504379 reported by
Vilobh Meshram
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Undecided
|
yatin |
Bug Description
As part of objects from bay, bay_uuid is not passed as a mandatory parameter for all the api's for READ/WRITE k8s resources.
The functional test seems to be failing because of it.
So in-oder to make them pass the following code will be commented out in object-from-bay patches
and once these patches are merged. The functional test will be fixed.
This bug is to keep track of the same.
Changed in magnum: | |
assignee: | nobody → Vilobh Meshram (vilobhmm) |
Changed in magnum: | |
milestone: | none → mitaka-1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/213368 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=3b1c0b28cb7 910debc26eed7bf 8aa8da9ed88a33
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3b1c0b28cb7910d ebc26eed7bf8aa8 da9ed88a33
Author: Vilobh Meshram <email address hidden>
Date: Tue Sep 8 11:00:41 2015 -0700
Objects from Bay - Replication Controller
Currently objects (pod/rc/service) are read from the
database. In order for native clients to work, they
must be read from the ReST bay endpoint. To execute
native clients, we must have one truth of the state
of the system, not two as we do now. This patch adds
changes for Replication Controller.
Also, please refer to the related-bug as to the temporary changes
done to make the test work for other objects namely pod,
service. These changes will be removed when the object from bay
patches for all the k8s objects are merged as part of a seperate
patch.
Partially- Implements: bp objects-from-bay
Related-Bug: #1502367
Related-Bug: #1504379
Change-Id: I7905af9e22f47b 16d92043cc1fdcb 1cdf72ebc48