09:02:37 #startmeeting powervm_driver_meeting 09:02:38 Meeting started Wed Jun 12 09:02:37 2019 UTC and is due to finish in 60 minutes. The chair is dikonoor. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:42 The meeting name has been set to 'powervm_driver_meeting' 09:04:01 As part of today's meeting we will cover the PowerVM CI and the OOT out of sync problems 09:04:46 #topic PowerVM CI 09:05:03 mujahidali: What's the latest update on the CI. 09:05:58 I believe amansi26 was running into some neutron l3 agent issues when stacking devstack. 09:06:23 dikonoor: We are trying to fix issue with devstack stacking here is the fix proposed by amansi26: https://review.opendev.org/#/c/663868/ 09:07:20 mujahidali: I think you posted the wrong link. https://review.opendev.org/#/c/663868/ is not the devstack changeset 09:07:53 amnsi26: is working on fixing the UT failures for the above patch 09:07:53 amansi26: Could you post the changeset you proposed for devstack for the stacking problem? 09:08:07 devstack change: https://review.opendev.org/#/c/664797/ 09:09:16 #link https://review.opendev.org/#/c/664797/ >> for the devstack stacking issue 09:10:18 The change 664797 is dependant on another change 663868 by amansi26: 09:10:20 amansi26: From https://review.opendev.org/#/c/664797/, the actual error that you were hitting is not clear. Is there a LP bug you have opened for this, that explains the problem details? 09:11:09 amansi26: If there isn't one, it will get very tricky for reviewers to comprehend the problem. Could you open a LP bug against devstack explaining the problem that you were running into ? 09:11:38 and then propose this changeset as part of that ? Basically update the commit msg of this to say closes-bug ? 09:12:26 #action amansi26 to open a devstack LP bug for the neutron l3 problem and propose changeset for that. 09:12:38 amansi26: ter ? 09:13:38 dikonoor: No there is no bug open for devstack in the LP. 09:13:58 amansi26: Could you open one? 09:14:09 Sure 09:15:49 amansi26: Thanks. It is not clear from the changeset how the proposed changeset will resolve the problem..especially because the problem is not unknown/clear 09:16:25 amansi26: mujahidali: With this patch in the local environment, are we able to proceed with the manual CI run ? 09:17:07 we are able to stack in the localenv. 09:17:29 dikonoor: nova-powervm driver is failing for some of the unit test cases as there is some Mock changes in the nova community. 09:18:52 amansi26: I was referring to the CI run, which runs tempest runs and not to the UT testcases.. After the successful installation of devstack, was the tempest run successful ? 09:19:56 dikonoor: There were failures for tempest. 09:20:10 amansi26: Approx. how many ? 09:21:01 and what are they complaining about? 09:21:17 dikonoor: Every run has different number of failures. 09:22:19 amansi26: That's very strange.. and are the testcases failing diferent? 09:22:19 dikonoor: Test case fails mostly with the log message- "TearDownClass" 09:22:38 dikonoor: yeas 09:22:38 amansi26: Any additional information? 09:24:59 amansi26: I believe you will be continuing to debug the same. #action amansi26 and mujahidali continuing to debug the cause of tempest testcase failure during a manual CI run. 09:25:22 #action amansi26 and mujahidali continuing to debug the cause of tempest testcase failure during a manual CI run. 09:25:40 #topic PowerVM driver out of sync with community 09:27:08 https://review.opendev.org/#/c/663868/ proposed by amansi26 and diffeernt changesets namely https://review.opendev.org/#/c/662393/ by aarora06 attempts to do the same 09:28:14 #link https://review.opendev.org/#/c/663868/ currently fails at 4 unit testcases. Looks like this is caused because of a mocking issue 09:28:54 Testcase expects https://github.com/openstack/nova-powervm/blob/master/nova_powervm/tests/virt/powervm/disk/test_localdisk.py#L52 to be of type EntryWrapper but it is of type mock.. 09:29:40 #action > Work on fixing the mocking problem 09:30:16 dikonoor: I am looking into the issue. 09:30:37 amansi26: Please check mock autospec functionality 09:30:44 These are the two set of immediate issues that we need resolution on. Anything else, anyone wants to bring up ? 09:32:09 nothing from me. 09:32:28 Ok then.Ending the meeting 09:32:35 #endmeeting