Monday, 2018-01-08

*** aspiers[m] has quit IRC00:05
*** ilpianista_ has quit IRC00:05
*** masayukig[m] has quit IRC00:05
*** bandini has quit IRC00:09
*** bandini has joined #openstack-infra00:10
*** slaweq has joined #openstack-infra00:11
*** masayukig[m] has joined #openstack-infra00:12
*** bgmccollum has quit IRC00:13
*** slaweq has quit IRC00:15
*** d0ugal has quit IRC00:15
*** AJaeger has quit IRC00:16
*** sree has joined #openstack-infra00:18
dmsimardianw: you're back? :D00:18
*** comstud has quit IRC00:19
*** bgmccollum has joined #openstack-infra00:20
*** claudiub has quit IRC00:20
*** masber has joined #openstack-infra00:21
ianwdmsimard: yes, currently context switching back in from swap :)00:21
dmsimardoh, you missed out on a bunch of fun00:21
*** comstud has joined #openstack-infra00:22
ianwnext time we find structural flaws in every modern processor, it would be nice if didn't happen over the new year break00:22
clarkb++00:22
dmsimardno worries, that vulnerability is about 20 years old00:22
clarkbwe are stil lwaiting on ubuntu patches fwiw00:23
clarkbalso my debian jessie server doesn't have a new kernel yet either00:23
dmsimardyeah I think Ubuntu was waiting for ianw to be back to make sure he's there to help us :D00:23
ianwnow every system call basically implies a context switch we might as well all just move to a microkernel anyway00:26
ianwbrb, just checking how puppet works with minix :)00:27
dmsimardcontainers ? I was promised that containers would fix all my problems00:27
*** d0ugal has joined #openstack-infra00:27
*** AJaeger has joined #openstack-infra00:27
ianwcontainers seem like they will be an almost infinite source of side-channel attacks imo00:29
*** masber has quit IRC00:29
*** sree has quit IRC00:30
*** pcichy has joined #openstack-infra00:34
*** ilpianista_ has joined #openstack-infra00:35
*** aspiers[m] has joined #openstack-infra00:35
*** xarses_ has joined #openstack-infra00:39
*** Apoorva has quit IRC00:40
*** tosky has quit IRC00:41
*** sree has joined #openstack-infra00:42
*** xarses_ has quit IRC00:49
*** sree has quit IRC00:51
*** sree has joined #openstack-infra00:56
*** dave-mccowan has joined #openstack-infra01:07
*** masber has joined #openstack-infra01:10
*** sshnaidm has quit IRC01:11
*** sshnaidm has joined #openstack-infra01:12
*** sree has quit IRC01:13
*** liusheng has joined #openstack-infra01:19
*** daidv has joined #openstack-infra01:20
*** daidv_ has joined #openstack-infra01:20
*** edmondsw has joined #openstack-infra01:21
*** liujiong has joined #openstack-infra01:22
*** daidv_ has quit IRC01:24
*** edmondsw has quit IRC01:26
*** sree has joined #openstack-infra01:33
*** kiennt26 has joined #openstack-infra01:36
*** sree has quit IRC01:37
*** leakypipes has quit IRC01:39
*** sshnaidm has quit IRC01:39
*** sshnaidm has joined #openstack-infra01:40
*** cuongnv has joined #openstack-infra01:45
*** annp has joined #openstack-infra01:54
*** hongbin has joined #openstack-infra02:03
*** openStackUser has joined #openstack-infra02:24
*** liusheng has quit IRC02:25
*** liusheng has joined #openstack-infra02:26
openStackUsermsg nickserv register Passcode1 mshankar4142@gmail.com02:30
*** zhurong has joined #openstack-infra02:46
*** openStackUser has quit IRC03:01
*** liujiong has quit IRC03:03
*** sree has joined #openstack-infra03:07
*** hongbin has quit IRC03:09
*** dave-mccowan has quit IRC03:09
*** hongbin has joined #openstack-infra03:09
*** edmondsw has joined #openstack-infra03:09
*** hongbin has quit IRC03:10
*** hongbin has joined #openstack-infra03:10
*** hongbin has quit IRC03:10
*** hongbin has joined #openstack-infra03:11
*** hongbin has quit IRC03:12
*** hongbin has joined #openstack-infra03:13
*** edmondsw has quit IRC03:14
*** hongbin has quit IRC03:14
*** hongbin has joined #openstack-infra03:15
*** kong has quit IRC03:17
*** kong has joined #openstack-infra03:17
*** liujiong has joined #openstack-infra03:36
*** ramishra has joined #openstack-infra03:44
*** ddurst has quit IRC03:46
*** yamamoto has joined #openstack-infra03:58
*** yamamoto has quit IRC04:03
*** ddurst has joined #openstack-infra04:11
*** dhajare has joined #openstack-infra04:14
*** hongbin has quit IRC04:19
*** sflanigan has joined #openstack-infra04:27
*** sflanigan has joined #openstack-infra04:27
*** aeng has quit IRC04:32
*** bhavik1 has joined #openstack-infra04:33
*** gcb has joined #openstack-infra04:41
*** dhajare has quit IRC04:46
*** aeng has joined #openstack-infra04:47
*** bhavik1 has quit IRC04:50
*** zhurong has quit IRC04:52
*** udesale has joined #openstack-infra04:54
*** edmondsw has joined #openstack-infra04:58
*** edmondsw has quit IRC05:02
*** yamamoto has joined #openstack-infra05:04
*** openStackUser has joined #openstack-infra05:05
*** sflanigan has quit IRC05:07
*** liujiong has quit IRC05:08
*** yamamoto has quit IRC05:12
*** pcichy has quit IRC05:24
*** armaan has joined #openstack-infra05:26
*** janki has joined #openstack-infra05:28
*** mikal has quit IRC05:33
*** psachin has joined #openstack-infra05:33
openstackgerritGoutham Pratapa proposed openstack-infra/project-config master: Add Templates to Kingbird-Dashboard.  https://review.openstack.org/53045205:38
*** dsariel has joined #openstack-infra05:39
*** dsariel has quit IRC05:44
*** zhurong has joined #openstack-infra05:52
*** pgadiya has joined #openstack-infra05:53
*** liujiong has joined #openstack-infra05:55
AJaegeropenStackUser: hope you changed your password...06:01
chandankumarAJaeger: Good morning06:04
chandankumarAJaeger: is the publish-to-pypi jobs fixed?06:04
openstackgerritChandan Kumar proposed openstack-infra/project-config master: Use tempest-plugin-jobs project template for all tempest plugins  https://review.openstack.org/53133906:10
AJaegerchandankumar: we haven't discussed that yet, sorry06:14
*** liusheng has quit IRC06:14
chandankumarAJaeger: some projects need tempest plugins on pypi, will i send a seperate patch for them?06:15
chandankumarcongress requires telemetry and mistral tempest plugin06:15
AJaegerchandankumar: put it on our agenda at https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting - for tomorrow's IRC meeting06:17
*** janki has quit IRC06:17
chandankumarAJaeger: sure :-)06:17
AJaegerchandankumar: yes, splitting those up might be best06:17
AJaegerchandankumar: I meant to say : I *just* put it there...06:17
*** janki has joined #openstack-infra06:18
*** aeng has quit IRC06:18
*** openStackUser has quit IRC06:21
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Don't treat finger client disconnect as exception  https://review.openstack.org/53140806:24
openstackgerritIan Wienand proposed openstack/diskimage-builder master: [DNM] Support networkx 2.0  https://review.openstack.org/50652406:30
*** khappone has joined #openstack-infra06:35
openstackgerritIan Wienand proposed openstack/diskimage-builder master: [DNM] Support networkx 2.0  https://review.openstack.org/50652406:36
*** florianf has joined #openstack-infra06:39
*** dsariel has joined #openstack-infra06:41
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Share a fake pull request database across connections  https://review.openstack.org/53150606:41
*** claudiub has joined #openstack-infra06:43
*** udesale__ has joined #openstack-infra06:45
*** edmondsw has joined #openstack-infra06:46
*** jbadiapa has joined #openstack-infra06:47
*** udesale has quit IRC06:48
*** edmondsw has quit IRC06:50
*** coolsvap has joined #openstack-infra06:51
*** udesale has joined #openstack-infra06:52
*** udesale__ has quit IRC06:54
*** dhajare has joined #openstack-infra06:56
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove the default argument to secure in nodepoolcmd  https://review.openstack.org/48031006:58
*** kjackal has joined #openstack-infra07:00
*** pcaruana has joined #openstack-infra07:04
*** mat128 has quit IRC07:09
*** Kevin_Zheng has quit IRC07:13
*** Shrews has quit IRC07:13
*** knikolla has quit IRC07:13
*** mgkwill has quit IRC07:13
*** jungleboyj has quit IRC07:13
*** knikolla has joined #openstack-infra07:13
*** mgkwill has joined #openstack-infra07:13
*** jungleboyj has joined #openstack-infra07:13
*** Shrews has joined #openstack-infra07:14
*** gaurangt has quit IRC07:15
*** Krenair has quit IRC07:15
*** Kevin_Zheng has joined #openstack-infra07:16
*** gaurangt has joined #openstack-infra07:18
*** Krenair has joined #openstack-infra07:22
*** liusheng has joined #openstack-infra07:22
*** slaweq has joined #openstack-infra07:30
*** makowals has joined #openstack-infra07:36
*** armaan_ has joined #openstack-infra07:36
*** armaan has quit IRC07:37
*** dsariel has quit IRC07:49
openstackgerritChandan Kumar proposed openstack-infra/project-config master: Use tempest plugin jobs and pypi jobs for Mistral tempest plugin  https://review.openstack.org/53167607:54
openstackgerritChandan Kumar proposed openstack-infra/project-config master: tempest plugin and pypi jobs for Mistral tempest plugin  https://review.openstack.org/53167607:57
openstackgerritChandan Kumar proposed openstack-infra/project-config master: tempest plugin and pypi jobs for Telemetry tempest plugin  https://review.openstack.org/53167808:00
*** eumel8 has joined #openstack-infra08:03
*** armaan_ has quit IRC08:03
*** eumel8 has quit IRC08:08
*** tesseract has joined #openstack-infra08:09
*** ralonsoh has joined #openstack-infra08:09
*** namnh has joined #openstack-infra08:09
*** jtomasek has joined #openstack-infra08:12
*** shardy has joined #openstack-infra08:18
*** pabelanger has quit IRC08:19
*** weshay has quit IRC08:19
*** aviau has quit IRC08:19
*** lucas-afk has quit IRC08:19
*** rook has quit IRC08:19
*** aviau has joined #openstack-infra08:19
*** honza has quit IRC08:20
*** honza has joined #openstack-infra08:20
*** pabelanger has joined #openstack-infra08:20
*** weshay has joined #openstack-infra08:20
*** lucasagomes has joined #openstack-infra08:20
*** honza is now known as Guest1450008:20
*** rook has joined #openstack-infra08:21
*** armaan has joined #openstack-infra08:21
*** rook is now known as Guest9276108:21
*** eumel8 has joined #openstack-infra08:30
*** edmondsw has joined #openstack-infra08:34
*** hashar has joined #openstack-infra08:36
*** jpena has joined #openstack-infra08:38
*** edmondsw has quit IRC08:39
*** gibi_away is now known as gibi08:44
*** nmagnezi has joined #openstack-infra08:45
*** dalvarez has joined #openstack-infra08:47
*** rossella_s has joined #openstack-infra08:53
openstackgerritMerged openstack/ptgbot master: Remove ethercalc support  https://review.openstack.org/52516709:00
*** jascott1 has quit IRC09:02
openstackgerritMerged openstack/ptgbot master: Rooms are now called Tracks  https://review.openstack.org/52516909:04
openstackgerritMerged openstack/ptgbot master: Specify and load event schedule  https://review.openstack.org/52516809:04
openstackgerritMerged openstack/ptgbot master: Add scheduled / additional rooms  https://review.openstack.org/52934509:04
openstackgerritMerged openstack/ptgbot master: Display scheduled and additional rooms in web page  https://review.openstack.org/52934609:04
openstackgerritMerged openstack/ptgbot master: Add ability to book a room  https://review.openstack.org/52958709:04
openstackgerritMerged openstack/ptgbot master: Select current day tab by default  https://review.openstack.org/52958909:04
openstackgerritMerged openstack/ptgbot master: Update location automatically  https://review.openstack.org/52983809:04
openstackgerritMerged openstack/ptgbot master: Add command to clean up at start of day  https://review.openstack.org/52984209:04
openstackgerritMerged openstack/ptgbot master: Reject some commands if a track is not scheduled  https://review.openstack.org/52984709:04
openstackgerritMerged openstack/ptgbot master: Also find room for tracks in additional rooms  https://review.openstack.org/52984809:04
openstackgerritMerged openstack/ptgbot master: Rewrite documentation in more user-friendly way  https://review.openstack.org/52985309:04
*** armaan_ has joined #openstack-infra09:06
*** dsariel has joined #openstack-infra09:07
*** sshnaidm is now known as sshnaidm|afk09:07
*** rcernin has quit IRC09:07
*** sshnaidm|afk has quit IRC09:08
*** jpich has joined #openstack-infra09:08
*** sshnaidm has joined #openstack-infra09:08
*** armaan has quit IRC09:09
*** armaan_ has quit IRC09:10
*** armaan has joined #openstack-infra09:10
*** sbezverk has quit IRC09:11
*** Guest14500 is now known as honza09:14
*** dbecker has joined #openstack-infra09:15
*** dbecker has quit IRC09:15
*** owalsh_ is now known as owalsh09:15
*** dbecker has joined #openstack-infra09:16
*** finucannot is now known as stephenfin09:16
*** Hal has joined #openstack-infra09:18
*** Hal has quit IRC09:18
*** zoli has quit IRC09:21
*** zoli has joined #openstack-infra09:22
*** danpawlik has joined #openstack-infra09:23
*** shardy has quit IRC09:27
*** armaan has quit IRC09:28
*** armaan has joined #openstack-infra09:29
*** nmagnezi has quit IRC09:30
*** shardy has joined #openstack-infra09:32
*** efoley has joined #openstack-infra09:32
*** e0ne has joined #openstack-infra09:33
AJaegerinfra-root, kingbird-dashboard new repo creation was merged yesterday but the repo is not fully created, see http://git.openstack.org/cgit/openstack/kingbird-dashboard/ .09:36
*** pcichy has joined #openstack-infra09:38
AJaegerinfra-root, I cannot reach http://zuulv3.openstack.org/ and cacti shows that zuulv3 uses 6+ GB swap09:40
*** liujiong has quit IRC09:43
*** liujiong has joined #openstack-infra09:43
*** udesale has quit IRC09:45
*** udesale has joined #openstack-infra09:46
*** derekh has joined #openstack-infra09:46
*** e0ne has quit IRC09:47
*** erlon has joined #openstack-infra09:54
openstackgerritMatthieu Huin proposed openstack-infra/nodepool feature/zuulv3: Add a separate module for node management commands  https://review.openstack.org/53170309:58
*** rossella_s has quit IRC09:59
*** armaan has quit IRC09:59
*** rossella_s has joined #openstack-infra09:59
*** sree has quit IRC10:02
*** gcb has quit IRC10:02
*** zhurong has quit IRC10:02
*** jascott1 has joined #openstack-infra10:03
*** tosky has joined #openstack-infra10:04
*** armaan has joined #openstack-infra10:05
*** kiennt26 has quit IRC10:07
*** liujiong has quit IRC10:07
*** tinwood_ is now known as tinwood10:10
*** pbourke has quit IRC10:12
*** pbourke has joined #openstack-infra10:12
fricklerAJaeger: ack, seem to be a bit better currently, but I'll prepared for a restart anyway. experience seems to be that this doesn't last for long10:14
*** namnh has quit IRC10:18
*** jklare has quit IRC10:19
*** pcichy has quit IRC10:19
*** pcichy has joined #openstack-infra10:20
*** jklare has joined #openstack-infra10:20
*** edmondsw has joined #openstack-infra10:22
fricklerinfra-root: I restarted zuul-(scheduler|web), but restoring the queues fails with traceback http://paste.openstack.org/show/640784/10:23
frickler#status notice zuul has been restarted, all queues have been reset. please recheck your patches when appropriate10:24
openstackstatusfrickler: sending notice10:24
-openstackstatus- NOTICE: zuul has been restarted, all queues have been reset. please recheck your patches when appropriate10:25
fricklerhttps://storyboard.openstack.org/#!/story/200144810:26
openstackstatusfrickler: finished sending notice10:27
*** edmondsw has quit IRC10:27
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Set remote url on every getRepo in merger  https://review.openstack.org/52929310:29
*** cuongnv has quit IRC10:30
fricklerianw: happy new year to you, too. if you are still looking to fill up your empty swap space, AJaeger has collected a nice list of reviews https://etherpad.openstack.org/p/Nvt3ovbn5x :)10:31
*** annp has quit IRC10:32
*** udesale has quit IRC10:34
openstackgerritliusheng proposed openstack-infra/zuul feature/zuulv3: Use hotlink instead log url in github job report  https://review.openstack.org/53154510:34
*** udesale has joined #openstack-infra10:35
frickleroh, that traceback happens when one doesn't have permission to read the zuul.conf file, pretty bad error handling I say. :( queues restored now10:35
*** gema has joined #openstack-infra10:39
gemaneed to add a new cloud to infra, can someone point me in the right direction as to how big the nodepool project needs to be and who to talk to ?10:40
*** ldnunes has joined #openstack-infra10:44
*** rossella_s has quit IRC10:46
*** rossella_s has joined #openstack-infra10:46
*** sambetts|afk is now known as sambetts10:50
*** simondodsley has quit IRC10:50
*** simondodsley has joined #openstack-infra10:51
*** jamespage has quit IRC10:51
*** Krinkle has quit IRC10:51
*** jamespage has joined #openstack-infra10:52
*** Krinkle has joined #openstack-infra10:52
*** ldnunes has quit IRC10:52
*** ldnunes has joined #openstack-infra10:54
*** udesale has quit IRC10:54
*** armaan has quit IRC10:55
*** electrofelix has joined #openstack-infra10:56
*** mat128 has joined #openstack-infra10:56
openstackgerritMatthieu Huin proposed openstack-infra/nodepool feature/zuulv3: [WIP] webapp: add optional admin endpoint  https://review.openstack.org/53171811:00
*** wolverineav has joined #openstack-infra11:00
openstackgerritMatthieu Huin proposed openstack-infra/nodepool feature/zuulv3: Refactor status functions, add web endpoints, allow params  https://review.openstack.org/53139011:02
*** armaan has joined #openstack-infra11:02
*** numans has quit IRC11:06
*** numans has joined #openstack-infra11:08
*** rfolco has joined #openstack-infra11:21
openstackgerritShachar Snapiri proposed openstack-infra/system-config master: Add openstack-dragonflow channel to statusbot  https://review.openstack.org/53172011:23
snapiriHi Infra, could anyone please help review  ^^^11:23
*** Guest92761 is now known as rook11:27
*** rcarrill1 has joined #openstack-infra11:32
*** rcarrillocruz has quit IRC11:35
*** zhurong has joined #openstack-infra11:35
openstackgerritStephen Finucane proposed openstack-dev/pbr master: doc: Rework features doc  https://review.openstack.org/51224811:39
openstackgerritStephen Finucane proposed openstack-dev/pbr master: doc: Minor rework of usage doc  https://review.openstack.org/51224911:39
*** smatzek has joined #openstack-infra11:40
*** smatzek has quit IRC11:40
*** smatzek has joined #openstack-infra11:40
*** jkilpatr has quit IRC11:50
*** ldnunes has quit IRC11:53
*** ldnunes has joined #openstack-infra11:55
*** jistr is now known as jistr|mtg11:58
*** lucasagomes is now known as lucas-hungry12:00
*** sdague has joined #openstack-infra12:00
*** zhongjun has quit IRC12:06
*** dave-mccowan has joined #openstack-infra12:09
*** edmondsw has joined #openstack-infra12:10
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Add roles for static web content build and publication  https://review.openstack.org/53140612:11
*** gcb has joined #openstack-infra12:13
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Add roles for static web content build and publication  https://review.openstack.org/53140612:14
*** edmondsw has quit IRC12:15
*** udesale has joined #openstack-infra12:16
*** rhallisey has joined #openstack-infra12:17
*** jkilpatr has joined #openstack-infra12:22
*** janki has quit IRC12:24
*** rcarrill1 is now known as rcarrillocruz12:24
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Add roles for static web content build and publication  https://review.openstack.org/53140612:26
*** jpena is now known as jpena|lunch12:33
*** sree has joined #openstack-infra12:36
*** sree has quit IRC12:41
openstackgerritFrank Kloeker proposed openstack-infra/system-config master: Upgrade translate-dev.o.o to Zanata 4.3.3  https://review.openstack.org/53173612:45
eumel8clarkb, ianw: ^^ the patch for Zanata 4.3.312:46
*** ldnunes has quit IRC12:47
*** ldnunes has joined #openstack-infra12:47
*** dave-mccowan has quit IRC12:47
*** armaan has quit IRC12:48
*** armaan has joined #openstack-infra12:49
*** dave-mccowan has joined #openstack-infra12:49
*** armaan has quit IRC12:49
*** armaan has joined #openstack-infra12:50
*** rosmaita has joined #openstack-infra12:54
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Also prefix the indexes if needed  https://review.openstack.org/53174212:55
*** rcernin has joined #openstack-infra12:59
*** TLAXKIT has joined #openstack-infra13:01
*** zhurong has quit IRC13:01
*** dhajare has quit IRC13:04
*** lucas-hungry is now known as lucasagomes13:05
*** kjackal has quit IRC13:13
*** sree has joined #openstack-infra13:13
*** sshnaidm has quit IRC13:14
*** kjackal has joined #openstack-infra13:14
*** sshnaidm has joined #openstack-infra13:15
*** kjackal has quit IRC13:15
*** rcernin has quit IRC13:16
openstackgerritMerged openstack-infra/storyboard master: Pin version of webob to 1.7.4  https://review.openstack.org/53150713:24
*** kjackal has joined #openstack-infra13:24
*** pcaruana has quit IRC13:25
*** pcaruana has joined #openstack-infra13:25
*** yamamoto has joined #openstack-infra13:28
*** jpena|lunch is now known as jpena13:31
*** jkilpatr has quit IRC13:31
*** jistr|mtg is now known as jistr13:35
*** coolsvap has quit IRC13:36
*** rlandy has joined #openstack-infra13:38
*** sree has quit IRC13:41
*** sree has joined #openstack-infra13:41
*** jkilpatr has joined #openstack-infra13:45
*** kgiusti has joined #openstack-infra13:46
*** sree has quit IRC13:46
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Add roles for static web content build and publication  https://review.openstack.org/53140613:48
*** edmondsw has joined #openstack-infra13:51
*** dprince has joined #openstack-infra13:51
*** kiennt26 has joined #openstack-infra13:53
*** katkapilatova1 has joined #openstack-infra13:54
openstackgerritMerged openstack-dev/pbr master: Support PEP 345 Project-URL metadata  https://review.openstack.org/52168913:54
*** jaypipes has joined #openstack-infra13:55
*** yamamoto has quit IRC13:56
*** yamamoto has joined #openstack-infra13:57
*** yamamoto has quit IRC14:01
*** esberglu has joined #openstack-infra14:03
dmsimardfrickler: I created a few stories recently around zuul operations (and logging)14:08
dmsimardlike https://storyboard.openstack.org/#!/story/2001445 and https://storyboard.openstack.org/#!/story/200144614:09
dmsimardso please document your experience as well so we can improve that14:09
openstackgerritDoug Hellmann proposed openstack-infra/project-config master: switch whereto doc job to python3  https://review.openstack.org/53176614:11
dmsimardI just updated https://storyboard.openstack.org/#!/story/2001445 with two other use cases14:13
*** mriedem has joined #openstack-infra14:14
*** esberglu has quit IRC14:17
*** esberglu has joined #openstack-infra14:17
*** smatzek has quit IRC14:21
fungigema: we'd probably want to know some more about your goals for donating resources to our pool, but the basic details are at https://docs.openstack.org/infra/system-config/contribute-cloud.html14:21
*** Goneri has joined #openstack-infra14:21
fungigema: from your linaro cloak, i'm guessing this is revisiting the earlier arm64 cloud discussions?14:22
mordredfungi: extrapolating from the irc nick cloak, I'm guessing maybe ARM?14:22
mordredfungi: jinx14:22
*** esberglu has quit IRC14:22
fungiif so, adding a new (second) architecture is going to be a lot more involved than what we have listed on that page14:22
mordredfungi: yah. having a second architecture will, I'm *sure*, flush out a few assumptions14:23
*** eharney has joined #openstack-infra14:24
*** dhill_ has joined #openstack-infra14:25
fungigema: and now i see your e-mail to me. will follow up once i'm more awake and caught up14:27
*** makowals has quit IRC14:27
*** makowals has joined #openstack-infra14:29
*** esberglu has joined #openstack-infra14:32
gemafungi: ack, thanks :)14:32
*** esberglu_ has joined #openstack-infra14:33
*** esberglu_ is now known as esberglu__14:34
*** e0ne has joined #openstack-infra14:37
*** esberglu has quit IRC14:37
*** armaan_ has joined #openstack-infra14:38
*** armaan has quit IRC14:38
*** armaan_ has quit IRC14:38
*** armaan has joined #openstack-infra14:39
*** makowals has quit IRC14:39
*** makowals has joined #openstack-infra14:39
*** yamamoto has joined #openstack-infra14:42
*** psachin has quit IRC14:45
*** yamamoto has quit IRC14:47
openstackgerritMerged openstack-dev/cookiecutter master: Switch to use stestr in README  https://review.openstack.org/53000114:48
openstackgerritMonty Taylor proposed openstack-infra/infra-manual master: Add some information about OpenStack IRC usage  https://review.openstack.org/53100014:49
mordreddmsimard: ^^ fixed from your comments14:49
dmsimard+214:50
openstackgerritFrank Kloeker proposed openstack-infra/puppet-zanata master: [WiP] Change Zanata install medium to war files  https://review.openstack.org/53180914:54
*** esberglu__ is now known as esberglu14:54
snapiriHi, any chance anyone could review: openstack-infra/system-config master: Add openstack-dragonflow channel to statusbot  https://review.openstack.org/531720 ?14:56
*** yamahata has joined #openstack-infra14:56
dmsimardsnapiri: are you looking for gerrit notifications ? or status updates (such as zuul restarts) ?14:56
openstackgerritFabien Boucher proposed openstack-infra/zuul feature/zuulv3: Make Zuul able to start with a broken config  https://review.openstack.org/52906014:56
*** afred312 has quit IRC14:57
*** afred312 has joined #openstack-infra14:57
snapiridmisimard: the latter please14:58
*** armaan has quit IRC14:59
snapiriwe have the first already14:59
dmsimardokay15:00
dmsimardsnapiri: +2, was just asking to make sure you were doing the right thing :)15:00
openstackgerritMonty Taylor proposed openstack-infra/infra-manual master: Fix yaml snippet for sphinx for python3  https://review.openstack.org/53181115:00
*** hongbin has joined #openstack-infra15:01
*** Guest8485 is now known as dansmith15:02
dmsimardIt's a shame that codesearch (hound) is largely unmaintained, there's a feature that would really be useful but there's no one to do it (and merge it) :/15:02
snapiridmsimard: Thanks!15:02
*** dansmith is now known as Guest6250115:02
dmsimardI tried pinging one of the authors on twitter a few weeks/months back but nothing came of it (although he did reply)15:03
fungihard to find stackers who want to hack on go projects, but maybe we could put out a call for help on hound's behalf?15:03
*** sdague has quit IRC15:04
fungitaron was looking at getting the online config reloading implemented, but their internship ran out before that part got tackled15:04
dmsimardfungi: the upstream is largely unresponsive :(15:04
dmsimardthe authors don't work at etsy anymore15:04
*** Guest62501 is now known as dansmith15:05
*** pgadiya has quit IRC15:07
*** sbezverk has joined #openstack-infra15:09
*** rlandy_ has joined #openstack-infra15:09
*** rkukura has quit IRC15:10
*** rkukura has joined #openstack-infra15:11
*** gouthamr has joined #openstack-infra15:11
*** smatzek has joined #openstack-infra15:15
*** katkapilatova1 has quit IRC15:15
*** smatzek has quit IRC15:15
*** smatzek has joined #openstack-infra15:15
*** smatzek has quit IRC15:15
*** felipemonteiro has joined #openstack-infra15:15
dmsimardWe'd like to use it for RDO, but the problem is actually a bit silly -- hound only indexes the master branch and some of our repos don't have a master branch so the branch would need to be configurable somehow. There's been a few issues/PRs around that topic but none that quite does that (and work)15:16
*** smatzek has joined #openstack-infra15:16
dmsimardI also trick hound into indexing locally cloned git repos instead of querying github15:16
*** Apoorva has joined #openstack-infra15:17
smcginnisNot really an infra questions, but I figure someone here probably knows. I haven't seen a BoD ballot in the email I would expect it in, the email it possibly could have been sent to, nor the email it shouldn't go to. Have those all been sent out?15:17
Adri2000hello15:19
dmsimardsmcginnis: I got my ballot email sometime this weekend15:20
Adri2000who should I get in touch with regarding a sudden increase of spam received on the -owner@ alias of an openstack.org mailing-list?15:20
dmsimardAdri2000: there's been a few patches to address that recently, what email is it ?15:20
Adri2000(like almost 100 - similar - spam per hour)15:20
Adri2000openstack-fr-owner@15:20
dmsimardAdri2000: for example http://git.openstack.org/cgit/openstack-infra/system-config/commit/?id=19037f2cbd2c554692160817a5aa9a05eeadfe0715:21
dmsimardAdri2000: if you send a patch to system-config along those lines, we can merge it quickly15:21
*** makowals has quit IRC15:22
Adri2000dmsimard: perfect, that should solve the problem indeed, will prepare a patch shortly15:22
*** makowals has joined #openstack-infra15:22
*** pcichy has quit IRC15:24
AJaegerinfra-root, kingbird-dashboard new repo creation was merged yesterday but the repo is not fully created, see http://git.openstack.org/cgit/openstack/kingbird-dashboard/ - could somebody check and fix, please?15:26
dmsimardAJaeger: It's missing the gitreview I guess ?15:26
AJaegerdmsimard: and github mirroring. not sure what else15:27
dmsimardhmm it's not even replicated to github or gerrit15:27
*** yamamoto has joined #openstack-infra15:27
dmsimardI can't look *right now*, but iirc that patch landed after fixing the zuul issues from yesterday so it might be related15:28
*** katkapilatova1 has joined #openstack-infra15:28
*** e0ne has quit IRC15:28
fungiit's not even created in gerrit yet: https://review.openstack.org/#/admin/projects/openstack/kingbird-dashboard15:28
AJaegermordred: did you see my patch to your change https://review.openstack.org/#/c/531430/ - is that fine?15:29
chandankumardmsimard: AJaeger please have a look at these two reviews https://review.openstack.org/#/c/531678/ and https://review.openstack.org/#/c/531676/15:29
*** eharney has quit IRC15:29
openstackgerritAdrien Cunin proposed openstack-infra/system-config master: Treat mail sent to openstack-fr-owner as spam  https://review.openstack.org/53182015:30
Adri2000dmsimard: ^15:30
*** SamYaple_ has quit IRC15:30
*** SamYaple has joined #openstack-infra15:30
dmsimardAdri2000: thanks +215:30
AJaegerchandankumar: I'm not reviewing right now new pypi additions until I know what to require15:30
AJaegerchandankumar: let's wait until we discussed that in our meeting tomorrow, please15:30
*** ramishra has quit IRC15:31
chandankumarAJaeger: sure, keeping on hold15:31
*** yamamoto has quit IRC15:32
openstackgerritMatthieu Huin proposed openstack-infra/nodepool feature/zuulv3: [WIP] webapp: add optional admin endpoint  https://review.openstack.org/53171815:33
mordredAJaeger: +2 thanks15:34
*** caphrim007_ has quit IRC15:34
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Publish neutron and horizon to pypi  https://review.openstack.org/53182215:34
*** caphrim007 has joined #openstack-infra15:35
mordredttx, smcginnis, dhellmann, mnaser: ^^ straw-man to get movement on that topic at least for neutron and horizon15:35
AJaegerconfig-core, I have written Zuul v3 native jobs for bindep and would love a review on https://review.openstack.org/53147015:35
smcginnismordred: Great, I'll take a look shortly.15:35
snapiridmsimard: sorry for the rudeness, anyone else who can review openstack-infra/system-config master: Add openstack-dragonflow channel to statusbot  https://review.openstack.org/531720 ?15:35
dmsimardsnapiri: someone will get to it eventually, it's still early where a lot of the core reviewers live15:36
snapirithanks :)15:36
openstackgerritMerged openstack-infra/infra-manual master: Update tox env to match zuul PTI  https://review.openstack.org/53099915:38
openstackgerritMerged openstack-infra/infra-manual master: Add some information about OpenStack IRC usage  https://review.openstack.org/53100015:38
openstackgerritMerged openstack-infra/infra-manual master: Fix yaml snippet for sphinx for python3  https://review.openstack.org/53181115:38
*** caphrim007 has quit IRC15:39
*** makowals has quit IRC15:40
dmsimardsnapiri: alternatively, all notices are also posted here: https://twitter.com/openstackinfra and here: https://wiki.openstack.org/wiki/Infrastructure_Status15:41
openstackgerritAndreas Jaeger proposed openstack-infra/project-config master: Add zuul_work_dir defaults to base-test  https://review.openstack.org/53143115:42
*** bobh has joined #openstack-infra15:42
openstackgerritAndreas Jaeger proposed openstack-infra/project-config master: Set defaults for zuul_work_dir and bindep_dir  https://review.openstack.org/53143215:42
*** armaan has joined #openstack-infra15:43
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Publish bifrost to PyPI  https://review.openstack.org/53182415:43
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Publish everything but keystone to PyPI  https://review.openstack.org/53182515:43
openstackgerritMonty Taylor proposed openstack-infra/project-config master: DNM Release keystone to PyPI  https://review.openstack.org/53182615:43
AJaegermordred: pypi has changed the way projects are registered and https://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases is not accurate anymore.15:44
*** nicolasbock has joined #openstack-infra15:45
snapiridmsimard: thanks! this is eye-opening...15:45
AJaegerI put this on the agenda for tomorrow - but currently do not approve new pypi publish jobs since I do not know how to reserve the names15:45
fungidid something change with our our puppeting of servers on friday? or late thursday? last puppet run on review.openstack.org was 23:33 on january 415:45
fungiand it's not in the emergency file15:46
dhellmannAJaeger : I think someone needs to run "setup.py register" and then adjust the resulting project's permissions15:46
dhellmannAJaeger : oh, maybe you have to actually upload a release by hand once15:47
fungidhellmann: i _think_ twine is supposed to do that automagically if you're uploading a not-yet-existent project15:47
fungiand that setup.py register is deprecated now15:47
dhellmannfungi : yeah. It didn't used to, but I think you're right based on the instructions on pypi.python.org15:47
dhellmannI think the change is you can't register a name without actually uploading a package15:48
*** gcb has quit IRC15:48
fungiproblem with requiring someone to manually register the project now that doing so requires at least a stub of a package is that if we're reviewing for it we can't add new projects with pypi publication jobs, and have to wait for the pypi jobs to get added later15:48
fungiof course, the down-side to just relying on the first twine run to create the project from our release jobs (aside from the risk a squatter will grab it in the meantime) is that only our openstackci account will be an index owner15:49
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Publish everything but keystone to PyPI  https://review.openstack.org/53182515:50
openstackgerritMonty Taylor proposed openstack-infra/project-config master: DNM Release keystone to PyPI  https://review.openstack.org/53182615:50
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Remove release-openstack-python-without-pypi  https://review.openstack.org/53182915:50
openstackgerritMonty Taylor proposed openstack-infra/openstack-zuul-jobs master: Remove release-openstack-server template  https://review.openstack.org/53183015:50
mordredfungi, dhellmann, AJaeger: yah- so - I just did a twine upload of bifrost to get it registered, but I grabbed the 4.0.0 release from tarballs.o.o ...15:51
dhellmannfungi : we could build a little tool for creating a mostly empty sdist for a given name and publish 0.0.0 releases15:52
fungimordred: thanks for confirming it works as described15:52
mordredin the past, to work around register not being a thing anymore, I've just done a 'python setup.py sdist upload' on a random commit in  a project, then have gone and deleted the release15:52
mordreddhellmann: ++15:52
mordreddhellmann: I was just thinking that same thing15:52
dhellmannoh, that sounds like a good process, too15:52
dhellmannalthough it has the problem fungi pointed out15:52
*** ram5391 has joined #openstack-infra15:52
fungidhellmann: we could, but i think that likely flies in the face of the reasons pypi has started requiring you to register by uploading a package, and wouldn't want to look like we're producing a reusable tool to skirt that15:52
*** yamamoto has joined #openstack-infra15:53
*** yamamoto has quit IRC15:53
fungibasically, i wouldn't want one of our release tools to become the thing that package name squatters use to mass register pypi projects15:53
mordredfungi: ++15:54
dhellmannsure15:54
mordredfungi: we have things that are only owned by openstackci already15:54
dhellmannperhaps it's not a tool a person runs.15:54
fungibut yeah, perhaps we should encourage projects to "release early (and often)" by tagging a release as soon as the packaging boilerplate is merged15:54
mordredmaybe we just let the release process be the thing15:54
mordredfungi: ++15:54
*** kiennt26 has quit IRC15:54
mordredfungi: we publish alphas and betas now, right?15:54
*** felipemonteiro has quit IRC15:54
fungiyeah, tag 0.0.0.0a115:55
mordreda person could just tag an 0.0.0a115:55
mordredjinx15:55
dhellmanndo we support uploading those?15:55
*** felipemonteiro has joined #openstack-infra15:55
fungiwe do15:55
mordredwe do - pip ignores them by default15:55
dhellmannok, I thought we set the job to only run for full releases15:55
fungiwe used to only upload wheels for prerelease tag strings, to work around (now very old) pip releases which didn't know how to distinguish pep 440 prereleases from releases15:56
mordredyou have to explicitly opt-in to a pre-release version number in a pip requirement for it to find it15:56
*** katkapilatova1 has quit IRC15:56
mordreddhellmann, fungi: double-checked - publish-to-pypi does upload pre-releases15:56
dhellmannok, cool15:56
fungias of a while ago (maybe the past year?) we switched to just do both wheels and sdists for prereleases too15:56
dhellmannso yeah, an alpha release is a way to go15:56
mordredthat said - the release team are the ones who have tagging acls these days15:56
fungimordred: also, to be clear, it would be 0.0.0.0a1 not 0.0.0a1 (pbr would attempt to normalize the latter to the former and then our upload job wouldn't find the corresponding artifacts)15:57
mordredwe maybe we need to have a job that runs when a new project is added to $something that submits the 0.0.0a1 tag?15:57
dhellmannthe releases repo validation stuff may have to change to support the very first release of a library being an alpha, because we don't allow pre-release versioning for all deliverable types right now15:57
*** SamYaple has quit IRC15:57
*** slaweq has quit IRC15:57
dhellmannsmcginnis : ^^15:57
*** SamYaple has joined #openstack-infra15:57
dhellmannmordred : proposing the tag needs to be manual because we have to wait for the repo to contain enough stuff to actually be packagable15:58
mordreddhellmann: ah. good point15:58
*** slaweq has joined #openstack-infra15:58
*** SamYaple has quit IRC15:58
*** SamYaple has joined #openstack-infra15:58
mordreddhellmann: does the release team have permissions to propose tags by hand?15:58
fungimordred: the catch-22 is that projects might add the pypi jobs before they've nailed down successful sdist/wheel generation15:58
*** e0ne has joined #openstack-infra15:58
dhellmannso, create the repo in project-config, populate it the normal way, propose a release as early as possible to reserve the name15:58
dhellmannuse an alpha version if that release is not actually consumable15:59
mordreddhellmann: ++15:59
fungimordred: they do, last i checked, yes15:59
*** xarses_ has joined #openstack-infra15:59
fungimordred: the way the release tooling works is it uses a gerrit account in the release managers group, which is how it gets sufficient permissions to push tags15:59
fungiso actual human release managers can in theory run the same commands16:00
mordredfungi, dhellmann: making an infra-manual patch with the above in it16:01
AJaegermordred: could you document this on the creators page, please?16:02
*** slaweq has quit IRC16:02
*** ijw has joined #openstack-infra16:03
fungithat's where i assumed he would add it16:03
AJaegerfungi, mordred : sorry, didn't read everything when I wrote this - sorry in a meeting16:05
AJaegerchandankumar: see above discussion, did you reserve the entreis already on pypi for all the tempest plugins16:06
dmsimardzuul-merger doesn't appear to be running on the ze nodes again... but grafana is not reporting any anomalies in merger counts16:06
dmsimardwait, is merger supposed to be running on the executors ? I thought it was16:07
dmsimard10x ze + 8 zm, that's the 18 mergers we're supposed to have16:07
fungidmsimard: last i remember, yes16:09
dmsimardthere's nothing in /var/lib/zuul/git so.. I guess I'm confused16:09
dmsimardI was actually troubleshooting why there was no merger-logging.conf on the zuul-executors but the puppet zuul merger class doesn't seem applied to the zuul-executors so far as I can tell16:10
openstackgerritPaul Belanger proposed openstack-infra/system-config master: Remove centos-release-openstack-ocata  https://review.openstack.org/53183716:10
clarkbdmsimard: that is correct16:10
pabelangerianw: clarkb: okay, I think we can just remove centos RDO ocata repos now^. I don't believe we need anything from there for our git servers.16:11
dmsimardclarkb: what is correct ? :)16:11
clarkbdmsimard: that we don't apply merger config to the executors16:11
dmsimardclarkb: but they *are* mergers, right ?16:11
dmsimardI recall discussing with corvus that ze's relied on themselves for merging (or something to that effect)16:12
clarkbdmsimard: only because executors run an implied merger aiui16:12
fungithe executors were running local mergers at one point16:12
pabelangerzuul-executor will launch their own process for mergers16:12
fungiahh, that makes sense16:12
pabelangerthey don't need zuul-merger class16:12
clarkbdmsimard: its built in requirement of the executor so it handles that itself16:12
dmsimardoh, so the zuul-merger bits would be logged in the executor logfile ?16:12
clarkbdmsimard: yes16:12
pabelangeryup16:12
dmsimardok, that was confusing (hard monday this morning)16:13
dmsimardI didn't know executors ran an implied merger16:13
dmsimardwithout the actual zuul-merger process running16:13
fungiokay, so it looks like the centos upgrades late last week likely broke puppet, which is why it never gets around to running against review.o.o16:16
fungii'm digging into logs on the git servers now to confirm16:16
clarkbfungi: oh you know what I may not have accepted new ssh host key for git.o.o16:16
clarkbbut it shouldn't be part of the stuff that blocks review.o.o only git0*.openstack.org should be16:16
fungi2018-01-08 16:02:33,806 p=1490 u=root |  fatal: [git05.openstack.org]: FAILED! => {"changed": false, "failed": true, "msg": "/usr/bin/timeout -s 9 30m /usr/bin/puppet apply /opt/system-config/production/manifests/site.pp --logdest syslog --environment 'production' --no-noop --detailed-exitcodes failed with return code: 6", "rc": 6, "stderr": "", "stdout": "", "stdout_lines": []}16:16
fungiis what we see on the puppetmaster end16:17
AJaegerinfra-root, can I ask again for help in finishing creation of kingbird-dashboard? fungi noticed that puppet did not run on review.o.o since January 4th - so that might be the first thing to look at, please16:17
clarkbah ya hopefully syslog has more info16:17
dmsimardgit05 was the server that wasn't updating properly iirc16:17
clarkbdmsimard: ya it was16:17
fungiAJaeger: that's what i've been looking into for the past half hour16:17
AJaegerinfra-root, I see fungi is commenting already above16:17
pabelangerfungi: python-six looks to be the issue16:17
AJaegerfungi, thanks! Wasn't clear to me.16:17
fungipabelanger: yeah, trying to upgrade jeepyb16:18
fungiJan  7 08:32:23 git01 puppet-user[10116]: #011python-six is needed by (installed) libstoragemgmt-python-1.4.0-5.el7_4.noarch16:19
sshnaidmpabelanger, can we send our custom metrics from multinode jobs in tripleo to http://graphite.openstack.org/ ?16:19
fungipabelanger: guessing something changed with that package when we updated to latest centos point release?16:19
AJaegersmcginnis: please see my note on https://review.openstack.org/#/c/531440 - and review your backports to properly checkout the correct branch16:20
pabelangersshnaidm: not currently, the ports are firewalled.  I know we have talked about a graphite publisher before, but we likely need to discuss it again16:21
smcginnisAJaeger: Yep, I've been updating outstanding patches this morning and just getting to the ones that had already merged.16:21
pabelangerfungi: yah, I'm trying to see what is going on now myself16:21
AJaegersmcginnis: cool, thanks16:21
*** armax has joined #openstack-infra16:21
smcginnisAJaeger: Thanks for the heads up!16:21
fungipabelanger: i'll let you continue on that front. you're likely going to be faster than me at troubleshooting rpm installation issues16:21
dmsimardsshnaidm: graphite.o.o access is restricted by a firewall right now16:22
corvusfungi, clarkb, dmsimard: zuul executors have internal mergers.  it doesn't run as a second process, it just implements both functions.16:22
dmsimardcorvus: yeah, TIL, thanks16:22
sshnaidmpabelanger, yeah, you wanted us to use graphite.o.o for multinode jobs..16:22
pabelangerfungi: http://git.openstack.org/cgit/openstack-infra/puppet-jeepyb/tree/manifests/init.pp#n6016:22
pabelangerfungi: seems we are forcing an removal, but other library needs it now16:22
dmsimardsshnaidm: if there would be a way for jobs to send data to graphite.o.o, it would probably need to be a task running on the local executor at the end of a job or something like that -- not unlike how we send data to logstash and openstack-health16:23
dmsimardsshnaidm: would you like to come discuss that at tomorrow's openstack-infra meeting ?16:23
pabelangersshnaidm: right, I wanted to see how we can remove the private infrastructure tripleo was using.  If you want to add the topic to our weekly meeting tomorrow, we can start to go over the requirements16:23
sshnaidmdmsimard, I think clouds IP ranges are well known, why not to allow them in firewall?16:23
sshnaidmpabelanger, dmsimard ok, let's raise it in meeting16:24
dmsimardagenda is here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting16:24
*** e0ne has quit IRC16:24
pabelangerfungi: seems https://review.openstack.org/505785/ from mordred might have broken things after point release16:25
dmsimardneed a +3 to merge https://review.openstack.org/#/c/531820/ to reduce spam to one of our ML owners16:25
clarkbsshnaidm: because they aren't well known in every case and in many cases are reused by other tenants16:25
sshnaidmclarkb, hmm, I see..16:26
pabelangerlibstoragemgmt, anybody konw what that is for?16:27
*** krtaylor_ has joined #openstack-infra16:27
*** krtaylor has quit IRC16:27
*** felipemonteiro has quit IRC16:27
corvussshnaidm: see also http://specs.openstack.org/openstack/qa-specs/specs/devstack/counter-inspection.html  for some partially completed prior work on the subject16:27
sshnaidmclarkb, are zuul executors IP ranges not known too?16:27
dmsimardinfra-root: yesterday all zuul-executors and zuul-mergers stopped due to a msgpack issue (see status log), while I reinstalled msgpack==0.5.0, there's still an outlying msgpack-python package we probably need to clean up16:27
dmsimardsshnaidm: zuul executors IP are whitelisted on a node basis16:27
corvusdmsimard: why did they stop?16:28
clarkbcorvus: my hunch was that msgpack 0.5.0 release was initially bad (broken wheels maybe) but have not been able toconfirm that16:28
fungisshnaidm: i really don't think we have a good way to determine the possible ip allocations used by all our providers, and even if we did that would be a pain to keep on top of what with the current state of ipv4 fragmentation and resale markets16:29
*** ijw has quit IRC16:29
clarkbI can't find anywhere where pypi says I deleted this thing16:29
dmsimardcorvus: I'm not 100% positive on why they stopped, my understanding is that there was an update of several python packages (amongst which was msgpack) and msgpack did not install properly .. leading zuul-executor and zuul-merger to fail starting16:29
corvusclarkb: right, but we don't have any puppet mechanism to actually stop the process16:29
fungisshnaidm: but also, that would allow anyone in any of those clouds to pollute our stats if they wanted, rather than being limited just to jobs we run16:29
dmsimardcorvus: so it's probably not so much a stop than a failed restart (or reload) or something else16:29
corvusi understand why they didn't start -- i just don't understand why they stopped16:29
sshnaidmfungi, I see.. I thought it's something constant16:30
*** jamesmcarthur has joined #openstack-infra16:30
dmsimardcorvus: amongst the updated packages, there was zuul itself, github3 and a few others.. does that cause a reload/restart of some sort to load the new code ?16:30
*** udesale has quit IRC16:30
corvussshnaidm, fungi: the spec i linked you has suggestions to address that issue16:30
fungisshnaidm: i agree that having the executors emit stats is the way to go for this. we know their addresses and can whitelist them easily16:30
dmsimardcorvus: otherwise, the rename of the msgpack module (from msgpack-python to msgpack) probably confused python (pip was confused itself)16:31
corvusdmsimard: nope.  no component of zuul ever automatically starts or restarts.16:31
corvusor stops16:32
dmsimardpip thought both msgpack and msgpack-python were installed, it showed up in pip3 freeze but msgpack was not actually installed (only had distinfo folders in /usr/local/lib/python3.5)16:32
*** slaweq has joined #openstack-infra16:32
fungidmsimard: what was the approximate date/time when you noticed they weren't running?16:32
dmsimardfungi: it's super obvious looking at grafana16:32
dmsimardhttp://grafana.openstack.org/dashboard/db/zuul-status see yesterday16:33
*** jistr is now known as jistr|off|mtg16:33
dmsimarddead 19:00 UTC according to graphs16:33
openstackgerritPaul Belanger proposed openstack-infra/puppet-jeepyb master: Revert "Remove python-six on centos"  https://review.openstack.org/53185116:34
fungidmsimard: and this roughly corresponds with when the unattended-upgrades runs broke?16:34
dmsimardalso, there should probably be a "job count" governor.. since ze01 started first, it picked up 200 jobs by itself and loaded up to 150+16:35
corvusJan  7 18:26:10 ze01 kernel: [8895847.097575] traps: zuul-executor[10850] general protection ip:513ef4 sp:7f2525ff9068 error:0 in python3.5[400000+3a9000]16:35
corvusdmsimard: not yet.  ram first.  then rate limit.16:35
*** d0ugal has quit IRC16:35
pabelangerfungi: clarkb: mordred: ^ should get puppet working again on git servers, is a revert of python-six removal. I think moving forward, we should discuss our DIB control plane effort (tomorrow) to finally solve cloud-init issues16:35
dmsimardfungi: the unattended-upgrades log I sent was probably unrelated but I stumbled on it when I was troubleshooting the issue16:35
dmsimardit was isolated to ze10 only afaik, which had crashed last week so it probably died in the middle of a package upgrade16:36
corvusJan  7 18:56:03 ze02 kernel: [12449956.548285] traps: zuul-executor[27272] general protection ip:513ef4 sp:7f05aeffJJaJaJan  7 18:56:03 ze02 kernel: [124499Jan  7 18:5Jan  7Jan  JaJanJJaJJan  7 18:56:03 ze02 kernel: [12449956.548285] traps: zuul-executor[27272] general protection ip:513ef4 sp:7f05aeff9918 error:0 in python3.5[400000+3a9000]16:36
fungiyeah, the gpf corvus pasted above was some 36 hours after the last unattended-upgrades run did anything with packages on ze01 according to dpkg.log, so likely unrelated16:36
*** slaweq has quit IRC16:37
corvuswow that was som weird pasting16:37
* fungi blames tabs16:37
clarkbpabelanger: fwiw there shouldn't be any cloud-init issues currently as we explicitly remove it as part of launch node execution16:37
clarkbpabelanger: its unrelated to the hostname stuff too. We explicitly set the hostname to the hostname we don't want16:37
dmsimardcorvus: there's probably no mistaking that timestamp, it correlates to when everything died16:38
*** kmalloc has joined #openstack-infra16:38
pabelangerclarkb: are you sure? ze09 and ze10 have cloud-init installed16:39
dmsimardsomething that I noticed when troubleshooting is that while this was not our problem -- do we really want to point to the develop branch of github3 ? There's a lot of commits there on a regular basis16:39
*** gyee has joined #openstack-infra16:39
dmsimardI'll copy/pasta that in #zuul16:39
clarkbpabelanger: ya its the step before we set the hostname in https://git.openstack.org/cgit/openstack-infra/system-config/tree/playbooks/roles/set_hostname/tasks/main.yml#n216:39
corvusdmsimard, fungi: http://paste.openstack.org/show/640975/16:39
clarkbpabelanger: we do remove cloud-init then set the hostname to the value we don't want16:40
fungicomparing the gpf from ze01 with puppet events, i don't see any tight correlations16:40
pabelangerokay, something must be pulling it back in16:40
pabelanger2018-01-05 23:54:10,759 - cc_update_hostname.py[DEBUG]: Updating hostname to ze09 (ze09)16:40
*** kjackal has quit IRC16:41
pabelangerthat is from /var/log/cloud-init.log16:41
fungipabelanger: it boots with cloud-init initially because the images we're using (provided by rax) have it installed. then we uninstall it16:41
clarkbright so cloud init comes up does whatever it does, then we should uninstall it and set the hostname to what we actually want16:42
clarkbbut we instead set it to ze09 too16:42
dmsimardbrb more shovelling (I love snow but this is a lot of snow now...) and lunch..16:42
clarkbbecause of the split at https://git.openstack.org/cgit/openstack-infra/system-config/tree/playbooks/roles/set_hostname/tasks/main.yml#n1216:42
*** jkilpatr has quit IRC16:44
AJaegerconfig-core, could you review https://review.openstack.org/#/c/531430/ , please? - we need this to fix publishing of openstack-manuals and friends16:44
*** jpena is now known as jpena|brb16:44
pabelangerfungi: clarkb: but dpkg -l cloud-init returns a result, doesn't that mean it is still installed?  This is ze0916:46
pabelangeror did we just remove it and haven't launched a new server?16:46
clarkbpabelanger: right its entirely possible that that ansible isn't doing what we want. My point is more even if cloud-init was completely gone we then set the hostname to what we don't want. So no amount of changing cloud-init will fix this16:47
*** david-lyle has quit IRC16:47
clarkbits also possible this isn't running for some reason? though the same part of launch node that executes puppet is what executes the hostname update16:48
*** david-lyle has joined #openstack-infra16:48
*** pcaruana has quit IRC16:48
*** yamahata has quit IRC16:48
*** fultonj has quit IRC16:48
pabelangerokay, so 2 things. Figure out why cloud-init is still installed, 2) figure how what hostname should be set ti16:49
fungipabelanger: when you `dpkg -l cloud-init` is shows "rc" as the status16:50
fungithat means "removed, configuration still present"16:50
fungiwhich is what you get if you remove without --purge16:50
pabelangerfungi: ah, okay. that makes sense16:51
*** ram5391 has quit IRC16:52
pabelangerfungi: so, we can update ansible to purge that16:52
*** david-lyle has quit IRC16:52
clarkbwe may not want it to purge16:52
clarkbso that if we do reinstall cloud-init it doesn't act like its on a fresh cloud init16:52
fungiif you want, it's not hurting anything leaving the conffile behind though afaik16:52
pabelangerclarkb: good point16:52
*** e0ne has joined #openstack-infra16:53
*** yamamoto has joined #openstack-infra16:53
*** fultonj has joined #openstack-infra16:56
*** ram5391 has joined #openstack-infra16:56
*** caphrim007 has joined #openstack-infra16:57
*** d0ugal has joined #openstack-infra16:59
*** jkilpatr has joined #openstack-infra17:00
openstackgerritMonty Taylor proposed openstack-infra/infra-manual master: Update the PyPI registration docs  https://review.openstack.org/53185917:00
*** slaweq has joined #openstack-infra17:00
mordredAJaeger, dhellmann, fungi: ^^ there's a stab17:00
*** iyamahat has joined #openstack-infra17:01
*** yamamoto has quit IRC17:02
clarkbpabelanger: fungi mordred corvus probably the first thing we need to do is decide if we want hostnames to be ze09 or ze09.openstack.org. Then modify the launch script's set hostname role to use foo.openstack.org if that is what we want17:04
clarkbI know SpamapS was running into similar things with glean recently but I think he wants something slight different which is use the name that nova provides by combining hostname and domainname into an fqdn. Which for us would be foo.novalocal because we don't have the integrated designate stuff17:05
mordredclarkb: I mean, I for one would like 'hostname' to return 'ze09' and 'hostname --fqdn' to return 'ze09.openstack.org'17:05
clarkbmordred: thats what we currently have and I think you implemented it that way :)17:05
mordredclarkb: the hostname provided by nova is completely broken17:05
mordredalthough I would LOVE IT if it wasn't17:05
clarkbmordred: yes I know, but you need to convince spamaps it isn't17:06
mordredwell - it's completely broken for public cloud17:06
mordredI could see it being totally correct for a private cloud - since the problem with it is that .novalocal is a cloud-admin setting17:06
mnaser^ it relies on dhcp_domain which is a used by nova-network and usually takes <server-name>.<CONF.dhcp_domain>17:06
mnaserbut if you're using a private network (with a recent release of openstack), you can set the dhcp domain for the network17:07
clarkbmnaser: oh thats good to know (though won't fix all cases)17:07
*** eumel8 has quit IRC17:07
clarkbmordred: I thik the confusion specific to us was that we always had ze09.openstack.org as the hostname17:07
clarkbmordred: then we change it to be what you describe (and cloud-init also possibly changed things on its endtoo)17:08
*** bhavik1 has joined #openstack-infra17:10
*** bhavik1 has quit IRC17:11
*** slaweq has quit IRC17:11
*** d0ugal has quit IRC17:11
fungiyeah, my understanding of wanting glean to support the nova-supplied domain is that in cases where it's configurable by the cloud user for their network, it's convenient to not have to hard-code domains into configuration management17:13
fungithough that still gets back to... if your instance has multiple network interfaces on different networks, which one sets the primary domain name? the one with the default route?17:14
mordredfungi: totally - and I am rather sympathetic to that desire17:14
AJaegermordred: a few nits on your change. But a more fundamental question:17:15
mordredfungi: this is amongst the reasons that I think that not having designate integrated fully is crazypants and that we should consider designate an essential part of our IaaS story17:15
*** pcichy has joined #openstack-infra17:15
AJaegerWhat is the workflow: 1) add publish-to-pypi to project-config; 2) "Prepare and Publish an Initial Release for Registration" - or the other way?17:15
*** dsariel has quit IRC17:16
mordredAJaeger: yah - I think that actually we should do $something to ensure that we reserve the name on PyPI before creating the  project in the system otherwise17:16
AJaegermordred: right I check before publish-to-pypi is set that the project exists but your description uses git push etc. so assume publish-to-pypi17:16
*** jascott1 has quit IRC17:17
mordredAJaeger: yah. also - if one adds the project to the system, then goes to register on pypi and only then realizes the name is taken, now we've got a renaming problem17:17
*** jascott1 has joined #openstack-infra17:17
AJaegermordred: then your description needs to add the two stesp "$something" and "add publish-to-pypi"17:17
*** ijw has joined #openstack-infra17:17
mordredyah. I'm starting to think I need to rewrite it ... here's an idea ...17:17
corvusAJaeger, mordred, dhellmann: sorry i missed the conversation earlier (well, only a little sorry -- i was asleep) -- but i would feel really uncomfortable going through the whole project creation process without having registered the name in pypi.  indeed, the most recent projects i've created, i did just upload an empty release in order to register the name.17:17
AJaegermordred: we always have - if people do this later. But yes, we should register directly17:18
AJaegercorvus: I think both mordred and myself are in agreement here. That's what I require today and I suggest to keep that.17:18
mordredAJaeger, fungi, dhellmann, corvus: what if we add 2 fields to gerrit/projects.yaml - python: <bool, defaults to true> - python-package: <str, defaults to name> ...17:18
corvusAJaeger, mordred, dhellmann: if you think creating the repos then uploading is the right thing to recommend, i won't object -- but i feel a little weird about it because i don't think i'd ever be comfortable following that process myself.17:18
*** jamesmcarthur has quit IRC17:19
mordredand then we add a check job for projects.yaml that verifies for python projects if the project name is either available or if it is already registered if the openstackci user has correct permissions17:19
mordredand a post job that creates the project with a null release17:19
mordredit's a bit more automation work on our part, but it protects us from adding pytohn projects we can't publish17:20
corvusmordred: that's not bad.... maybe also have jeepyb check that happened before creating gerrit projects, etc?17:20
AJaegermordred: would work for me - and remove a manual step for setup17:20
corvus(so if the post job failed, we don't proceed until someone manually fixes)17:20
*** yamahata has joined #openstack-infra17:20
mordredcorvus: ++17:21
*** jamesmcarthur has joined #openstack-infra17:21
*** trown is now known as trown|lunch17:22
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP: Support cross-source dependencies  https://review.openstack.org/53080617:23
*** jpena|brb is now known as jpena17:24
openstackgerritAdam Spiers proposed openstack-infra/infra-manual master: promote IRC channel creation info into its own section  https://review.openstack.org/53113317:27
*** ram5391 has quit IRC17:27
*** kjackal has joined #openstack-infra17:28
*** Apoorva has quit IRC17:29
clarkbcorvus your feedback on mordred's ideal hostname situation would be nice as I think you aren't entirely.happy woth the current situation (which I think achieves mordred's ideal)17:31
dmsimardLast Ubuntu update was yesterday about candidate kernels being spun up.. https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown17:32
dmsimardThey were really caught off guard and they were at the last minute already..17:32
*** jpich has quit IRC17:33
*** david-lyle has joined #openstack-infra17:34
*** jascott1 has quit IRC17:34
*** eharney has joined #openstack-infra17:37
*** gema has quit IRC17:38
corvusclarkb: the thing i'm unhappy about is that every time we spin up a machine, we have a 50% chance it will get one kind of hostname or the other, and we spend a long time going through the whole process to try to figure out why "this server" did it "this way" instead of "that way" like "that other server".  if we can get a consistent behavior, i'll be happy.  can you or mordred reply to that email thread with what you think the final ...17:39
corvus... state should be, and what we have to do to get there?17:39
*** yamamoto has joined #openstack-infra17:43
*** yamamoto has quit IRC17:43
*** felipemonteiro has joined #openstack-infra17:45
*** david-lyle has quit IRC17:47
*** jascott1 has joined #openstack-infra17:48
clarkbI think it is consistent now17:48
SpamapSclarkb: You all convinced me that I was wrong about wanting an fqdn in hostname. :)17:48
clarkbwhich is what set hostname does during launch node17:49
clarkbI think without that it would depend on cloud init/nova agent17:50
corvusclarkb: didn't you say set_hostname does a split?17:50
*** ram5391 has joined #openstack-infra17:51
corvusclarkb: oh, disregard that, sorry17:51
clarkbcorvus: yes so remove the .openstack.org from hodtname17:51
corvusclarkb: so why are all the other executors ze.o.o ?17:51
corvusdid we change something since we launched them?  it wasn't that long ago17:52
*** lucasagomes is now known as lucas-afk17:52
*** ram5391 has quit IRC17:53
clarkbyes set hostname is new17:55
dhellmannmordred , corvus , AJaeger : automatically creating things on pypi when we create the repo seems ok, but there's a chance the name used in setup.cfg won't match the name used in projects.yaml so we need to either enforce that or allow for it in other processes later17:55
clarkbas is the cloud init uninstall17:55
*** e0ne has quit IRC17:55
corvusdhellmann: i think mordred suggested we have a field in projects.yaml to 'override' the normal project name, so folks can set it to what they know they will put in setup.cfg later17:56
*** Apoorva has joined #openstack-infra17:57
dhellmanncorvus : sure. I'm anticipating a source of mistakes with manually replicating that value.17:57
dhellmannI don't know how likely that is to actually come up17:57
corvusdhellmann: ah i see -- if someone forgets to set it there, we could end up with a spurious registration... i guess we could just delete it in that case17:57
dhellmannyeah17:58
*** Goneri has quit IRC17:58
corvusclarkb: set_hostname is almost a year old... the executors are only a few months17:58
dhellmannto fungi's earlier point if the purpose of this api change on pypi was to avoid having people park names, maybe we're better off just asking teams to prepare real releases quickly17:58
dhellmanneven if the "real" release is just an alpha with some packaging metadata17:59
*** greghayn1 is now known as greghaynes17:59
*** derekh has quit IRC18:01
corvusdhellmann: that sounds reasonable, but i don't think i could convince myself to do that.  i would never feel comfortable doing all the work to create a new project without knowing i had secured the name.  the cost to secure the name is trivial; the cost of a rename is very high.18:01
dhellmannI'm probably in the same camp. In fact, I'm pretty sure I've done exactly that -- publish from a local set of files before things were even on github18:02
*** Goneri has joined #openstack-infra18:02
corvusdhellmann: yeah, same here, but s/github/gerrit/ :)18:03
dhellmannwell, yeah, not everything I do is openstack or self-hosted18:03
corvuspretty sure i did that for the most recent projects i created18:03
mordredcorvus, dhellmann: npm recently added namespaces to their uploads - which are signified with an @ sign -so like angular-ui-router (ui-router project for angular but not by angular) became @uirouter/angularjs ... I wonder if we should propose to donald something similar for warehouse18:04
*** slaweq has joined #openstack-infra18:05
mordredit would be nice to be able to publish to @openstack/nova and @openstack/keystone (or even openstack/nova and openstack/keystone - no clue why the @ was added)18:05
*** ralonsoh has quit IRC18:05
dhellmann"Namespaces are one honking great idea — let's do more of those!"18:05
*** efoley has quit IRC18:06
dhellmannmordred : so the thing with the / could be distinguised from a filename?18:06
mordreddhellmann: ah - yah - probably so18:06
fungicorvus: to be fair, the cost to secure the name on pypi is trivial for someone who's at least minimally versed in the python packaging ecosystem... we have people wanting to create new python projects who seemed to have trouble even following our earlier instructions for registering packages (back when that still worked)18:06
funginow, whether or not that barrier to entry is a good thing is debatable18:07
openstackgerritDmitry Tantsur proposed openstack-infra/project-config master: Update the list of ironic jobs in nova's experimental queue  https://review.openstack.org/53186818:07
* fungi feels like letting some things remain hard for people who won't take the time to gain familiarity with the ecosystem is entirely justified, but often gets accused of not taking "developer friendliness" into account18:08
openstackgerritGage Hugo proposed openstack-infra/project-config master: Remove legacy jobs from Keystone  https://review.openstack.org/52423218:12
corvusfungi: yes.  i'm not opposed to merging mordred's change as-is if we think that's the best way (i said so above).  i would personally have trouble +2ing it because i would be recommending something other than what i would do myself.  so if it were all up to me, i would probably work out how to make an empty release and then document that for developer friendliness, since that's what i would do.18:14
*** Goneri has quit IRC18:16
corvusthe most importanting thing for developer friendliness is that we have *something (that works)* documented :)18:16
fungiyep, i completely agree18:16
*** slaweq has quit IRC18:17
fungiwe could also recommend both creating a basically empty package (my old instructions there are already partly sufficient), and then mention that if the submitter is comfortable taking the risk that they should make sure to tag a very early (even alpha) release as soon as they merge packaging boilerplate to properly exercise the automation anyway18:17
fungii wonder if simply stuffing that dummy PKG-INFO file into the right path in a tarball would do the trick18:18
*** jpena is now known as jpena|off18:18
*** hashar is now known as hasharDinner18:19
*** jkilpatr has quit IRC18:19
fungithe primary hurdle we ran into with the last iteration of instructions (before the upload form on pypi.p.o was taken away for good) was people who only had access to windows systems trying to figure out how to use notepad to create a file without an extension18:19
*** dtantsur is now known as dtantsur|afk18:20
corvusfungi: mordred's proposed automation is probably the best response then :)18:20
fungibut again, if they can't get far enough to make a stub python package, they're going to have a devil of a time running any tests on their software locally18:21
*** slaweq has joined #openstack-infra18:21
fungii'm also perfectly fine with the idea that our instructions strongly urge the reader to have (and be proficient with) a unix/linux environment or else make friends with someone who can do the necessary steps for them18:23
fungiit's not our job to teach people how to computer18:23
dhellmannwhy do they need to be able to create a file without an extension?18:24
fungithe old instructions said to make a PKG-INFO file18:25
dhellmannoh, ok18:25
fungifor uploading in the (no longer available) registration form18:25
dhellmannah18:25
fungiafter they took away the parts of the form where you could enter the fields directly, but before they got rid of the place where you could still upload a PKG-INFO file18:26
fungithey were progressively paring away the places where name squatters could spam empty project creation with minimal effort18:27
*** shardy is now known as shardy_afk18:27
corvuss/squatters/developers/;s/spam/perform/18:28
fungiright. basically squatters need automation to be able to do what they want to do on a mass scale... so the pypi response has been to make project creation increasingly hostile to automation (and hence anyone who wants to legitimately automate stuff)18:29
corvus(i'm baffled why this workflow is okay in any situation)18:29
corvusfungi: i don't think it's hostile to automation, i think it's hostile to python developers.18:29
*** trown|lunch is now known as trown18:29
fungii agree that's the end result. it takes very little additional effort to adjust automation to create and upload empty sdists18:30
fungiyet significantly more effort for people creating new projects on pypi on a smaller scale to wrap their heads around18:30
dhellmanndid they really have a problem with bulk squatters?18:30
dhellmannI figured it was just an issue with a few common names or something18:31
fungiyup. for a while there was a rash of typo squatters uploading (thankfully only prankish that anyone found) packages for slight misspellings of popular projects18:31
dhellmannah18:31
*** slaweq has quit IRC18:31
fungiand also bulk registering discionary words18:32
fungier, dictionary18:32
corvusi'dve thought a captcha or something would be a preferred approach18:32
fungiostensibly auctioning off control of them18:32
dhellmannI guess I missed all of that18:32
fungiif memory serves some of them had readmes with instructions on how to purchase control (obviously those got taken down by the pypi admins once reported)18:32
corvusfungi: yeah, that last thing is why the scheme is obviously dumb18:33
corvus"how about instead of paying you, i just ask the nice human to tell you to take a hike?"18:33
*** jkilpatr has joined #openstack-infra18:33
*** slaweq has joined #openstack-infra18:34
fungibut yeah, they have (or at least had anyway) only a couple of part-time sysadmins taking care of pypi so some of the reactions seemed (to me at any rate) to have been of the knee-jerk variety18:34
*** beekneemech is now known as bnemec18:34
fungithey just recently got a very generous infrastructure funding donation so have been able to hire on a lot of additional humans to finish retiring teh cheeseshop and get the remaining missing bits of warehouse implemented18:35
*** shardy_afk has quit IRC18:35
fungiso hopefully the situation will improve in the nearish future18:35
*** tesseract has quit IRC18:35
*** armaan has quit IRC18:36
*** shardy_afk has joined #openstack-infra18:36
*** armaan has joined #openstack-infra18:36
fungialso i gather the removal of the registration form was only partly driven by abuse, and was also seen as a continuation of the plan from some several years ago to transition away from being a general package index separate from package hosting18:37
fungiso well before the registration forms were touched, they stopped having pypi index externally-hosted artifacts18:37
fungiand i'm pretty sure as a result of requiring that projects in the index have their artifacts hosted in pypi itself, the warehouse spec didn't include any form for registering a new project separate from uploading the initial artifact18:38
fungithus the registration form was seen as a legacy feature of the (deprecated) cheeseshop platform18:39
dhellmannthat makes a lot of sense. I still think it's an oversight, but I can see how they would come to that conclusion.18:39
dhellmannmaybe 'reserve a name' is a separate operation that creates a record that times out after some period of time18:40
corvusdhellmann: ++18:40
dhellmanns/is/should be/18:40
fungiyeah, feels a bit like tunnel-vision to me. but also could be a pragmatic choice they made to keep the hitlist of warehouse requirements for production availability limited to an achievable scope18:40
dhellmannnamespaces seems like a better ultimate solution18:41
corvusthough, in some ways it shifts the problem18:41
dhellmannalthough then you have to deal with things like moving a package from @dhellmann/virtualenvwrapper to @virtualenvwrapper/virtualenvwrapper or whatever as new owners take over18:42
dhellmannso you have different issues, too18:42
dhellmannwhat do the container image registries do about that? do they care?18:42
dhellmannmaybe it's not quite the same problem for them18:42
fungibasically, from what i've been able to gather (and encountered myself recently trying to track down the Project_URL support pieces for my setuptools/pbr implementations) the cheeseshop code is an unmaintainable mess of >decade-old spaghetti, and that's contributed to the reluctance of the current team to really implement anything new in it (even something relatively simple like a captcha, or fixing18:43
fungithe now-not-so-recent google openid changes)18:43
*** yamamoto has joined #openstack-infra18:44
fungiand that's driven the move to get warehouse in place with a minimal required featureset so they can officially shut down the cheeseshop before they even begin to talk about more significant changes to the archive18:45
dhellmannyeah, that's definitely my impression, too18:46
dhellmanniirc, the legacy code was built before there were popular web frameworks for python18:46
fungis/for python// ;)18:47
dhellmannthe approach they're taking for replacement makes sense18:47
fungi(depends on your definition of "popular" too i guess)18:47
dhellmannI believe pypi predates even zope18:47
fungiASPs. very dangerous. you go first18:48
clarkbcorvus: ok back from optometrist18:49
clarkbcorvus: ya looks like launch node started doing the set hostname thing in march. now to see if set hostname has always had the same behavior18:50
clarkbcorvus: we started removing cloud init in october18:51
fungione of the consistency concerns on the hostname front is that debuntu take a different approach than rhel/centos18:51
corvusclarkb: oh, so maybe up till then, we were still fighting it, but now we've stopped that and it's stabilized?  but servers launched before then had the full hostname due to cloud init?18:51
fungi(i think the red hat guidance on setting hostname to an fqdn is patently wrong, but admit my judgement may be clouded by years as a debian user)18:52
corvusfungi: our setting it explicitly will "correct" that though (either approach should work on either system, afaik)18:52
dmsimardThe zuul executors losing connections to the hosts are starting to be quite problematic... http://status.openstack.org/elastic-recheck/#1721093 with http://status.openstack.org/elastic-recheck/#1718197 combined account for ~1200 gate failures over the past 10 days. When I last wanted to check, ze09 and ze10 were crashed so I got sidetracked by that but I'll try to understand what's going on now.18:52
clarkbcorvus: ya thats my current theory18:52
*** yamamoto has quit IRC18:52
dmsimardA low hanging fruit I was wondering.. would it be worth considering adding a ssh config for keeping the connection alive client-side ? Like .ssh/config "ServerAliveInterval 60"18:53
corvusclarkb: so we should 'correct' all hosts other than ze09?18:53
dmsimardze09 should have been corrected now (manually)18:53
dmsimardor, well, at least be consistent with the other zuul executors18:54
corvusdmsimard: then it's been 'un-corrected' :)18:54
clarkbcorvus: or correct all the xenial hosts and fix things when we go to trusty?18:54
clarkber18:54
clarkbwhen we upgrade off of trusty18:54
clarkbfungi: our git.o.o server does the same as ubuntu servers in our case. hostname -> git, hostname -f -> git.openstack.org18:54
corvusdmsimard: i would not consider any changes to ssh in zuul to be low-hanging-fruit due to the thoroughness that must be involved in making any changes, but do please look into it.18:54
fungidmsimard: it's worth a try as long as paramiko supports it, but the particular incident i looked at last week acted like the node's filesystem had turned read-only and so the ssh connection wasn't actually broken, it just never responded to new commands over the socket18:55
dmsimardcorvus: this would be puppet-zuul IMO18:55
corvusdmsimard: this==?18:55
dmsimardcorvus: setting up the .ssh/config keepalive18:55
fungidmsimard: are we using openssh and not paramiko with ansible?18:55
corvusdmsimard: no, zuul manages its own ssh client config18:55
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Add support for a secure ZooKeeper configuration  https://review.openstack.org/53188218:56
* fungi will readily admit the ansible ssh backend is a bit of a black box to him18:56
dmsimardansible doesn't use paramiko unless you explicitely tell it to (if ssh is available)18:56
dmsimardparamiko is the fallback18:56
corvusfungi: what dmsimard and we do not tell it to use paramiko so we use openssh18:56
fungioic, so if no ssh client is present, paramiko gets used18:56
dmsimardcorvus: hmm, I know that executor server sets up some ssh configuration for ansible (such as pipelining), I'll look there.18:57
corvusdmsimard: just make sure you consider the whole environment, including especially controlpersist.18:57
fungidmsimard: also, if the goal is dead peer detection, see the ServerAliveCountMax and ClientAliveCountMax options (for ssh_config and sshd_config respectively)18:58
fungithough, again, if the particular node i looked at last week is representative, i don't think _any_ of thos will help18:59
dmsimardfungi: yeah I know about ServerAliveInterval for client side, sshd_config would need to go into the nodepool VMs I guess ?18:59
fungis/thos/this/18:59
dmsimardfungi: there's been ~1200 failures in recent history, I doubt they all match that particular pattern18:59
dmsimardbut it's something I want to find out18:59
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Rename _useBuilder method to useBuilder  https://review.openstack.org/53188318:59
fungidmsimard: right, if we want the nodes to send keepalives and to detect the executor going away, then presumably have dib adjust the /etc/ssh/sshd_config19:00
* dmsimard nods19:01
corvuswhat would that accomplish?19:01
*** slaweq has quit IRC19:01
fungithough just doing the client side on the executor may be sufficient given that i doubt there's any graceful anything we need the nodes to concern themselves with19:01
*** yamamoto has joined #openstack-infra19:01
dmsimardyeah just ServerAliveInterval by itself is magic... I'll even recover ssh connections after waking up my laptop from hibernation :)19:01
*** slaweq has joined #openstack-infra19:02
fungithe keepalive is a ping/pong so doing it from either client or server should be sufficient to keep firewalls and nats from destroying what it sees as idle connections. from a dead peer detection standpoint we probably only care that the executor can detect the client failing to respond and not the other way around19:03
fungisince an unresponsive node means the job fails and nodepool deletes it19:03
dmsimardfrom looking elastic-recheck, it seems to happen in waves19:03
dmsimardThere was two large peaks recently, one today and one Jan 4th19:04
clarkbfungi: I've also just now sorted out the ssh hostkey for ansible and git.openstack.org19:05
clarkbmordred: fungi can you review https://review.openstack.org/#/c/531851/1 to fix puppet on git0*.o.o?19:06
*** slaweq has quit IRC19:06
fungithanks! i missed that one getting uploaded19:06
dmsimard126x "Ansible timeout exceeded" on ze09 alone19:08
dmsimardnevermind, half that because it was picking up both debug and normal logs19:08
dmsimarda few OOM kills but not that many19:09
*** xarses_ has quit IRC19:09
*** slaweq has joined #openstack-infra19:09
*** xarses_ has joined #openstack-infra19:09
dmsimardstarting a pad.. I'll write my notes there: https://etherpad.openstack.org/p/executor-timeouts19:10
*** harlowja has joined #openstack-infra19:19
*** slaweq has quit IRC19:19
*** pramodrj07 has joined #openstack-infra19:22
*** e0ne has joined #openstack-infra19:22
*** pramodrj07 has quit IRC19:22
*** wolverineav has quit IRC19:23
*** wolverineav has joined #openstack-infra19:23
*** wolverineav has quit IRC19:26
clarkbdmsimard: you might try correlating it to high load, cacti should help with historical load data19:26
*** wolverineav has joined #openstack-infra19:26
dmsimardyeah, I am to some extent with grafana19:26
dmsimardfor today's wave, there has been no OOM killers though19:26
dmsimardonly 2 on ze09, nothing on the others19:26
clarkbload is orthogonal to oomkiller though19:26
clarkbbut if load gets high enough it may not be able to keep all those connections open reliable19:27
AJaegerconfig-core, could you review https://review.openstack.org/#/c/531430/ , please? - we need this to fix publishing of openstack-manuals and friends. It removes some explicit parameter, the defaults work just fine19:28
*** slaweq has joined #openstack-infra19:28
* AJaeger waves good bye19:29
dmsimardclarkb: we're on the same wavelength for that, load is generally high (above 10) but I'm trying to see if there's anything in particular19:29
fungiload is a relative measurement. what's "high" for some systems may be entirely reasonable for others (for example an mta with a system load >250 might still be entirely healthy)19:30
dmsimardthe notion of keeping those 80+ concurrent ansible playbooks running (over ssh) reliably must be a bit challenging, I mentioned the client-side (executor) ssh keepalive we could add but perhaps there's something else19:30
dmsimardfungi: right, it also depends on a multitude of factors.. cpu, ram but also i/o (and i/o wait)19:31
*** jamesmcarthur has quit IRC19:31
dmsimardfor example, keeping ze09's top open, I see a consistent ~10% i/o wait19:31
*** dhajare has joined #openstack-infra19:32
dmsimardkwapd taking a large amount of CPU cycles19:32
dmsimardkswapd*19:32
dmsimardso we're likely swapping out to a (slow) disk because we're running out of ram and it exacerbates everything else ?19:33
*** jkilpatr has quit IRC19:33
fungidmsimard: yeah, the executor is using a fair amount of ram19:34
fungidipping 2.2gb into swap there is likely unhealthy19:34
fungi5660080 virt for zuul-executor pid 971819:35
dmsimardthe ram usage is why I was inquiring about where ansible kept it's output buffer the other day19:36
dmsimardI know we end up streaming it, but we likely don't discard the "standard" output (which is, amongst other things, passed to ara)19:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP: Support cross-source dependencies  https://review.openstack.org/53080619:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Move CRD tests to test_gerrit_legacy_crd  https://review.openstack.org/53188619:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add skipped CRD tests  https://review.openstack.org/53188719:37
dmsimardsome of the "command" (legacy and other) tasks end up running for an hour just by themselves, that's one hour worth of buffering output19:38
dmsimardfor example "run devstack" (cue 30+ minutes of waiting for this one task)19:38
* dmsimard asks #ansible-devel19:39
*** Goneri has joined #openstack-infra19:39
*** e0ne has quit IRC19:40
openstackgerritMerged openstack-infra/puppet-jeepyb master: Revert "Remove python-six on centos"  https://review.openstack.org/53185119:41
*** felipemonteiro_ has joined #openstack-infra19:41
dmsimardokay, so the output is buffered in RAM on the target node -- so not on the executor node.19:41
corvusdmsimard: we don't discard it.  the output is buffered on the remote host while the task is running.  then it's sent back to ansible running on the executor at the end.19:42
*** wolverineav has quit IRC19:42
corvusdmsimard: ansible will need to process it.  i don't know how efficient it is with processing large json blobs19:43
dmsimardcorvus: how do you feel about the ram usage on the executors ? is that something we want to look into or do we want to throw more machines at it ?19:43
SpamapSCurious.. have we seen impact from meltdown fixes at the infra node providers?19:43
corvusdmsimard: i absolutely want to have the ram governor in place19:43
corvusdmsimard: i don't want to spin up more executors until it is19:43
fungiSpamapS: no directly observed impact so far19:43
SpamapSI'd guess by now some of them are rolling out PTI enabled hypers.19:43
fungiSpamapS: at least as far as i'm aware19:43
*** david-lyle has joined #openstack-infra19:43
*** wolverineav has joined #openstack-infra19:44
dmsimardcorvus: yeah, but beyond that, I mean, do you think the ram usage is legitimate right now ?19:44
corvusdmsimard: hard to say without the ram governor.  the distribution is not sufficiently even19:44
fungiSpamapS: the vast majority of our control plane in in rax, which runs xen, and the guest risk on xen is mitigated by using hvm, so we may see no impact there19:44
SpamapSpabelanger: weren't you resurrecting my RAM governor patch?19:44
dmsimardthere's a zuul meeting today, let's chat ram governor then :D19:44
SpamapSfungi: guest risk, but you still have to update your hyper kernel.19:45
*** felipemonteiro has quit IRC19:45
fungiSpamapS: yeah, in theory they live migrate us around to do that (in practice, it breaks for some of our instances, but that's been a constant thing well before now)19:45
fungiSpamapS: the main impact i'm expecting to observe is performance19:46
fungibut that's going to be tough to measure19:46
SpamapSI'm also pretty sure zuul executors will run for crap with PTI.19:46
SpamapSSince the worst case is "lots of network I/O with CPU in between"19:46
dmsimardyeah, it sucks.19:47
SpamapSHave we already built test images with Ubuntu's new kernels?19:47
dmsimardthey're not out yet unless mistaken19:47
SpamapSIIRC they just published today19:47
dmsimardlast I looked earlier today ..19:47
dmsimardreleased kernels are still TBD https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown19:48
SpamapShttps://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/19:48
*** TLAXKIT has quit IRC19:48
SpamapSPPA only right now19:48
fungiwhat a marvellous place for them19:48
dmsimardit's a staging ground before release afaik19:49
SpamapSI believe they're taking it slow because of the perf problems they raise.19:49
SpamapSI mean, there's nothing to protect from exploits if the DC burns down. ;)19:49
fungimakes sense, assuming they consider potential performance regression to be a bigger problem than your users taking over your servers19:50
dmsimardyeah... meltdown seems scaringly easy to exploit19:50
clarkbSpamapS: rax is largely unaffected because hvm guests cant attack the hypervisor19:50
dmsimardespecially if it has really existed for the past 20 years ..19:50
clarkbSpamapS: so havent really seen anything on our control plane19:50
dmsimardclarkb: do we know if rax is up to date ?19:50
clarkbdmsimard: they dont have to update if they dont have pv nodes19:51
dmsimardWell, regardless of virtualization attack vectors, they likely need to update their hypervisors and that would have an impact on performance (does ephemeral live on the compute nodes?)19:52
dmsimards/hypervisors/compute nodes/19:52
clarkbthats what I'm saying they likely dont have to because hvm19:53
clarkbxen is only affected if running 64bit pv guests19:53
*** yamamoto has quit IRC19:53
dmsimardmeltdown isn't just about virtualization, it's about processes being able to read RAM from other processes (cross boundary) -- so I would think they want PTI enabled on their compute nodes even if the VMs can't attack them, it's still a door opened for anything else.. right ?19:55
fungiunless they simply assume that any account on the hypervisor host is equivalent to root19:55
clarkbxen wrote a blog about it19:56
clarkbthey seemed to bein a pretty good position19:56
dmsimardyeah, but the node has other software (l3 agent, ovs, dnsmaq or whatever)19:56
clarkbaiui beause they already do multiple virtual address spaces19:56
fungii think dmsimard's point is that local processes on the hypervisor host are still a risk even if the guests aren't19:56
dmsimardfungi: +119:56
clarkbsure but those are all privileged anyeays19:57
clarkbevery one of those is19:57
dmsimard¯\_(ツ)_/¯19:57
fungiwhich is what i meant by "assume that any account on the hypervisor host is equivalent to root"19:57
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Add support for a secure ZooKeeper configuration  https://review.openstack.org/53188219:57
fungiodds are in a hands-off deployment that very well may be a safe enough assumption19:57
clarkbalso those dont run on the hypervisor with xen right?19:58
clarkbso guests wont see a cpu impact19:58
clarkbjs I guess what I am getting at as they already run in this safer mode19:58
fungidepends on how you have xen deployed, but yes commonly the control processes actually run in a separate guest as well19:59
fungiand so there's really no process other than the kernel in the "host"19:59
openstackgerritMonty Taylor proposed openstack-infra/jeepyb master: Add checking for PyPI project ownership  https://review.openstack.org/53189820:00
*** sdague has joined #openstack-infra20:00
fungigranted, it's been a long while since i ran any xen hosts myself so some of that may have changed20:00
mordredfungi, dhellmann, AJaeger, corvus: ^^ there's project creation validation added to manage-projects as well as a utility script we can use in a gate job to do the same thing in check/gate20:00
clarkbbut yes guests should update but thats on the customer (us)20:01
clarkband we may see an impact once ubuntu pushes out kernels20:01
*** Apoorva has quit IRC20:01
*** Apoorva has joined #openstack-infra20:02
*** Goneri has quit IRC20:02
dhellmannmordred : added to my review queue20:02
*** jgriffith_ is now known as jgriffith20:03
EmilienMpabelanger: when you have time, please look https://review.openstack.org/#/q/status:open+project:openstack-infra/system-config+branch:master+topic:puppetlabs/mirrors20:04
fungiwho was working on zuul v3 support in puppet-openstackci?20:04
openstackgerritMonty Taylor proposed openstack-infra/jeepyb master: Add checking for PyPI project ownership  https://review.openstack.org/53189820:04
clarkbfungi: mmedvede20:04
fungithanks clarkb20:04
*** yamamoto has joined #openstack-infra20:04
mordreddhellmann: it SHOULD be possible to try out the check-pypi command with just a local copy of projects.yaml20:05
dhellmannk20:05
openstackgerritAmy Marrich (spotz) proposed openstack-infra/irc-meetings master: Add entry for the Diversity WG  https://review.openstack.org/53190020:05
*** dsariel has joined #openstack-infra20:06
*** snapiri1 has joined #openstack-infra20:07
*** snapiri1 has quit IRC20:08
*** CrayZee has joined #openstack-infra20:08
*** yamamoto has quit IRC20:09
*** jkilpatr has joined #openstack-infra20:11
CrayZeeHi, Is there something wrong with zuul or is it just a problem on my side?20:13
mwhahahai'm getting a service unavailable from zuulv3.o.o so probably not just you20:14
*** ldnunes has quit IRC20:15
dmsimardweb interface is working for me right now20:16
dmsimardbut there was a definite drop in RAM usage, maybe the scheduler restarted ?20:16
dmsimardcorvus: ^20:17
mwhahahamust be nice, i'm still getting 50320:17
dmsimardoh crap20:17
dmsimard[Mon Jan  8 19:55:28 2018] traps: zuul-web[26027] general protection ip:513ef4 sp:7f2f9a521798 error:0 in python3.5[400000+3a9000]20:17
CrayZeesame here20:17
dmsimard[Mon Jan  8 19:55:40 2018] traps: zuul-scheduler[25965] general protection ip:7f1ffbfbe746 sp:7f1fadff8718 error:0 in libc-2.23.so[7f1ffbf33000+1c0000]20:17
dmsimardclarkb, fungi, corvus: msgpack failure propagated to zuulv3.o.o just now20:18
dmsimardmodules were updated not long ago http://paste.openstack.org/raw/641017/20:18
dmsimardmodule update timestamps correlate with the gpf20:19
dmsimardinfra-root: unless someone wants to investigate why this has happened, I'll hotfix like zm and ze yesterday20:20
fungii wonder if upgrading/rebuilding linked c extensions underneath a running python is unsafe20:20
dmsimardfungi: the msgpack rename has to have something to do with it20:20
dmsimardhotfixing20:20
dmsimardzuul-web and zuul-scheduler have been started20:22
*** Goneri has joined #openstack-infra20:22
CrayZeedmsimard: +1 - working on my side20:22
dmsimardI'm seeing a lot of those errors in the zuulv3.o.o logs: http://paste.openstack.org/raw/641019/20:24
dmsimardzuulv3.o.o seems to still have all the ongoing jobs listed... really ?20:24
dmsimardhmm, now I realize that it was pending scheduler reload -- should have taken the opportunity to dump the queues20:26
*** edmondsw has quit IRC20:26
*** beagles has joined #openstack-infra20:27
dmsimardfungi: is this okay ? #status notice The jobs and queues in Zuul between 19:55UTC and 20:20UTC have been lost after recovering from a crash, you might need to re-check your patches if they were being tested during that period.20:32
fungidmsimard: sure, good enough20:38
fungii sometimes mention reapplying approvals, but that's long enough prose already ;)20:38
fungidmsimard: you likely also want to #status log a summary of the actions you took on the server20:38
fungifor the benefit of our sysadmins in other timezones20:38
dmsimard#status log (dmsimard) the msgpack issue experienced yesterday on zm and ze nodes propagated to zuulv3.o.o and crashed zuul-web and zuul-scheduler with the same python general protection fault. They were started after re-installing msgpack but the contents of the queues were lost.20:38
openstackstatusdmsimard: finished logging20:38
dmsimardwas already on it :)20:38
fungiperfect!20:38
*** jamesmcarthur has joined #openstack-infra20:38
dmsimard#status notice The jobs and queues in Zuul between 19:55UTC and 20:20UTC have been lost after recovering from a crash, you might need to re-check your patches if they were being tested during that period.20:38
openstackstatusdmsimard: sending notice20:38
dmsimardbrb20:38
*** openstack has quit IRC20:38
*** openstack has joined #openstack-infra20:40
*** ChanServ sets mode: +o openstack20:40
pabelangerSpamapS: Yup, hopefully can rebase that today and push it up20:43
SpamapSpabelanger: rebasing it is not easy. I suggest manually re-doing the patch.20:44
SpamapSpabelanger: the bits have changed too much since I did it.20:44
SpamapSgit can't figure it out.20:44
pabelangerSpamapS: ack20:44
openstackgerritAntoine Musso proposed openstack-infra/zuul master: zuul-cloner: recognizes bare repos in cache dir  https://review.openstack.org/24920720:45
toskythe last message from statusbot was sent on twitter as usual, but it was split; I guess that the bot plugin that handles twitter should be updated to support the 280 character tweets20:47
pabelangerfungi: looks like git servers are working again!20:50
fungiyup. thanks for the revert20:51
pabelangerhttps://review.openstack.org/531837/ and https://review.openstack.org/531401 could also use a review to help get automated updates applied to centos20:52
*** jamesmcarthur has quit IRC20:54
*** jamesmcarthur has joined #openstack-infra20:54
Shrewstosky: depends on python-twitter lib. looks like we're waiting for 3.3.1 to be released: https://github.com/bear/python-twitter/pull/52520:55
fungiyeah, ttx was going to patch statusbot to support long tweets until i pointed out that we need a new python-twitter supporting the protocol change first20:57
toskyShrews: ah,good to know20:57
fungieasy enough to fix once the lib has support20:57
*** jtomasek has quit IRC20:58
openstackgerritMerged openstack-infra/project-config master: Add charm-interface-designate project  https://review.openstack.org/51733621:01
openstackgerritAntoine Musso proposed openstack-infra/zuul master: Add __repr__ to a few classes  https://review.openstack.org/36106421:01
*** openstackgerrit has quit IRC21:03
*** CrayZee has left #openstack-infra21:03
*** dprince has quit IRC21:06
*** dhajare has quit IRC21:07
*** smatzek has quit IRC21:11
*** smatzek has joined #openstack-infra21:11
*** jamesmcarthur has quit IRC21:12
*** rhallisey has quit IRC21:14
*** smatzek has quit IRC21:16
*** rcernin has joined #openstack-infra21:17
*** openstackgerrit has joined #openstack-infra21:18
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP: Support cross-source dependencies  https://review.openstack.org/53080621:18
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove updateChange history from github driver  https://review.openstack.org/53190421:18
openstackgerritMonty Taylor proposed openstack-infra/jeepyb master: Add checking for PyPI project ownership  https://review.openstack.org/53189821:19
openstackgerritIhar Hrachyshka proposed openstack-infra/devstack-gate master: Switch from lib/neutron-legacy to lib/neutron  https://review.openstack.org/43679821:19
openstackgerritMonty Taylor proposed openstack-infra/jeepyb master: Add checking for PyPI project ownership  https://review.openstack.org/53189821:20
clarkbfungi: so you think the compile process for linking against python may trip up running python processes?21:22
*** gouthamr has quit IRC21:22
dmsimardWhat makes it so pip tries to get a package that isn't yet on the mirror ? There's a lot of "No matching distribution found" for various packages (it's our most popular elastic-recheck item)21:22
dmsimardFor example, here we see a failure getting os-brick==1.15.5 @ 2018-01-08 16:59:21 http://logs.openstack.org/36/531836/1/check/legacy-grenade-dsvm-neutron-multinode/f84f74d/logs/grenade.sh.txt#_2018-01-08_16_59_21_95621:23
clarkbdmsimard: some of it is "normal" iirc osa or something tries to install a package that was deleted from pypi on a stable branch21:23
dmsimardAnd Bandersnatch recovers it ~3 minutes before that: 2018-01-08 16:56:40,050 INFO: Downloading: https://pypi.python.org/packages/37/29/820cdc09fec4701a615cf4293f1dbfbfa5b5e12ba4bcd1949b4a660b4d31/os-brick-1.15.5.tar.gz21:23
clarkbdmsimard: so one case is when pypi deletes a package so you can no longer satisfy the requirement(s)21:23
dmsimardclarkb: the couple cases I've isolated were all "legit" like the one above21:24
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add memory awareness to system load governor  https://review.openstack.org/50896021:25
clarkbdmsimard: that is interesting, looks like that release came out today so likely a race between updating constraints and updating our mirror?21:25
dmsimardI can't find a reference to os-brick==1.15.5 in openstack/requirements21:26
clarkbdmsimard: I think releases push constraints updates and if someone manages to merge that constraint update before our mirror update pulls it in that could happen21:26
dmsimardbut it might just be me looking at the wrong place21:26
clarkbwe might also push the constriant update before we actually publish to pypi21:26
clarkbwhich could be another source of racing21:26
* clarkb looks at zuul config21:26
dmsimardclarkb: that's exactly the kind of thing I was expecting to see and fix21:26
*** Anticimex has joined #openstack-infra21:27
dmsimardwell, I'm not sure how fixable it is -- the commit will always be merged before the post job (that publishes to pypi) runs I would guess21:27
*** r-daneel has joined #openstack-infra21:27
clarkbpropose-update-constraints depends on release-openstack-python21:27
clarkbdmsimard: the commit/tag to make a release is what triggers the job to make a new ocmmit to update constraints21:28
*** david-lyle has quit IRC21:28
clarkbpublish-to-pypi is the template in ozj21:28
* dmsimard looks21:28
openstackgerritMonty Taylor proposed openstack-infra/jeepyb master: Add checking for PyPI project ownership  https://review.openstack.org/53189821:29
dmsimardwell, I found the propose-constraints for os-brick (thanks zuul dashboard) http://logs.openstack.org/b8/b8bb0ab8b33d67786c3673b3de29be4ed68d4ee5/release/propose-update-constraints/7f4e9b4/21:29
*** aeng has joined #openstack-infra21:30
dmsimardfrom https://review.openstack.org/53183621:30
fungiclarkb: we discussed maybe having the constraints update job wait until it could find the package on the mirror, but nobody's worked on solving the race yet. requirements reviewers just recheck it21:30
dmsimardwait that's not merged yet o_O21:30
*** kgiusti has left #openstack-infra21:30
openstackgerritMonty Taylor proposed openstack-infra/system-config master: Add PyPI settings for jeepyb  https://review.openstack.org/53190921:31
dmsimardhah, bummer. The errors for os-brick seem to be all coming from that propose-constraints patch.21:31
clarkbdmsimard: ok so those are legit fails but its failing in a way that is good :) eg preventing us from merging something that would break21:31
clarkbI think that probably indicates our pypi mirroring may be broken21:32
dmsimardfungi: seems like an opportunity to get an ansible retry/wait going21:32
clarkbdmsimard: mirror-update.openstack.org is the host that updates pypi and other mirrors. It does so out of cron21:32
dmsimardyeah, already looked at the bandersnatch logs to see if there was anything unusual21:32
clarkbpabelanger: I don't see a cron entry for pypi on ^21:32
clarkbdoes it rn as not root /me checks21:33
dmsimardit does21:33
*** rcernin has quit IRC21:33
pabelangerclarkb: checking21:33
clarkbah ok21:33
dmsimard*/5 * * * * flock -n /var/run/bandersnatch/mirror.lock bandersnatch-mirror-update /var/log/bandersnatch/mirror.log21:33
clarkbdmsimard: the end of the log file seems to indicate it htinks it is happy21:33
clarkbdmsimard: it could be a bug on the pypi side21:34
pabelangerhttp://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/mirror_update.pp#n7121:34
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Run jeepyb-check-pypi on project-config patches  https://review.openstack.org/53191121:34
dmsimardclarkb: could it just be stale cache from the mirror/afs ?21:34
dmsimardthe package was downloaded by bandersnatch ~3 minutes before pip got a "404"21:34
pabelangerdmsimard: clarkb: bandersnatch looks to be running every 5mins or so, according to log21:35
mordredfungi, dhellmann, corvus: ^^ added a zuul job to the jeepyb patch and a patch to configure it to run on project-config changes - I think that should be about good for today21:35
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Correctly use project name in getGitUrl  https://review.openstack.org/52830921:35
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Initialize github auth in getGitUrl if needed  https://review.openstack.org/52831021:35
clarkbdmsimard: in that case it could be a bug in the only release afs when we need to check21:35
clarkbdmsimard: since a 404 likely made it fail, then next time we run we only check against the current run not previous runs21:36
*** hemna_ has joined #openstack-infra21:37
*** gouthamr has joined #openstack-infra21:37
clarkbya bandersnatch-mirror-update is set -e so if a bandersnatch run fails it won't check if it needs to sync21:39
openstackgerritJeremy Stanley proposed openstack-infra/zuul feature/zuulv3: Link to zuul-base-jobs docs from User's Guide  https://review.openstack.org/53191221:39
clarkbYou'd expect the next run would sync something though since the previous failed21:39
*** yamamoto has joined #openstack-infra21:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use configured github server in app mode  https://review.openstack.org/52831121:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Fix github app authentication in _getNeededByFromPR  https://review.openstack.org/52831221:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add the project to GithubUser  https://review.openstack.org/52831321:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Reprime the installation map in getGitUrl if needed  https://review.openstack.org/52950621:39
smcginnisclarkb: Is it possible it didn't update the index and now it needs a PURGE on that one?21:41
dmsimardclarkb: bandersnatch didn't get a 404, it's pip who did21:41
clarkbsmcginnis: it seems to hvae grabbed the package so I don't think so21:41
dmsimardpip fails to get os-brick==1.15.5, but it was downloaded by bandersnatch ~3 minutes prior so it's possible the mirror's AFS or Apache cache was stale21:42
clarkbdmsimard: I'm comparing timestamps. 16:56 is when bandersnatch grabbed it21:42
dmsimardyeah, and it failed at 16:5921:42
smcginnisI ran bandersnatch internally for a little over a year. Probably had about 3-4 times I had to run the PURGE thing.21:42
dmsimard(the pip in the job)21:42
clarkbdmsimard: 2018-01-08T16:59:52,888404332+0000 is when we synced it21:42
clarkbso thats the race there21:43
clarkbdmsimard: since the mirrors won't see it until the vos release21:43
clarkbit is interesting that it took almost an hour for bandersnatch to pick it up from when it was published to pypi21:45
clarkbbut we likely can't do much to speed that up as pypi drives those events21:45
dmsimardclarkb: pip doesn't query pypi from a nodepool node, does it ?21:45
dmsimardI mean, we're configuring it to query our mirrors ?21:45
clarkbdmsimard: you mean we don't use upstream pypi from our jobs? no they should mostly use our mirrors (but there are some exceptions)21:45
SamYaplelooking for review love https://review.openstack.org/#/c/517105/ bindep -- 2 months and counting21:46
dmsimardWhen I set up the configure-mirrors role in z-j, I don't remember setting up something for pypi.. wonder how that ends up being set up /me looks21:46
clarkbdmsimard: I'm not sure I understand21:46
clarkbyou juts mean how do we configure out mirrors?21:47
*** yamamoto has quit IRC21:47
dmsimardyeah21:47
clarkbah, it was part of the nodepool ready script stuff before zuulv3 but now its part of a very base job I think21:47
pabelangerit should be setup with configure-mirror role, I remember writing it for pip.conf21:48
dmsimardright, I'm the one who translated the mirror setup from readyscript to a role and I don't remember setting something up for pip21:48
dmsimardlooking at configure-mirror I don't see pip stuff either ..21:48
pabelangerhttp://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/configure-mirrors/tasks/mirror.yaml#n121:48
dmsimardwell, there it is21:49
dmsimardpabelanger: makes sense I don't remember writing it if it was you who wrote it :p21:49
pabelangerso, something is hitting pypi directly?21:50
*** slaweq has quit IRC21:50
pabelangerat one point we did that for pep8 jobs to test wheels building, not sure we kept that for zuulv3 migration21:50
dmsimardpabelanger: I don't think but I wanted to make sure -- what seems to be happening is that an index is referencing a package that hasn't yet been pushed21:51
dmsimardso pip tries to download it but it's not there yet21:51
clarkbya its definitely hitting our mirror, that is why the package doesn't exist yet21:51
clarkbits just racing bandersnatch + vos release21:51
*** smatzek has joined #openstack-infra21:52
pabelangerI thought index was only updated after vos release, to avoid this issue21:52
*** eharney has quit IRC21:53
dmsimardpabelanger: well, it's either that or the requirements jobs force that version (this particular case ocurred in a constraints update)21:53
clarkbpabelanger: the issue is we made a release of os-brick and then immediately push a change to requirements to bump constraints up to use it21:53
clarkbpabelanger: that change races our mirroring21:53
*** esberglu has quit IRC21:53
pabelangerclarkb: okay, that makes sense21:54
clarkbpabelanger: vos releasing ensures that we always publish a consistent pypi it does not guaruntee that it will be up to date21:54
pabelangeryah21:54
fungipabelanger: the wheel building deps test was that we skipped our custom wheel mirror and went straight to our bandersnatch-built pypi mirror21:54
funginot to global pypi21:55
*** Goneri has quit IRC21:55
fungiwe also, further back, used to have requirements test jobs use real pypi instead of our pypi mirror, mainly because of races (though that came from a time when we only maintained a partial mirror and so you couldn't otherwise test proposed additions which we weren't yet configured to add to the mirror)21:56
*** smatzek has quit IRC21:56
pabelangerspeaking of wheels, I guess we could have requirements job trigger building them again? Now that they are native zuulv3 jobs. Or actually, I think we want to wait for the enqueue job once into post pipeline patch for that21:57
*** trown is now known as trown|outtypewww21:58
dmsimardI'd like to try something in the propose-constraints job but it's running out of project-config so wouldn't be able to use depends-on :(21:58
fungii'd also like to see our wheel mirror stop building wheels which are already available from pypi/our pypi mirror21:59
pabelangerfungi: Yah, for the most part, it is only 30mins per wheel type now. But agree, would make the jobs much faster21:59
fungibecause we technically aren't testing how projects work with official wheels of deps since we host rebuilt ones and use those instead21:59
pabelangerthere was also a bug in zuul, that kept old branches around, so we end up building wheels for ocata22:00
clarkbfungi: that has saved us once or twice after pypi deletes a wheel but ya not ideal22:00
corvusit's zuul meeting time in #openstack-meeting-alt22:00
pabelangereven liberty22:00
fungiless about speed of building the mirror and more about that we're not testing what we think we are22:00
clarkbfungi: right, and while we may keep working no one else does making our software non deployable22:00
*** rkukura has quit IRC22:04
*** esberglu has joined #openstack-infra22:04
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Add support for a secure ZooKeeper configuration  https://review.openstack.org/53188222:05
*** rcernin has joined #openstack-infra22:06
*** jamesmcarthur has joined #openstack-infra22:08
openstackgerritClark Boylan proposed openstack-infra/nodepool feature/zuulv3: Clarify provider manager vs provider config  https://review.openstack.org/53161822:11
*** jamesmcarthur has quit IRC22:13
*** florianf has quit IRC22:18
openstackgerritIan Wienand proposed openstack/diskimage-builder master: [DNM] Support networkx 2.0  https://review.openstack.org/50652422:21
*** afred312 has quit IRC22:22
*** erlon has quit IRC22:24
*** e0ne has joined #openstack-infra22:28
*** rkukura has joined #openstack-infra22:31
*** dave-mccowan has quit IRC22:37
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Add ansible/ansible to zuul  https://review.openstack.org/50451022:38
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Run shade functional tests on ansible OpenStack PRs  https://review.openstack.org/53191622:38
*** armax has quit IRC22:40
*** wolverineav has quit IRC22:41
*** hongbin has quit IRC22:45
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Run shade functional tests on ansible OpenStack PRs  https://review.openstack.org/53191622:47
*** rlandy is now known as rlandy|bbl22:47
mordredcorvus, pabelanger: ^^ ... https://review.openstack.org/#/q/topic:turn-on-ansible has the whole thing22:48
*** e0ne has quit IRC22:49
*** david-lyle has joined #openstack-infra22:55
*** slaweq has joined #openstack-infra22:58
*** hashar has quit IRC22:58
*** slaweq has quit IRC23:00
*** afred312 has joined #openstack-infra23:00
*** gcb has joined #openstack-infra23:01
ianwhttps://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe <-- this had passed me by but is good23:04
mordredclarkb, fungi, pabelanger: https://review.openstack.org/#/c/504510 is safe to land right now- it'll only make ansible/ansible available in required-projects23:04
ianwi'll get to a dib release so we can try out fedora27 soon, could simplify a number of things longer term23:04
mordredianw: ZOMG. that's awesome!23:05
clarkbianw: looks like they are going the debian route of using /usr/local for pip23:05
mordredyah23:06
mordrednow if only debian would revert the dist-packages thing...23:06
clarkbfungi: pabelanger AJaeger looks like git0* are running puppet successfully now?23:06
openstackgerritMatthieu Huin proposed openstack-infra/nodepool feature/zuulv3: [WIP] webapp: add optional admin endpoint  https://review.openstack.org/53171823:06
* mordred is thrilled wit that fedora change and will need to email beers to someone23:06
clarkbmordred: your ansible/ansible change looks wrong to me. include: - job is global to the source and not per repo?23:07
clarkbbut also you have projects: under untrusted-projects:23:08
*** bobh has quit IRC23:09
clarkbkingbird-dashboard exists in gerrit now https://review.openstack.org/#/admin/projects/openstack/kingbird-dashboard,access23:10
*** jaypipes has quit IRC23:12
*** david-lyle has quit IRC23:12
mordredclarkb: that's defining a list of projects for-which to only load jobs - it's an etry that's basically {'projects': ['ansible/ansible'], 'include': ['jobs']}23:12
pabelangerclarkb: yah, we merged a fix for git servers23:12
mordreddmsimard: oh - https://review.openstack.org/#/c/504510 to you too23:13
clarkbmordred: it doesn't read well :/23:13
*** david-lyle has joined #openstack-infra23:13
pabelangerI need to step away for a bit, will catch up on backscroll23:14
mordredcorvus: ^^ I'm doing that right, yeah?23:14
clarkbmordred: I think the nested projects is what confuses me23:15
clarkbwe list projects at the top level but now there is a third type of project being listed under them23:15
clarkbalso does that mean we can't have a project called include?23:16
mordredclarkb: it does not - include is a key in the dict that's in the untrusted-projects list23:17
clarkbmordred: so we type check it?23:17
clarkbI guess in this case we'd hvae to23:17
mordredso - basically, untrusted-projects is a list that contains the string gtest-org/ansible and an anonymous dict that has the keys "include" and "project"23:18
mordredso - basically, untrusted-projects is a list that contains the string gtest-org/ansible and an anonymous dict that has the keys "include" and "projects"23:18
mordredclarkb: yah - there's a common pattern in the zuul config reading that is "the value here can be either a string or a dict"23:18
clarkbya I'm reading the voluptuous schema for it now23:19
*** gcb has quit IRC23:20
mordredthat has led to me look at what the yaml would look like if one of the entries of that list was a list ... it's weird :)23:20
corvusclarkb, mordred: i believe that's correct for an anonymous project group.23:21
mordredhttp://paste.openstack.org/show/641039/23:21
corvuswhich is, unfortunately, undocumented23:21
corvusthat's my bad, i will correct it23:22
*** sambetts is now known as sambetts|afk23:22
clarkbcorvus: mordred the thing I descirbe appears to be supported as well23:22
clarkbmy human readable preference would be for what I describe over the anonymous nested list of projects23:23
corvusclarkb: what's the thing you describe?23:23
clarkbcorvus: set the includes per project entry in untrusted-projects rather than have a nested list of projects23:23
clarkbproject_dict in the schema23:24
corvusclarkb: yes, that works too.23:24
mordredclarkb: but what about when we have 50 github projects and we only want to load jobs from each of them?23:24
clarkb(which is how I thought it had to be done but schema says both are valid)23:24
clarkbmordred: we don't have that problem yet and I think it will likely still be more readable in the non anonymous dict case23:25
clarkbat least for humans23:25
mordredmaybe it would make more sense when there are more than one and for now doing it as an include on the one project itself would be better23:25
corvusmordred: that sounds reasonable.23:25
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Add ansible/ansible to zuul  https://review.openstack.org/50451023:26
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Run shade functional tests on ansible OpenStack PRs  https://review.openstack.org/53191623:26
mordredclarkb, corvus: ^^23:26
clarkbcorvus: but ya I Think greatest source of confusion is likely the docs only doing the project_dict case and not the anonymous dict case23:27
corvus(also, ftr, "include: job" works as well)23:27
clarkb(so fixing that ++)23:27
*** dciabrin has joined #openstack-infra23:28
mordredcorvus: should I collapse it to include: job? since this is our first example in the config file for later cargo-culting?23:28
corvusmordred: maybe so?  that feels like a common case where brevity would be nice.23:28
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Add ansible/ansible to zuul  https://review.openstack.org/50451023:30
mordredk. there we go23:30
openstackgerritMonty Taylor proposed openstack-infra/project-config master: Run shade functional tests on ansible OpenStack PRs  https://review.openstack.org/53191623:31
mordredcorvus: wanna do the honors? :)23:32
corvusdone :)23:35
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP: Support cross-source dependencies  https://review.openstack.org/53080623:36
openstackgerritMerged openstack-infra/project-config master: Add ansible/ansible to zuul  https://review.openstack.org/50451023:38
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add job for testing against devel of ansible  https://review.openstack.org/53193423:43
mordredcorvus, clarkb: ^^ there's a similar patch for zuul itself23:43
*** felipemonteiro_ has quit IRC23:46
*** olaph has quit IRC23:49
*** dingyichen has joined #openstack-infra23:52
*** olaph has joined #openstack-infra23:53
*** tosky has quit IRC23:56
*** stakeda has joined #openstack-infra23:59

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