| *** rfolco_ has quit IRC | 00:07 | |
| *** Apoorva_ has joined #openstack-third-party-ci | 00:30 | |
| *** Apoorva has quit IRC | 00:34 | |
| *** Apoorva_ has quit IRC | 00:35 | |
| *** rfolco has joined #openstack-third-party-ci | 01:31 | |
| *** rfolco has quit IRC | 01:31 | |
| *** s-shiono has quit IRC | 02:10 | |
| *** stakeda has joined #openstack-third-party-ci | 04:25 | |
| *** pooja__ has joined #openstack-third-party-ci | 06:07 | |
| pooja__ | creating setup for OpenStack Third-Party CI Setup | 06:07 |
|---|---|---|
| pooja__ | but facing issue during image build for noodpool | 06:07 |
| pooja__ | getting this error ERROR jobs.ImageBuildJob: DIB Image image-build (id 2) failed to build. Deleting | 06:07 |
| pooja__ | can comebody plz help in this | 06:08 |
| *** isaacb has joined #openstack-third-party-ci | 06:24 | |
| *** stakeda has quit IRC | 11:09 | |
| *** lennyb has quit IRC | 11:29 | |
| *** lennyb has joined #openstack-third-party-ci | 11:30 | |
| *** rfolco has joined #openstack-third-party-ci | 11:43 | |
| asselin_ | pooja__, there should be some log files that give you an error message | 13:42 |
| asselin_ | look inside /var/log/nodepool/image | 13:42 |
| pooja__ | Hi asselin: yes i am having will uplodeit and send u the link | 13:44 |
| pooja__ | https://gist.github.com/anonymous/fdb50d0e476d7a620a2a14d19dcaddd3 | 13:45 |
| pooja__ | PFA | 13:45 |
| asselin_ | can you try using http://paste.openstack.org/ instead? | 13:46 |
| asselin_ | and just the snippet for the error message? | 13:46 |
| asselin_ | gist makes it hard to look at long lines | 13:46 |
| *** NileshSawant has joined #openstack-third-party-ci | 13:48 | |
| pooja__ | actually i tried that but was not able to detect the actual error | 13:52 |
| pooja__ | thats why | 13:52 |
| asselin_ | hmmm...maybe paste the last 500 lines? | 13:54 |
| pooja__ | we were not able to fetch latest changes for /etc/nodepool/nodepool.yaml | 13:55 |
| pooja__ | http://paste.openstack.org/show/607336/ | 14:00 |
| pooja__ | Hi asselin : can plz have look for this logs | 14:02 |
| pooja__ | http://paste.openstack.org/show/607338/ | 14:02 |
| pooja__ | http://paste.openstack.org/show/607339/ | 14:05 |
| pooja__ | http://paste.openstack.org/show/607340/ | 14:05 |
| *** esberglu has joined #openstack-third-party-ci | 14:05 | |
| *** pabelanger has joined #openstack-third-party-ci | 14:10 | |
| pabelanger | NileshSawant: lets continue here | 14:11 |
| NileshSawant | pabelanger: sure, am trying this out , will udpate you | 14:12 |
| *** tushar_ has joined #openstack-third-party-ci | 14:14 | |
| asselin_ | pooja__, I think this is the error: 2017-04-20 10:57:06,253 INFO nodepool.image.build.dpc: dib-run-parts Thu Apr 20 05:27:06 UTC 2017 Running /tmp/in_target.d/install.d/91-venv-os-testr | 14:14 |
| asselin_ | remove that file from your project-config and try again | 14:15 |
| tushar_ | HI | 14:15 |
| pabelanger | morning! | 14:28 |
| pabelanger | let me try and explain the recent failures you might be seeing with 3rd-party CI lately. | 14:29 |
| pabelanger | 2 weeks ago we started the process to unpuppet our diskimage-builder images, in a effort to bring new OSes online easier. With nodepool.o.o that works has gone smoothly. | 14:29 |
| pabelanger | however, with 3rdparty CI, were are seeing some issues. | 14:30 |
| pabelanger | this is because, your local version of project-config appears to be lagging behind our version upstream | 14:30 |
| pabelanger | So, my question is, how often do people resync with project-config? | 14:31 |
| pabelanger | because, we now have important changes for nodepool diskimage-images that exists there | 14:31 |
| pooja__ | hi asselin: from where to remmpove this file | 14:33 |
| asselin_ | pooja__, it should be somewhere in your project-config repo | 14:33 |
| tushar_ | Pabelanger : In our setup, we have fixed the project-config to a particular version | 14:34 |
| tushar_ | and usually we are not upgrading this | 14:34 |
| pabelanger | okay, that explains the breakages for you | 14:35 |
| pabelanger | because, you are missing the other 1/2 of changes with system-config | 14:35 |
| NileshSawant | pabelanger : in out case the image is sync in 15 days | 14:35 |
| NileshSawant | *our | 14:35 |
| tushar_ | okay | 14:35 |
| pabelanger | the end goal, is to remove the need for 3rdparty to depend on system-config, and instead only require project-config | 14:35 |
| NileshSawant | that will be great | 14:36 |
| asselin_ | pabelanger, what is still in system-config for recent changes? | 14:36 |
| pabelanger | so, for the next week or so, it will be a bumpy ride I think. Once we are completely off system-config, we should not have this problem moving forward | 14:36 |
| NileshSawant | I hope the documention is also updated for this | 14:36 |
| pabelanger | asselin_: https://review.openstack.org/#/q/topic:unpuppet-zuul-workers is the topic for changes | 14:37 |
| pabelanger | NileshSawant: yes, we'll have to update the docs for sure | 14:37 |
| NileshSawant | great ! | 14:38 |
| asselin_ | ok I see...project-config dependencies to system-config | 14:38 |
| pabelanger | yes, we've been moving stuff out of puppet into DIB elements directly | 14:39 |
| NileshSawant | pabelanger :actully We have cinder CI running correctly, We need a CI for os_brick as well | 14:40 |
| NileshSawant | is it possible to use same for both ? | 14:40 |
| pabelanger | same CI account? | 14:41 |
| NileshSawant | yes with same account and from same node | 14:41 |
| pabelanger | there is no technical reason stopping you. You'll just be running more jobs on the single system | 14:42 |
| pabelanger | I would check with os_brick first, that the account from cinder will also comment on changes | 14:42 |
| NileshSawant | yes, can you point me the zuul layout.yaml for running multiple project | 14:42 |
| pabelanger | NileshSawant: http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n3763 | 14:43 |
| pabelanger | you would just add another project under the projects section in layout.yaml | 14:43 |
| NileshSawant | yes this looks good to me. | 14:44 |
| NileshSawant | for now we are using this, but we Defiantly try creating new noodpool env after 15 days | 14:45 |
| NileshSawant | will just wait for these new changes get in | 14:47 |
| tushar_ | Pabelanger : As you mentioned the nodepool.o.o will unpuppet the diskimage building | 14:53 |
| tushar_ | this is the new version of nodepool? | 14:53 |
| pabelanger | tushar_: no, just DIB elements that nodepool will run | 14:54 |
| *** isaacb has quit IRC | 14:54 | |
| tushar_ | Pabelanger : okk | 14:55 |
| *** isaacb has joined #openstack-third-party-ci | 15:11 | |
| *** pooja__ has quit IRC | 15:12 | |
| *** NileshSawant has quit IRC | 15:46 | |
| *** isaacb has quit IRC | 16:08 | |
| *** esberglu has quit IRC | 16:55 | |
| *** Apoorva has joined #openstack-third-party-ci | 17:28 | |
| *** tushar_ has quit IRC | 17:31 | |
| *** esberglu has joined #openstack-third-party-ci | 17:34 | |
| rajinir | Gerrit queries: I'm trying to list all the patchets our Job failed or didn't run due other issues. Has anyno written one? | 20:15 |
| asselin_ | rajinir, http://ci-watch.tintri.com/project?project=cinder&time=24+hours | 20:55 |
| rajinir | asselin_ I've know about the ci-watch by tintri. I'm trying to write a python script and parse the result and trigger the failed builds though zuul | 20:58 |
| asselin_ | rajinir, ok....I'm not aware of any such tool | 20:58 |
| rajinir | https://www.irccloud.com/pastebin/dX0PSdHr/gerrit | 20:58 |
| mmedvede | I think a few people wrote queries in the past | 20:58 |
| rajinir | I have this query, but the thirdparty job results are missing when I run the query | 20:59 |
| asselin_ | rajinir, you can look at this which might be a starting point: https://github.com/jogo/lastcomment | 20:59 |
| mmedvede | also see https://review.openstack.org/#/c/430439/ | 21:00 |
| *** rfolco has quit IRC | 21:01 | |
| mmedvede | It says the script is based on lastcomment | 21:01 |
| rajinir | mmedvede>, asselin_ Thanks, these are helpful. Will check them out | 21:02 |
| mmedvede | rajinir: iirc, you are not supposed to comment on the same patch twice. E.g. if our CI reported failure, you should not just report another result without an explicit recheck. | 21:03 |
| mmedvede | s/our/your/ | 21:03 |
| rajinir | mmedvede> These failures are because of some upgrade issues or devstack patch that broke the builds for days | 21:04 |
| *** krtaylor has quit IRC | 21:16 | |
| *** krtaylor has joined #openstack-third-party-ci | 21:23 | |
| *** esberglu has quit IRC | 21:46 | |
| *** esberglu has joined #openstack-third-party-ci | 21:46 | |
| *** esberglu has quit IRC | 21:51 | |
| *** Apoorva_ has joined #openstack-third-party-ci | 22:08 | |
| *** Apoorva has quit IRC | 22:11 | |
| *** Apoorva_ has quit IRC | 22:41 | |
| *** Apoorva has joined #openstack-third-party-ci | 22:41 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!