Monday, 2019-03-04

sfbenderFabien Boucher created software-factory/sf-ci master: Fix repoxplorer functional test for last repoxplorer version  https://softwarefactory-project.io/r/1512301:54
sfbenderTristan de Cacqueray created software-factory/sf-config master: cauth: prevent deployment issue when running on external host  https://softwarefactory-project.io/r/1512401:58
sfbenderTristan de Cacqueray created software-factory/sf-config master: cgit: fix multinode deployment without gerrit  https://softwarefactory-project.io/r/1512501:58
sfbenderTristan de Cacqueray created software-factory/sf-config master: config-update: replace fetch by synchronize  https://softwarefactory-project.io/r/1512601:58
sfbenderTristan de Cacqueray created software-factory/managesf master: configurations: remove the git clone depth argument  https://softwarefactory-project.io/r/1512702:35
sfbenderTristan de Cacqueray created software-factory/sf-config master: cgit: add smart http git transport configuration  https://softwarefactory-project.io/r/1512803:42
sfbenderTristan de Cacqueray created software-factory/sf-config master: cgit: enable local-cgit repo to be configured  https://softwarefactory-project.io/r/1512903:42
*** raukadah has quit IRC05:45
*** chandankumar has joined #softwarefactory05:46
*** jangutter has joined #softwarefactory07:23
sfbenderTristan de Cacqueray created software-factory/sf-config master: cgit: do not require component when config locations are remote  https://softwarefactory-project.io/r/1513007:35
janguttertristanC: thanks very much for your help on Friday, after a set of reboots everything is working perfectly!07:57
tristanCjangutter: excellent, that's good to hear07:57
tristanCjangutter: i'm pretty sure it was related to the fast-forward-upgrade from 3.0 to 3.207:58
janguttertristanC: yep. Also, our 3.0 install was "unorthodox" to say the least. I did a backup -> recover -> FF upgrade.07:58
tristanCjangutter: from now on, using "sfconfig --update" should just work automagically07:58
janguttertristanC: I'm working through the papercuts left over. I notice https://softwarefactory-project.io/r/#/c/10569/ regressed, unfortunately.07:59
janguttertristanC: manually adding rev 1 of that patch works around the issue again.07:59
tristanCjangutter: arg, indeed, the patch somehow dissapeared. looking for what happened08:06
janguttertristanC I found it.08:06
janguttertristanC: https://softwarefactory-project.io/r/#/c/13569/ <--- this "reverted" it.08:07
tristanCjangutter: my bad, let me revert that chunk08:08
sfbenderTristan de Cacqueray created software-factory/sf-config master: base: ensure DocumentRoot is set to /var/www  https://softwarefactory-project.io/r/1513408:09
sfbenderJan Gutter created software-factory/sf-config master: Set DocumentRoot explicitly in logserver conf  https://softwarefactory-project.io/r/1513508:11
jangutterWhoops.08:11
janguttertristanC: I was worried that DocumentRoot should be /var/www/html in certain circumstances.08:13
tristanCjangutter: that works for me, we'll merge your version08:15
janguttertristanC: another one that should be a clean backport to 3.2 is: https://softwarefactory-project.io/r/#/c/15131/08:15
janguttertristanC: but other than that, things went more smoothly than I expected. I switched from a nodepool/openstack vm based jobs to runC based jobs and things are working pretty well.08:17
janguttertestinfra does fail when the nodepool/runC bits don't start up 100%, but that was easy to fix08:19
tristanCjangutter: thanks for the backport, once our cloud provider is working we'll land it in 3.208:22
tristanCjangutter: what was the testinfra issue with runC?08:23
janguttertristanC: no worries, I'll try to shake out as much as I can. Thanks a lot for all the work you guys are doing and we're shamelessly using :-p08:23
janguttertristanC: it's not a biggie: I just noticed that testinfra fails if test nodes haven't been spun up by nodepool yet.08:24
janguttertristanC: since one of the tests is "are there running containers". If nodepool is slow or something, the test might fail even though the runC node is running "perfectly".08:25
janguttertristanC: but at that stage, software-factory is up and running, and cleaning out the stale nodes on nodepool made everything work.08:27
janguttertristanC: specifically - https://github.com/softwarefactory-project/sf-config/blob/master/testinfra/test_hypervisor-runc.py#L19 <--- if nodepool hasn't spawned the nodes, this'll fail even if runC is happy.08:29
janguttertristanC: I'm not sure how to "fix" the test though.08:30
tristanCjangutter: oh right, i think the fix is to remove the min-ready from the default configuration and remove that test08:35
tristanCjangutter: instead, we could check that the provider got started properly08:35
*** jpena|off is now known as jpena08:56
sfbenderMerged DLRN master: Remove unneeded "git reset" in the run method  https://softwarefactory-project.io/r/1511609:40
*** jangutter_ has joined #softwarefactory11:07
*** jangutte_ has joined #softwarefactory11:09
*** jangutter has quit IRC11:09
*** jangutter_ has quit IRC11:11
*** jangutte_ is now known as jangutter11:25
jangutterHi, weird question. I've been using rh-python35-python-shade  and ansible on software-factory 3.1... any alternatives you could suggest?12:09
sfbenderJavier Peña created dlrnapi_client master: Fix exception handling  https://softwarefactory-project.io/r/1513812:37
*** jpena is now known as jpena|lunch12:38
*** jpena|lunch is now known as jpena13:31
*** mhu has quit IRC13:36
*** mhu has joined #softwarefactory13:37
*** rfolco is now known as rfolco|pto13:50
jangutter(facepalm - rh-python35-python-shade -> rh-python35-python-openstacksdk )15:16
*** chandankumar is now known as raukadah15:32
dmsimardjangutter: shade was eventually replaced by openstacksdk17:45
dmsimardit was merged and integrated in openstacksdk17:45
jangutterdmsimard: I have to doublecheck if ansible picks it up though....17:48
dmsimardjangutter: which ansible ? the one used to deploy SF ?17:49
jangutterdmsimard: the one running inside SF: I had a nice docker set up with sf-3.1's ansible scl and used the os_server module for example.17:50
jangutterdmsimard: it's not critical - the one shipped by centos (non-scl version) also works.17:51
dmsimardjangutter: the ansible modules import openstacksdk iirc -- it should work17:51
jangutterdmsimard: I'll run some checks later when I get more time to verify - there's a .80 chance it's PEBCAK on my part.17:54
dmsimardjangutter: sure, keep us updated :D17:56
jangutterweird question: I'm looking at your nodepool.yaml config and I see: ELEMENTS_PATH: /etc/opt/rh/rh-python35/nodepool/elements:/usr/share/project-config/nodepool/elements18:10
jangutteris /usr/share/project-config/nodepool/elements something specific to your setup?18:11
dmsimardjangutter: yeah.18:12
dmsimardjangutter: Some of our images rely on nodepool elements which are provided by the upstream openstack-infra/project-config repository18:13
jangutterdmsimard: aah, so if I clone that to my builder.......18:13
dmsimardIf you're not interested in reproducing images that are fairly similar to the openstack gate ones, you can disregard that18:13
dmsimardyes, we have an adhoc process that syncs project-config to the builder node (read: a cron)18:14
*** jpena is now known as jpena|off18:27
*** sbadia has quit IRC18:35
*** sbadia has joined #softwarefactory19:37
*** ChanServ sets mode: +o sbadia19:37
*** sbadia has quit IRC20:34
*** sbadia has joined #softwarefactory20:39
*** ChanServ sets mode: +o sbadia20:39
*** shanemcd has quit IRC21:53
*** shanemcd has joined #softwarefactory21:57

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