Fix functional test for k8s resource list api

Bug #1504379 reported by Vilobh Meshram
6
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

https://github.com/openstack/magnum/blob/master/magnum/tests/functional/test_k8s_python_client.py#L130-L137

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)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to magnum (master)

Reviewed: https://review.openstack.org/213368
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=3b1c0b28cb7910debc26eed7bf8aa8da9ed88a33
Submitter: Jenkins
Branch: master

commit 3b1c0b28cb7910debc26eed7bf8aa8da9ed88a33
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: I7905af9e22f47b16d92043cc1fdcb1cdf72ebc48

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/223384
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=067b38391cfb2e5e393d923364a05b0ae313674b
Submitter: Jenkins
Branch: master

commit 067b38391cfb2e5e393d923364a05b0ae313674b
Author: Vilobh Meshram <email address hidden>
Date: Mon Sep 14 15:02:18 2015 -0700

    Objects from Bay - Services

    Currently k8s 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 proposes the
    change to the Service object.

    Also, please refer to the related-bug as to the temporary changes
    done to make the test work for other objects namely pod, rc. 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: I05177944a693710c70a22cae57f521b0fe738e9e

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/223367
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=44122d08f8fea0bf6e83c539dde222572957acb7
Submitter: Jenkins
Branch: master

commit 44122d08f8fea0bf6e83c539dde222572957acb7
Author: Vilobh Meshram <email address hidden>
Date: Mon Sep 14 18:39:04 2015 -0700

    Objects from Bay - Pods

    Currently k8s 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 proposes the
    change to the Pod object.

    Also, please refer to the related-bug as to the temporary changes
    done to make the test work for other objects namely rc,
    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: Id5be7fba2eb8622fcfeb48068728e440a0af3f5e

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/348319

Changed in magnum:
assignee: Vilobh Meshram (vilobhmm) → yatin (yatinkarel)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/348319
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=0f3ebe9a42b1d4d3cfe2a29e63d81835db93a949
Submitter: Jenkins
Branch: master

commit 0f3ebe9a42b1d4d3cfe2a29e63d81835db93a949
Author: yatinkarel <email address hidden>
Date: Thu Jul 28 19:03:18 2016 +0530

    Remove unnecessary code

    The code has to be fixed once blueprint: objects-from-bay
    is implemented. Since the bp is implemented we can now
    remove this.

    Change-Id: I88b3905b066440d64db542ef7a365896e477f95a
    Closes-Bug: #1504379
    Depends-On: I664be1b00975b048e2289f5be3270b4a00520e80

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.0.0

This issue was fixed in the openstack/magnum 3.0.0 release.

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.