Friday, 2018-11-16

*** tosky has quit IRC00:04
*** derekh_afk has quit IRC00:20
*** saneax has quit IRC00:40
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone @ https://review.openstack.org/604298, stable/pike: tripleo-ci-centos-7-scenario002-multinode-oooq-container @ https://review.openstack.org/602248, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone, tripleo-ci-centos-7-scenario007-multinode-oooq- (1 more message)00:49
rlandyweshay: you still around?01:03
rlandyweshay: if so, at what point do we expect the zuul change to be applied if the change is mode to tripleo-quickstart/tripleo-ci?01:04
rlandynot dlrn01:04
*** rlandy is now known as rlandy|biab01:09
weshayrlandy|biab, I think the ci repos need to updated w/ the zuul change right after invoking the script01:44
*** weshay is now known as weshay_pto01:44
*** chem` has joined #oooq02:33
*** chem has quit IRC02:37
*** rlandy|biab is now known as rlandy02:45
*** rlandy has quit IRC02:45
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone @ https://review.openstack.org/604298, stable/pike: tripleo-ci-centos-7-scenario002-multinode-oooq-container @ https://review.openstack.org/602248, master: tripleo-quickstart-extras-gate-master-delorean-full-featureset052, tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci- (1 more message)02:49
*** ykarel|away has joined #oooq03:04
*** udesale has joined #oooq03:51
*** chem` has quit IRC04:17
*** ykarel|away is now known as ykarel04:32
*** chandankumar has joined #oooq04:33
*** chandankumar is now known as chkumar|ruck04:36
*** ykarel has quit IRC04:37
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone, tripleo-ci-centos-7-scenario007-multinode-oooq-container @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-quickstart-extras-gate-master-delorean-full-featureset052,  (1 more message)04:49
*** ykarel has joined #oooq04:53
*** ratailor has joined #oooq05:22
*** saneax has joined #oooq05:41
*** jfrancoa has joined #oooq06:20
*** jaganathan has quit IRC06:30
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone, tripleo-ci-centos-7-scenario007-multinode-oooq-container @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-quickstart-extras-gate-master-delorean-full-featureset052,  (1 more message)06:49
Tengupanda|rover|off: it was https://review.openstack.org/#/c/618092/06:51
Tengualready merged.06:51
*** apetrich has joined #oooq07:03
*** quiquell|off is now known as quiquell07:09
*** saneax has quit IRC07:21
*** jtomasek has joined #oooq07:27
*** ykarel is now known as ykarel|lunch07:58
quiquellmarios: How can I help with the 001 thing to standalone ?08:05
quiquellmarios: good morning btw08:05
*** jbadiapa has quit IRC08:07
chkumar|ruckquiquell, marios \o/08:09
quiquellchkumar|ruck: o/08:12
*** bogdando has joined #oooq08:18
*** amoralej|off is now known as amoralej08:20
*** holser_ has joined #oooq08:26
mariosquiquell: o/ morning08:35
mariosquiquell: not really much at the moment for that - alex/wes were discussing last night about the override for featureset_overide here https://review.openstack.org/61687208:35
mariosquiquell: i will update that there is a nit as folco pointed out but after this just a small matter of making the job green :)08:36
mariosquiquell: so last run was like http://logs.openstack.org/72/616872/26/check/tripleo-ci-centos-7-scenario001-standalone/e2a851b/logs/undercloud/home/zuul/standalone_deploy.log.txt.gz#_2018-11-15_22_46_4808:36
quiquellmarios: ack,08:36
mariosquiquell: if it settles today wrt the approach (looks like we are mostly agreeing now, this featureset override was the last detail i think for now) then we can just split the others08:37
mariosquiquell: so you can take scen2 for example08:37
mariosquiquell: so maybe that is something to do too i mean start looking at the other scenarios we have 4 for this sprint but lets see how many we do :)08:38
quiquellmarios: Will take scenario002 and will try to replicate to 0001 stuff08:39
quiquellmarios: It's that ok ?08:39
mariosquiquell: right sounds good man08:39
quiquellmarios: So I have to replicate first the 002 environment yaml I suppose first08:39
quiquellmarios: then the featureset08:39
quiquellmarios: then the  job08:39
mariosquiquell: well no featureset08:39
mariosquiquell: that was the point of featureset_override08:39
mariosquiquell: so we don't need it sec08:39
quiquellmarios: Ahh cool cool08:39
quiquellmarios: So we use directly the  052 featureset with featureset_override in the job08:40
marioshttps://tree.taiga.io/project/tripleo-ci-board/task/363?kanban-status=144727808:40
mariosquiquell: read here i explained a bit in the description08:40
quiquellmarios: ack08:40
mariosquiquell: right chkumar|ruck++ idea08:41
hubbot1marios: chkumar|ruck's karma is now 308:41
mariosvery good one08:41
quiquellmarios: You have remember me that I have to talk with upgrade guys about reusing featurests08:41
mariosthough it caused quite a bit of discussion in the end we convinced weshay_pto :)08:41
quiquellmarios: chkumar|ruck++ already tested at puppet projects08:41
hubbot1quiquell: chkumar|ruck's karma is now 408:41
quiquellmarios: That's difficult :-)08:41
chkumar|ruckquiquell, marios thanks :-)08:42
chkumar|ruckquiquell, marios https://docs.openstack.org/tripleo-docs/latest/contributor/check_gates.html#featureset-override08:42
chkumar|ruckadvertized here08:42
chkumar|ruckwe can expand the docs here for scenario job and list all the jobs at one place08:43
marioschkumar|ruck: yeah but trouble is weshay_pto doesn't like it as a general purpose thing (well in this case he didn't like the environment file override because others will use it and then we have problems if env files are maintained)08:43
quiquellmarios: Humm, also you need the job yaml to run this, with quickstart I think you just pass featuresets and release file08:44
quiquellmarios: I mean it means dependency to reproducer to run this08:44
marioschkumar|ruck: in the end the compromise was we don't pass the feature directly through the override but instead expose standalone_environment_files and then translate it i.e. like here https://review.openstack.org/#/c/616872/27/zuul.d/standalone-jobs.yaml where you add it to your job then we munge it here https://review.openstack.org/#/c/616872/27/playbooks/tripleo-ci/run-v3.yaml08:44
mariosstandalone_environment_files is a new ci specific thing which you can override and it gets passed to the deployment as standalone_custom_env_files08:45
mariosquiquell: ^08:45
chkumar|ruckmarios, but there is a problem in the long run08:45
chkumar|ruckmarios, we end up adding lots of vars there08:45
marioschkumar|ruck: right and its one of those "you had to be there" to know wtf it does but ...08:45
* marios shrug 08:46
mariosi don't know what the right way is. alex point was exactly that i.e. why do we keep adding vars and overriding things but weshay_pto point is also valid08:46
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone, tripleo-ci-centos-7-scenario007-multinode-oooq-container @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-quickstart-extras-gate-master-delorean-full-featureset052,  (1 more message)08:49
chkumar|ruckmarios, in devstack jobs, https://github.com/openstack-dev/devstack/blob/master/.zuul.yaml#L10708:51
chkumar|ruckthey include the roles and i think they just set it there08:52
chkumar|ruckas a vars08:52
*** ykarel|lunch is now known as ykarel08:54
marioschkumar|ruck: cool08:54
chkumar|ruckmarios, I am not sure it will work in our case08:55
chkumar|ruckmarios, as our roles are in TQE and TQ, may we once merge these two repo in TOCI, that will open few more posibilties08:55
quiquellmarios: So we merge the two environment files with featurest_override option ?08:56
quiquellmarios: Ahh no08:57
mariosquiquell: well not merge. the idea is to pass the standalone_custom_env_files to the deployment. standalone_environment_files is just something we made up08:57
*** tosky has joined #oooq08:57
*** saneax has joined #oooq08:57
mariosquiquell: this ismy v23 fro yesterday little different but maybe clearer as to the point here https://review.openstack.org/#/c/616872/21/playbooks/tripleo-ci/run-v3.yaml08:58
mariosquiquell: i was just using regex/replace s/standalone_environment/standalone_custom_env_files08:58
*** holser_ has quit IRC08:59
quiquellmarios: Too much noise to just have an absolute path08:59
mariosquiquell: right i was adding the path too like https://review.openstack.org/#/c/616872/21/zuul.d/standalone-jobs.yaml09:01
mariosquiquell: so in the job you just give the name09:01
quiquellmarios: Prefer that, or even implement it as part of Standalone, like adding it09:02
quiquellmarios: I think it's done in other featuresets that use thth09:02
quiquelltht09:02
mariosquiquell: yeah actually that isn't about usability primarily but rather to resttrict it. so whichever env they want to specify HAS to live in usr/shar/tht/ci/environments09:02
quiquellmarios: Also why we don't use standalone_custom_env_files directly as name in featureset_override ?09:03
mariosquiquell: to restrict its use09:03
quiquellmarios: Is uglier but explicit09:03
*** panda|rover|off is now known as panda09:03
quiquellmarios: It's part of the disccussion I haven't read I suppose :-/09:03
quiquellmarios: btw found little nit that can break other jobs09:04
*** chkumar|ruck has quit IRC09:04
quiquellmarios: Why do we need the restriction ?09:05
quiquellmarios: Going to read a little before talk :-)09:06
mariosquiquell: because this is not meant to be a general purpose 'override environment files in your jobs' thing but specifically a 'override the standalone env files, only for these scenario jobs'09:07
marioswe don't want people using it09:07
mariosquiquell: now it made more sense when we even assumed tht/ci/environment in the path and you only specify scenario1.yml BUT now09:08
mariosquiquell: latest version is like this https://review.openstack.org/#/c/616872/27/zuul.d/standalone-jobs.yaml so we are basically allowing any env under tht, making it more general again09:08
mariosquiquell: thus we may as well us the original name i think. i'll add that comment. but honestly i just want to make our minds up and go with it.. :/09:08
quiquellmarios: we review those, is not like the are going to break them09:09
mariostoo much discussion...09:09
quiquellmarios: Yep sorry :-/ it's only that add more ad-hoc stuff to the CI workflow09:09
quiquell:-/09:09
mariosquiquell: yeah indeed.09:09
mariosquiquell: as i said it made more sense before but if we are going to allow it unrestrricted may as well use tha original name gonna comment09:10
quiquellmarios: Humm I understand it now, is not only about this job, but jobs people do, like it starts to scalate and peple add env file and weird paths and so on09:11
quiquellmarios: And then CI is impossible to understand or follow09:11
quiquellmarios: something like this ?09:11
mariosquiquell: right09:11
quiquellmarios: like you can have an empty featurest and put all the featureset thing in the env file and wrong stuff like that09:12
mariosquiquell: so first of all restrict to be something under tht root at least and not random location/env file . but then the problem is the env file in tht might change/folkd don't maintain it then we have problem09:12
quiquellmarios: we are the owner not only of featuresets but also featureset attribtues, that's right ?09:13
mariosquiquell: commented here https://review.openstack.org/#/c/616872/27/zuul.d/standalone-jobs.yaml09:14
*** chandankumar has joined #oooq09:15
quiquellmarios: understood09:16
quiquellmarios: It woul dbe nice to have a featurest_override role, with all this logic09:16
quiquellmarios: we are already restricing the attribute we override so from the beginning is not just a mapping, so feels like it's going to have more logic there09:17
mariosquiquell: right we are changing it by restricting thus it becomes a new thing, it isn't the normal standalone_custom_env_files that we have in the standalone deployment. we are using a new variable to create that standalone_custom_env_files and pass it on09:18
*** udesale has quit IRC09:18
quiquellmarios: thanks for the explanation, will add two task to 002, job and env file.09:20
quiquellmarios: also the we will have to override tempest, isn't it ?09:20
*** holser_ has joined #oooq09:20
chandankumarquiquell, since for tempest, in future we will move to os_tempest so overrides value change or we can featureset_override role to do the translation09:21
chandankumarby mapping each tempest var to specific os_tempest var09:21
chandankumarthis will also help not to change anything09:21
quiquellchandankumar: so tempest disappear from featureset and we just configure os_tempest ?09:22
chandankumarquiquell, nope09:22
chandankumarquiquell, temepst will be there just validate-tempest role will be removed and we can use os_tempest role https://github.com/openstack/openstack-ansible-os_tempest/09:23
chandankumaros_tempest vars is different from validate_tempest var09:23
chandankumarsince you are going to featureset_override role there I am thinking to map validate_tempest vars to os_tempest var09:23
quiquellchandankumar: Humm, the less mapping we have the better, that's good idea temporally but in feature the vars have to be os_tempest vars09:24
chandankumaryes09:24
quiquellchandankumar: But I suppose it's going to take time to have everything ported to os_tempest09:25
chandankumarquiquell, we can switch to os_tempest vars without breaking09:25
chandankumarquiquell, yes in future09:25
chandankumarfuture ~= 3-4 months09:25
quiquellchandankumar: ack, the featurest_override will be good place for those temporal mappings09:25
quiquellchandankumar: That's enough to maintain a mapping, and remove it later on09:25
chandankumaryes09:26
*** chandankumar is now known as chkumar|ruck09:27
quiquellssbarnea|bkp2: You there ?09:28
*** derekh has joined #oooq09:38
*** chem has joined #oooq09:39
*** panda is now known as panda|rover09:39
*** dtantsur|afk is now known as dtantsur09:41
*** agopi_ has joined #oooq09:51
ssbarnea|bkp2quiquell: hi! now I am.09:51
*** jbadiapa has joined #oooq09:52
quiquellssbarnea|bkp2: Are we going to activate tempest for f28 job ?09:53
quiquellpanda|rover: ^?09:53
*** rascasoft has quit IRC09:53
quiquellssbarnea|bkp2: Ahh I see we are ok09:53
*** agopi|brb has quit IRC09:53
ssbarnea|bkp2quiquell: yes. when exactly, I do not know exactly with which settings but I would assume the final goal is to match the centos one.09:54
quiquellssbarnea|bkp2: ack, about the paunch thing, looks like it's passing without it, it's using python2 ?09:54
quiquellssbarnea|bkp2: Do we have a review here ? https://tree.taiga.io/project/tripleo-ci-board/task/377?kanban-status=144727609:59
ssbarnea|bkp2let me get back to it, i have review09:59
chkumar|ruckssbarnea|bkp2, let me and arxcruz|summit and mkopec, know if you need any help on f28 tempest09:59
ssbarnea|bkp2https://review.openstack.org/#/c/617338/ -- lets assure this merges asap.10:00
quiquellssbarnea|bkp2: Alex say something about paunch not being used as module10:01
quiquellssbarnea|bkp2: Also the error is not because of this10:02
chkumar|ruckssbarnea|bkp2, please have a look at https://review.openstack.org/#/c/618163/10:02
ssbarnea|bkp2obviously that it was not used as module because it was not possible before that patch.10:02
quiquellssbarnea|bkp2: I mean10:02
quiquellssbarnea|bkp2: Ahh wait I remember we have a review that calls paunch-310:03
quiquellssbarnea|bkp2: That's why is working but you don't like suffixes10:03
ssbarnea|bkp2i don't like that approach but they are not conflicting.10:04
quiquellssbarnea|bkp2: So this is more of good to have10:04
quiquellssbarnea|bkp2: Using "python3" is using suffix too10:04
ssbarnea|bkp2well, all good tools have it. even ansible was close to having it but i got stuck due to the multiple CLI commands debate.10:05
*** holser_ has quit IRC10:05
quiquellpuff what a pain...10:05
ssbarnea|bkp2yes, but is one simple pattern reusable everywhere, without extra conditions.10:05
quiquellAt pure python3 stuff we will use directly the commands ?10:05
quiquellAnd expect they don't break stuff with python4 :-)10:06
*** udesale has joined #oooq10:10
*** dtantsur is now known as dtantsur|afk10:10
ssbarnea|bkp2panda|rover: i think you can help with https://review.openstack.org/#/c/617338/10:13
ssbarnea|bkp2quiquell: you may not have read the PEP related to command names, the plan is to go back to "python" when py2 will be out.10:13
quiquellssbarnea|bkp2: Yep that what I read, so we will have to replace stuff around again10:13
quiquellssbarnea|bkp2: python3 command will still be present ?10:13
ssbarnea|bkp2i have some reasons why I push for the python_cmd approach.... is more future proof. the current "-3" suffix is more of future-poof.10:14
ssbarnea|bkp2yep10:14
quiquellssbarnea|bkp2: ack, thanks man, let's try to merge that10:15
ssbarnea|bkp2thus is why I am trying to use module calling, when possible.10:15
quiquellssbarnea|bkp2: But we have to ensure that commind calling is working too10:16
mariospanda|rover: o/10:16
quiquellssbarnea|bkp2: I think that's Alex point10:16
marioswana talk?10:16
mariospanda|rover: or would you prefer to do it at 1900 when i'm leaving ;()10:17
mariospanda|rover: :)10:17
*** udesale has quit IRC10:21
*** holser_ has joined #oooq10:28
chkumar|ruckquiquell, panda|rover How can I pull the list of failed nodes and stacks which are not able to delete by script?10:37
quiquellchkumar|ruck:10:37
quiquellchkumar|ruck: You need the nodepool access and you can do a openstack stack list10:38
quiquellchkumar|ruck: There you will see DELETE_FAILED or similar10:38
chkumar|ruckquiquell, which I donot have10:38
chkumar|ruckaccess to nodepool10:39
panda|roverchkumar|ruck: you don't have nodepool tenant password ?10:39
*** saneax has quit IRC10:39
chkumar|ruckpanda|rover, nope10:39
quiquellchkumar|ruck: priv10:39
chkumar|ruckpanda|rover, last time it happened, quiquell done it10:39
panda|roverquiquell: priv on internal IRC please ...10:39
panda|roverquiquell: or use dcc chat10:40
quiquellpanda|rover: ack10:40
quiquellchkumar|ruck: check email10:41
*** saneax has joined #oooq10:41
chkumar|ruckquiquell, not received yet10:42
chkumar|ruckpanda|rover, pleas join #rhos-ops internally10:46
chkumar|rucke*please10:46
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-fedora-28-standalone, tripleo-ci-centos-7-scenario007-multinode-oooq-container @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-fedora-28-standalone @ https://review.openstack.org/560445,  (1 more message)10:49
ssbarnea|bkp2tosky raised a good question regarding linting hardening: that it may make sense to attempt to make the linting fixing in separated change(s), to avoid polluting our changes.10:51
ssbarnea|bkp2with the risk of alienating few, please check https://review.openstack.org/#/c/618306/ - panda|rover chkumar|ruck quiquell10:57
panda|roverssbarnea|bkp2: can you make a bigger change ?11:02
panda|roverssbarnea|bkp2: can you put some fixes for tripleo-heat-templates, puppet-tripleo, and linux kernel too please ? :)11:02
ssbarnea|bkp2panda|rover: sure, just let me finish my cloning machine.11:03
ssbarnea|bkp2the reality is that this once could be split in two, one part for flake8 and one for ansible-lint, but i think it does not work the extra load to do that.11:04
quiquell ssbarnea|bkp2 thinking agina about the paunch thing, maybe we can just change the RPM to make paunch command the python3 version, I know this is not correct, but the future is going to be like this11:14
quiquellssbarnea|bkp2: I mean future is calling just 'command'11:15
ssbarnea|bkp2i am not so sure able that, we will always have some kind of duality. when py2 will be dead, we will have py4, or some other py* that breaks things and we will have to run things in parallel. based on the extra roundtrips for making RPM, I am *sure* that we will face the need to install from git or wheel packages,... where we do *not* have the symlinking stuff.11:17
chkumar|ruckpanda|rover, i have emailed the list of server/nodes to delete11:18
ssbarnea|bkp2also module calling method is addressing *other* problems: ability to install the tool at user level and use it, without needing root.11:18
quiquellssbarnea|bkp2: Didn't PEP say that future is using "command" and that we are not going to suffer the same again ?11:18
quiquellssbarnea|bkp2: But this is more of how thinks are designed, looks like paunch is desgined to be a command (we can replace python with another language and it shoudl work11:19
ssbarnea|bkp2in fact PSF has something baking for everyone is called a python launcher if i remember well, and guess what is another.... python_cmd tool.11:19
panda|roverchkumar|ruck: I blocked te-broker from destroying overcloud nodes,11:21
panda|roverchkumar|ruck: we are doing debugging with kieran11:21
chkumar|ruckpanda|rover, ok11:21
panda|roverchkumar|ruck: some stacks will need to be manually destryed11:22
quiquellchkumar|ruck, panda|rover: Contact first with kforde11:22
quiquellHe deal with that stuff11:22
chkumar|ruckpanda|rover, I have dropped all info in email you are in cc11:23
chkumar|ruckas per kforde there is some Db needs adjusting11:23
chkumar|ruckoh not again vexhost deployment failed11:24
panda|roverquiquell: ??11:24
panda|roverquiquell: what stuff ?11:24
quiquellpanda|rover: deleting nodepool stacks that get stuck11:24
chkumar|ruckbrb11:25
panda|roverquiquell: ok, don't touch the old stacks for now, I'can't select what te-broker is not going to destroy, so I modified destroy-env for now, until we're done11:25
*** holser_ is now known as holser|lunch11:35
*** dtantsur|afk is now known as dtantsur11:37
*** quiquell is now known as quiquell|brb11:53
chkumar|ruckpanda|rover, can we sync?12:10
panda|roverchkumar|ruck: sure12:11
panda|roverchkumar|ruck: in your channel12:12
chkumar|ruckpanda|rover, https://redhat.bluejeans.com/1571313919/6145/?src=meet_now12:12
chkumar|ruckpanda|rover, https://review.openstack.org/#/c/618477/12:13
chkumar|ruckpanda|rover, https://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/periodic-tripleo-ci-centos-7-standalone-master/0323c3f/logs/undercloud/home/zuul/undercloud_install.log.txt.gz#_2018-11-16_12_03_3512:22
*** quiquell|brb is now known as quiquell12:25
ssbarnea|bkp2marios: quiquell|brb chkumar|ruck: can we please revote on https://review.openstack.org/#/c/618131/ -- it was ready to workflow but the linters change merged before it so I had to update it.12:25
chkumar|ruckpanda|rover, https://review.rdoproject.org/zuul/builds?job_name=periodic-tripleo-ci-centos-7-standalone-master12:25
quiquellssbarnea|bkp2: is failing like shit12:26
quiquellssbarnea|bkp2: http://logs.openstack.org/31/618131/4/check/tripleo-ci-centos-7-containers-multinode/433e323/job-output.txt.gz12:28
quiquellpardon my english12:29
ssbarnea|bkp2quiquell: thanks! fixed.12:32
quiquellmarios: Add you as the QE of scenario002 ?12:34
mariosquiquell: sure12:36
mariosssbarnea|bkp2: so you decided to keep the 4 space indent?12:39
* marios shakes fist12:39
ssbarnea|bkp2quiquell: speaking about shit... i just lost o huge stash and now I am digging inside git object cache to retrieve it...12:39
ssbarnea|bkp2... using git fsck for the first time but... I fount it. reminds me of msdos days of fixing FAT partition by hand.12:40
quiquellssbarnea|bkp2: Hehe I think I have do both things, but totally forgot details :-)12:43
ssbarnea|bkp2marios: not at all, i like 2 chars for yaml. only on ini files (tox.ini) I usually use 4.12:45
ssbarnea|bkp2advise on yamllint: default settings are to check for spacing consistency inside the same file, meaning that it may decide to go to 2 or 4 based on what it finds first. thus we may see bit confusing errors but I hope everyone already knows we use "2".12:47
mariosssbarnea|bkp2: yes i am trolling you because of discussion here https://review.openstack.org/#/c/617118/1/roles/environment/tasks/main.yml12:47
mariosssbarnea|bkp2: and you 'fixed' from 4 to 2 here https://review.openstack.org/#/c/618131/3/roles/validate-tempest/tasks/tempest-rpm.yml but threw it all away in v 512:48
mariosit could have been beautiful man12:48
* marios back to regex12:48
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @  (1 more message)12:49
*** ratailor has quit IRC12:50
ssbarnea|bkp2i was curious about introduction of whitelist, i remember reading some comments about obliteration of white/black list in many codebases. i guess include/exclude are more neutral.12:50
quiquellmarios: is Alex env file usable ?12:50
mariosquiquell: how do you mean? it is being consumed by the job yes12:52
marioshttp://logs.openstack.org/72/616872/28/check/tripleo-ci-centos-7-scenario001-standalone/0134a94/logs/undercloud/home/zuul/standalone.sh.txt.gz12:52
mariosquiquell: T^ like   -e /usr/share/openstack-tripleo-heat-templates/ci/environments/scenario001-standalone.yaml \12:52
quiquellmarios: ack12:53
chkumar|ruckpanda|rover, please have a look at this bug https://bugs.launchpad.net/tripleo/+bug/180370312:53
openstackLaunchpad bug 1803703 in tripleo "[master] master standalone job is failing during undercloud install with Server Error for url: https://192.168.24.2:13696/v2.0/network" [Critical,Triaged]12:53
panda|roverchkumar|ruck: thanks12:54
chkumar|rucksee ya on monday, bye12:56
*** chkumar|ruck has quit IRC12:56
weshay_ptohey marios12:56
mariosweshay_pto: o/12:58
weshay_ptomarios, want me to sum up what alex and I agreed on? I think he captured it well in the review12:58
weshay_ptoHe wants to be able to pass a list/array of files from tht to the standalone deployment command12:59
weshay_ptowhich I'm cool w/ as long as it's from tht12:59
mariosweshay_pto: ack yeah all good seen it. commented here https://review.openstack.org/#/c/616872/27/zuul.d/standalone-jobs.yaml@9412:59
weshay_ptoif you want to chat I have a bit before I go12:59
mariosweshay_pto: no its fine. in the end lets just do one thing. i think current form is fine. we DO have new param, because we are changing the original functionality of that standalone_custom_env_files and instead construct it from our param13:00
mariosweshay_pto: we could also have argued to include ci/environments in the path but fine. ack on the list, i mean the original param is a list i just thought we'd need a single thing here for our override13:00
weshay_ptok13:01
weshay_pto{{ featureset_override | combine(custom_env, recursive=true) }}  recursive is cool13:01
weshay_ptodidn't know about that13:01
mariosweshay_pto: quiquell has started poking at scen2 based on the current scen1 state, which i think is fairly well along now design wise esp. given this very latest discussion about the featureset13:02
weshay_ptosounds great13:02
weshay_ptothere is a minor ceph issue on fs001 but you see that I'm sure13:02
weshay_ptopanda|rover, need anything while i'm around?13:02
weshay_ptopanda|rover, did you see inventory still failed on vexx13:03
mariosweshay_pto: ack yeah had to read that task a couple times ;)13:03
quiquellweshay_pto: btw zuul-in-a-box deploying standalone and running tempest13:03
mariosweshay_pto: but it seems to do the right thing :) passing it through http://logs.openstack.org/72/616872/28/check/tripleo-ci-centos-7-scenario001-standalone/0134a94/logs/undercloud/home/zuul/standalone.sh.txt.gz13:03
weshay_ptoquiquell, oh fuck you.. that is amazing13:03
weshay_ptoquiquell++13:03
hubbot1weshay_pto: quiquell's karma is now 1313:03
panda|roverweshay_pto: yes, but we made progress at least, different error. We are working with kforde to debug the network failure in OVB, and standalone is failing in promotion, so to promote manually we would need to remove ovb and standalone from criteria13:04
panda|roverquiquell: zuul-in-a-box out of the box ? or with workarounds ?13:05
weshay_ptopanda|rover, k.. and to handle the images13:06
weshay_ptopanda|rover, by hand or by softlink13:06
ssbarnea|bkp2quiquell: marios: it seems that godzilla fix passed linters so you are welcome to review it: https://review.openstack.org/#/c/618518/13:06
panda|roverweshay_pto: so it's ok if we take an image that passes only fs002 and manually promote it  ? even if the hash that built it is failing standalone ?13:09
weshay_ptopanda|rover, I would not promote while the standalone is failing13:10
weshay_ptoit's a gate job13:10
weshay_ptoI saw chandan's bug on it13:10
panda|roverssbarnea|bkp2: you forgot to include a patch in libc in your review13:10
panda|roveryep13:10
weshay_ptopanda|rover, any upstream zuul job has to pass before we promote13:10
ssbarnea|bkp2weshay_pto: now that I see you "out" of pto, i may try to remind about  https://review.openstack.org/#/c/617338/ ?13:10
weshay_ptoas we don't want to break the gate13:10
weshay_ptobut ovb is optional at this point..13:11
weshay_ptossbarnea|bkp2, nag some folks in #tripleo man13:11
weshay_ptossbarnea|bkp2, sbaker, mandre, dprince, alex etc13:11
weshay_ptossbarnea|bkp2, k?13:12
ssbarnea|bkp2weshay_pto: sure! i didn't know the magic names, usually I look at who +W last changes to the repo.13:12
weshay_ptossbarnea|bkp2, aye np13:13
weshay_ptol8r I'll be back about 2pm MST.. take care13:16
weshay_ptohave a good weekend13:16
ssbarnea|bkp2marios: https://review.openstack.org/#/c/618477/  please.13:21
*** trown|outtypewww is now known as trown13:31
*** quiquell is now known as quiquell|lunch13:32
*** quiquell|lunch is now known as quiquell13:35
*** holser|lunch is now known as holser_13:36
*** dtrainor has joined #oooq13:41
*** rlandy has joined #oooq13:46
*** agopi_ is now known as agopi|brb13:46
*** dtantsur is now known as dtantsur|afk13:50
*** agopi|brb has quit IRC13:50
rlandymarios: hello13:53
panda|roverykarel: ping13:55
ykarelpanda|rover, pong13:55
mariosrlandy: o/13:57
panda|roverykarel: overcloud logs, I hoped it was quicker but We stil can't reach the overcloud nodes over ssh13:59
panda|roverykarel: so this https://review.openstack.org/618205 works, but w'ell have to wait for  the network problems to be resolved before we have them14:00
*** amoralej is now known as amoralej|off14:03
panda|roveramoralej|off: NOOOOOOOOOO14:03
*** amoralej|off is now known as amoralej14:04
*** amoralej is now known as amoralej|lunch14:04
quiquellpanda|rover: Do we have to backport python3 changes to rocky ?14:04
panda|roverquiquell: no14:05
panda|roverquiquell: did you get any indication on this ?14:05
panda|roverrlandy: do you have time for me today ? Apparently we have packages in Ceotos7.6 repos and we need to start some tests14:08
rlandypanda|rover:  in meeting - will ping you14:08
quiquellpanda|rover: nop just pop up into my mind14:09
panda|roverrlandy: sure, I'm in meetint too, just malloc() your time.14:09
*** quiquell is now known as quiquell|lunch14:09
*** agopi|brb has joined #oooq14:10
*** agopi|brb is now known as agopi14:10
ykarelpanda|rover, ack so u are running by turning of SSL, and now script is able to get overcloud_nodes list, but this time SSH error due to network issues14:13
ykarel?14:13
ykarelpanda|rover, do u know what is the network issue?14:13
panda|roverykarel: I think I saw ssh problems even before that patch, but I thought it was related to this bug14:19
panda|roverykarel: we are trying with kforde to hold a deploy and debug live14:20
ykarelpanda|rover, ack, yes that would help a lot14:20
*** ykarel is now known as ykarel|away14:26
*** derekh has quit IRC14:27
*** derekh has joined #oooq14:27
*** quiquell|lunch is now known as quiquell14:30
*** ykarel|away has quit IRC14:31
*** saneax has quit IRC14:32
*** vkapalav has joined #oooq14:35
quiquellrlandy: the zuul-in-a-box thingy is deploy standalone and running tempest14:40
quiquellrlandy: executor get stuck though, I have to discover why14:40
quiquellrlandy: do you want to sync ?14:40
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @  (1 more message)14:49
rlandyquiquell: in meeting with marios14:50
rlandypanda|rover: fyi ..14:51
rlandy<kforde> just to say ovb is on cloud-d now ... I think your projects are there already14:51
rlandy<kforde> so you guys could start testing there14:51
quiquellrlandy: ack14:53
*** amoralej|lunch is now known as amoralej15:00
*** ratailor has joined #oooq15:02
quiquellmarios: Can we split scenario001 job review into to https://review.openstack.org/#/c/616872 ?15:03
quiquellmarios: one with the workflow change and the other with the job itself15:03
quiquellmarios: so other scnearios depend only on the workflow change15:04
*** ykarel|away has joined #oooq15:26
rlandypanda|rover: ok - ready to meet when you are15:36
*** ratailor has quit IRC15:39
mariosquiquell: ack sorry was on phone. sure we can do it, you mean just the run-v3 change?15:40
quiquellmarios: Yep, so we can merge it before the others, if it's  not breaking anything15:40
mariosquiquell: yeah sec, doing15:41
quiquellmarios: cool thanks15:41
mariosquiquell: on its way15:48
quiquellssbarnea|bkp2: the linting change has break upgrade job15:59
quiquellssbarnea|bkp2: Nah false alarm16:02
*** quiquell is now known as quiquell|off16:13
*** jfrancoa has quit IRC16:13
*** agopi is now known as agopi|food16:25
ssbarnea|bkp2marios: quiquell|off : we need to get https://review.openstack.org/#/c/618518/ in before it upsets too many people about having to fix linting in touched files.16:26
*** d0ugal has quit IRC16:27
*** d0ugal has joined #oooq16:27
*** agopi|food has quit IRC16:33
*** agopi has joined #oooq16:33
*** agopi is now known as agopi|food16:34
*** bogdando has quit IRC16:42
*** holser_ has quit IRC16:42
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @  (1 more message)16:50
*** dtrainor has quit IRC16:51
*** agopi|food is now known as agopi17:06
rlandypanda|rover: hello17:13
rlandypanda|rover: so you happen to know when the zuul applies the change if it is not in dlrn?17:14
agopihey rlandy, I don't see any builds for openstack/browbeat here in https://review.rdoproject.org/zuul/builds?job_name=tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset05317:16
agopiI don't see any changes to https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/zuul.d/tripleo.yaml#L719 as well17:16
agopiis everything fine and is anything needed from my end?17:17
*** ykarel|away has quit IRC17:28
*** trown is now known as trown|lunch17:44
*** quiquell|off has quit IRC17:51
*** derekh has quit IRC18:01
*** rfolco has quit IRC18:31
rlandyagopi: not sure - been working exclusively on the reproducer - panda|rover?? if not - I'll look in a bit18:36
agopioh okay cool rlandy. panda|rover, please lmk if you need anything from my side.18:37
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @ https://review.openstack.org/604298, master: tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @  (1 more message)18:50
*** amoralej is now known as amoralej|off18:55
*** trown|lunch is now known as trown19:11
*** apetrich has quit IRC19:28
*** saneax has joined #oooq19:37
*** apetrich has joined #oooq19:42
*** saneax has quit IRC20:09
*** saneax has joined #oooq20:21
*** saneax has quit IRC20:38
*** rlandy has quit IRC20:47
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario008-multinode-oooq-container, tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @ https://review.openstack.org/604298, stable/pike: tripleo-ci-centos-7-scenario004-multinode-oooq-container @ https://review.openstack.org/602248, master: tripleo-ci- (2 more messages)20:50
panda|roverFINALLY I could get rdoinfo job to launch quickstart ... was losing my sanity21:03
*** panda|rover is now known as panda|rover|off21:03
*** agopi has quit IRC21:14
*** holser_ has joined #oooq21:18
*** holser__ has joined #oooq21:28
*** holser__ has quit IRC21:28
*** holser_ has quit IRC21:31
*** trown is now known as trown|outtypewww22:07
hubbot1FAILING CHECK JOBS on master: tripleo-ci-centos-7-scenario008-multinode-oooq-container, tripleo-ci-centos-7-scenario001-multinode-oooq-container, tripleo-ci-centos-7-scenario007-multinode-oooq-container, tripleo-ci-centos-7-standalone-upgrade @ https://review.openstack.org/604298, stable/pike: tripleo-ci-centos-7-scenario004-multinode-oooq-container @ https://review.openstack.org/602248, master: tripleo-ci- (2 more messages)22:50
*** jtomasek has quit IRC23:15

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!