Eli, I'm ok with removing that test but we'll still have the real problem, which is the fact that heat hangs in heat_stack_create while /something/ in cloud init fails to complete. Currently, the theory is that etcdctl hangs, which leaves the entire stack in the progress state [1]. Case in point, when bay create hangs, the test would still fail after about an hour [2] by giving up trying to create a bay. The last couple of days we've really been seeing a myriad of issues in the gates not related to Magnum, from keystone version bump to apt-get failing (which caused the majority of check failures). I agree with the frustration but I'm afraid that just taking that test out won't fix all our problems.
Thanks, Dimitry [1] https://bugs.launchpad.net/magnum/+bug/1541105 [2] http://logs.openstack.org/65/272965/7/check/gate-functional-dsvm-magnum-api/4a35917/console.html#_2016-02-04_02_57_03_244 From: Eli Qiao <liyong.q...@intel.com<mailto:liyong.q...@intel.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, February 3, 2016 at 10:03 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Magnum] Remove time costing case from gate-functional-dsvm-magnum-api hello all, as you see that[1], gate failed to merge patch though gate since gate-functional-dsvm-magnum-api will cause timeout error and make job failed. by investigate cases in gate-functional-dsvm-magnum-api, these 2 are time costing. 2016-02-03 22:25:42.834<http://logs.openstack.org/94/260894/1/check/gate-functional-dsvm-magnum-api/f21b118/console.html#_2016-02-03_22_25_42_834> | 2016-02-03 22:25:42.811 | magnum.tests.functional.api.v1.test_bay.BayTest.test_update_bay_name_for_existing_bay[negative] 1350.770 2016-02-03 22:25:42.836<http://logs.openstack.org/94/260894/1/check/gate-functional-dsvm-magnum-api/f21b118/console.html#_2016-02-03_22_25_42_836> | 2016-02-03 22:25:42.814 | magnum.tests.functional.api.v1.test_bay.BayTest.test_create_list_and_delete_bays[positive] 1300.981 I suggest to remove test_update_bay_name_for_exiting_bay as it can be covered by unit test. I proposed 2 patch to achieve that, please help to do review[2], let avoid reverify time to time. [1]https://review.openstack.org/#/c/260894/ [2]https://review.openstack.org/276028https://review.openstack.org/276029 -- Best Regards, Eli(Li Yong)Qiao Intel OTC China
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
