Re: [OpenStack-Infra] Zuul v3 questions (was: Re: [openstack-dev] Update on Zuul v3 Migration - and what to do about issues)
Hello James, Thank you for replying! On 2017/10/28 7:17, James E. Blair wrote: Rikimaru Honjo writes: Hello, (Can I still use this thread?) In the future, you may want to start a new thread on openstack-infra@lists.openstack.org for general Zuul questions. I've changed the CC list and subject of this message to redirect the conversation there. Excuse me, I'm trying to run Zuul v3 in my environment, and I have three question about it. I'd appreciate it if anyone helps. My environment) I use feature/zuulv3 branch, and version is 2.5.3.dev1374. We have not released Zuul v3 yet and we don't recommend that folks use it yet unless they want to contribute to developing it. Installation and configuration is currently more difficult than we would like, and the code base is still rapidly changing. We will send out announcements when it is ready for general use (including OpenStack third-party CI). This may or may not apply to you, but I wanted to reiterate it for anyone else reading. Thanks for trying it out. :) Thank you for explaining. I understood the status of zuul v3. Q1) "Unknown option --die-with-parent" error was occurred when zuul ran job. Is there requirement of bubblewrap version? I used bubblewrap 0.1.7-1~16.04~ansible. If I removed "--die-with-parent" from zuul/driver/bubblewrap/__init__.py, above error wouldn't occurred. You will need a newer version of bubblewrap. Attempting to run with an older one will cause Zuul not to behave as expected. I believe OpenStack-infra uses a PPA with a more recent version. I confirmed the below PPA, but my version is the latest. https://launchpad.net/~ansible/+archive/ubuntu/bubblewrap Should I use ubuntu higher than 16.04...? Q2) When I specified "zuul_return" in playbook, the below error was occurred on remote host. KeyError: 'ZUUL_JOBDIR' Should I write a playbook to set a environment variable "ZUUL_JOBDIR"? I believe that zuul_return is only expected to work on the executor, so you may need to delegate this play to 'localhost' to ensure it does not run on the remote node. Q3) Setup module of ansible took long time when zuul ran jobs. My job was succeeded if I extended timeout from 60 to 120 by modifying runAnsibleSetup() in zuul/executor/server.py. But, if I run same job directly(by own), it was finished soon. Do you have any knowledge about it? I'm not sure about this. It might be related to the persistent SSH connections which are constructed by the setup task and then used by later playbook invocations. I'd start by correcting the bubblewrap issue and see if this changes. OK, I watch your work. Thanks. P.S. Is there a constructed VM image or ansible for running zuul v3...? Not yet, but we hope to have something like that before release. -Jim -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikimaru Honjo E-mail:honjo.rikim...@po.ntt-tx.co.jp ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Zuul v3 questions
Rikimaru Honjo writes: > I confirmed the below PPA, but my version is the latest. > > https://launchpad.net/~ansible/+archive/ubuntu/bubblewrap > > Should I use ubuntu higher than 16.04...? We are running on 16.04. But it looks like this is the PPA we're using: deb http://ppa.launchpad.net/openstack-ci-core/bubblewrap/ubuntu xenial main Hopefully there will be a backport soon and we can stop using it. -Jim ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [third-party][ci] Help needed with Dell EMC Gerrit CI accounts
On 2017-10-30 08:03:52 + (+), Wan, Sam wrote: [...] > 1. I can NOT login into https://review.openstack.org/ using > 'emc.vnx...@emc.com'. [...] It looks like you had two accounts: 12017 (EMC VNX CI) and 12185 (emc-vnx-ci). The earlier account has SSH username set, while the later one is the only one with a Launchpad OpenId attached to it but is marked inactive. The only way I can think of for 12017 to have no OpenId is for it to predate the third-party CI account management overhaul, so was added by request to one of our admins. The 12185 was likely set inactive sometime after you attempted to set up a Launchpad account only to discover that the conflicting E-mail address was an issue. I have "fixed" this by moving your OpenId from the inactive 12185 account to the older 12017 account so you should now be able to log into Gerrit to manage it normally. > 2. I've changed 'Full Name' for 'emc.vmax...@emc.com' account in > https://review.openstack.org/#/settings/contact but old name still > shows up in CI posts. [...] Much as in #1 above, you have an account 12016 (EMC VMAX CI) and another account 12197 (Dell EMC VMAX CI). The 12016 account has SSH access configured but the 12197 account is the only one with an OpenId (this time both accounts are set active). I have moved the OpenId from 12197 to 12016 and set 12197 inactive. > 3. Same issue happens to emc.xio...@emc.com, accounts as well. [...] Addressed in the same way as #2, I moved OpenIds from a later 12409 (Dell EMC XtremIO CI) account to an earlier 12033 (EMC XIO CI) account and then set 12409 inactive. You may need to log out of Gerrit and back in again so you will end up under the correct account. Please let us know if this did not help. -- Jeremy Stanley signature.asc Description: Digital signature ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Zuul v3 questions
Hello James, On 2017/10/31 0:56, James E. Blair wrote: Rikimaru Honjo writes: I confirmed the below PPA, but my version is the latest. https://launchpad.net/~ansible/+archive/ubuntu/bubblewrap Should I use ubuntu higher than 16.04...? We are running on 16.04. But it looks like this is the PPA we're using: deb http://ppa.launchpad.net/openstack-ci-core/bubblewrap/ubuntu xenial main Thank you so much, I could use "--die-with-parent" option with bubblewrap suggested by you. And, my 3rd problem has also been solved by the above bubblewrap! My 3rd problem: Setup module of ansible took long time when zuul ran jobs. Hopefully there will be a backport soon and we can stop using it. -Jim -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikimaru Honjo E-mail:honjo.rikim...@po.ntt-tx.co.jp ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
