Wednesday, 2021-06-16

*** diablo_rojo is now known as Guest232600:47
*** marios is now known as marios|ruck05:04
*** rpittau|afk is now known as rpittau07:15
*** elodilles is now known as elodilles_afk08:10
*** gthiemon1e is now known as gthiemonge08:23
*** ykarel is now known as ykarel|lunch08:31
*** ysandeep|out is now known as ysandeep08:45
ttxlooking08:53
ttxyeah it's weird, can't find the source for the error. Maybe some temporary sync issue, rechecking09:03
ttxhmm, looks like we'll need fungi's help on this one. Summary being: puppet-panko temporarily had its puppet-release-jobs template removed, but now it's back to the same as the other puppet-* things, and yet it triggers a validation error that the others do not trigger at https://zuul.opendev.org/t/openstack/build/5bd631f96753468c9a74c3ce35db8c88/log/job-output.txt#2239409:38
*** ykarel|lunch is now known as ykarel09:38
opendevreviewHervé Beraud proposed openstack/reno master: Moving to OFTC  https://review.opendev.org/c/openstack/reno/+/79662210:05
hberaudttx: thanks10:11
*** jbadiapa is now known as jbadiapa|afk10:48
*** ykarel_ is now known as ykarel10:54
opendevreviewAndrey Kurilin proposed openstack/releases master: Release rally 3.3.0  https://review.opendev.org/c/openstack/releases/+/79663412:03
*** diablo_rojo__ is now known as diablo_rojo12:35
*** jbadiapa|afk is now known as jbadiapa12:35
*** elodilles_afk is now known as elodilles13:04
fungiERROR: openstack-infra/project-config/zuul.d/projects.yaml no release job specified for openstack/puppet-panko, one of ['publish-to-pypi'] needs to be included in ['puppet-openstack-check-jobs', 'puppet-openstack-module-unit-jobs', 'puppet-openstack-integration-jobs-scenario001', 'puppet-openstack-beaker-jobs', 'release-notes-jobs-python3'] or no release will be published13:55
fungithat?13:55
ttxyeah.. that error does not show on all the other puppet-* things despite them being similarly configured13:56
fungii guess the question is why that first list has only one element13:56
ttxthat message always was a bit hard to parse13:57
ttxwhy that first list has only one element, and why it works for all the others13:57
fungiso maybe somewhere in this function things are going strangely: https://opendev.org/openstack/releases/src/branch/master/openstack_releases/project_config.py#L178-L28413:58
hberaudI expected to see our job fixed once these changes would be reverted13:58
fungiin theory it should be matching this: https://opendev.org/openstack/releases/src/branch/master/openstack_releases/project_config.py#L156-L15913:59
hberaudyes https://opendev.org/openstack/project-config/src/branch/master/zuul.d/projects.yaml#L471114:00
fungiis release_type not set correctly for that project?14:00
ttxyeah, and again, it works ok with puppet-ovn which is executed just before and is configured exactly the same. That's why i was thinking the git repo was stuck at a previous state14:00
hberaudgood question14:00
ttxlike the project-config checkout used in the job is stuck to teh pre-revert version14:01
ttx(i.e. before https://review.opendev.org/c/openstack/project-config/+/793891 merged to restore the config)14:02
fungithis is what should detect it's puppet: https://opendev.org/openstack/releases/src/branch/master/openstack_releases/cmds/validate.py#L689-L69014:02
hberaudfungi: puppet-panko and puppet-ovn seems to be configured the same14:02
fungiso puppetutils.looks_like_a_module() is probably returning false14:02
fungilooks like that conditional chain defaults to python if everything falls through, which looks like what we're seeing in the log14:03
fungihttps://opendev.org/openstack/releases/src/branch/master/openstack_releases/puppetutils.py#L19-L2614:04
fungii'm going to bet if i go looking i'll find most of the puppet files have been deleted from the master branch14:05
ttxhah14:05
ttxcould be, since it was retired14:06
hberaudgood catch https://opendev.org/openstack/puppet-panko/14:08
hberaudwe pass the repo.name to this function, so, maybe we could use it to determine the deliverable type too... at least temporarly and to avoid to revert the repo abandon14:13
ttxis the need temporary?14:13
hberaudnope you're right14:14
hberaudUVWX will follow the same path14:14
hberaudat least14:14
ttxwe should hit that "   if repo.is_retired:"14:17
ttxhttps://opendev.org/openstack/releases/src/branch/master/openstack_releases/project_config.py#L19514:17
ttxand therefore skip it14:18
ttxso maybe the solution is just to add "retired" in the repo flags14:20
ttxlet me try that14:21
opendevreviewHervé Beraud proposed openstack/releases master: Adding more way to determine the deliverable type  https://review.opendev.org/c/openstack/releases/+/79668314:23
hberaudfungi, ttx: ^14:23
ttxI don;t think that's necessary14:23
hberaudok14:24
ttxWe have a test in there for retired repos14:24
ttxwe just failed to flag puppet-panko as retired14:24
opendevreviewThierry Carrez proposed openstack/releases master: Puppet OpenStack: Create final stable/train release  https://review.opendev.org/c/openstack/releases/+/79282014:24
ttxI bet that case happened in the past and that was the solution for it14:24
hberaudI see14:25
ttxIf that works ^ we should probably put that flag into puppet-panko for UVWX14:25
hberaudyes14:25
hberaudIf That work that's the right solution to follow14:26
fungidoes it also merit mentioning in the project-team-guide section on project deprecations and retirements?14:27
hberaudYes14:28
hberaudCan't hurt14:28
hberaudttx: As long as we are there can you have a look too => https://review.opendev.org/c/openstack/releases/+/79645614:29
hberauds/too/to14:29
ttxhaha, good catch14:30
ttxwondering if we could have a test case checking that14:31
opendevreviewMerged openstack/releases master: Push validations-common 1.2.0 min version  https://review.opendev.org/c/openstack/releases/+/79624314:31
hberauda so tiny change with possibly so huge impacts14:31
hberaudyes that can't hurt14:31
ttxbasically what you did in 796485, but as a test case14:32
hberaudYes I'll have a look14:32
ttxok commented to that effect14:33
ttxIf the test framework makes it super hard to test, we can just merge this... but it feels like it should be able to cover it14:33
hberaudsure14:33
hberaudthanks for the comment14:33
*** gthiemon1e is now known as gthiemonge14:37
*** ykarel is now known as ykarel|away14:39
hberaud\o/ that worked14:43
hberaudfungi, ttx: https://review.opendev.org/c/openstack/project-team-guide/+/79668714:51
opendevreviewHervé Beraud proposed openstack/releases master: retire panko  https://review.opendev.org/c/openstack/releases/+/79668914:58
opendevreviewHervé Beraud proposed openstack/releases master: retire puppet-panko  https://review.opendev.org/c/openstack/releases/+/79669015:05
opendevreviewRico Lin proposed openstack/releases master: Release yaql 1.1.4  https://review.opendev.org/c/openstack/releases/+/79669215:06
opendevreviewHervé Beraud proposed openstack/releases master: retire panko and python-pankoclient  https://review.opendev.org/c/openstack/releases/+/79668915:25
opendevreviewMerged openstack/releases master: Puppet OpenStack: Create final stable/train release  https://review.opendev.org/c/openstack/releases/+/79282015:33
opendevreviewHervé Beraud proposed openstack/releases master: Fix validation to ensure that first release of series isn't a bugfix  https://review.opendev.org/c/openstack/releases/+/79645615:36
opendevreviewMerged openstack/reno master: Moving to OFTC  https://review.opendev.org/c/openstack/reno/+/79662215:38
*** marios|ruck is now known as marios|out15:45
hberaudfungi: We just experienced a new SSH issue in one job https://zuul.opendev.org/t/openstack/build/1815e820706347478ac24f7af132d33f I think that we need to reenqueue this job http://lists.openstack.org/pipermail/release-job-failures/2021-June/001541.html15:58
opendevreviewAndrey Kurilin proposed openstack/releases master: Release rally 3.3.0  https://review.opendev.org/c/openstack/releases/+/79663416:08
*** rpittau is now known as rpittau|afk16:11
fungihberaud: thanks, i'll take a look in a moment16:17
hberaudfungi: sure, thanks16:17
fungilooks like the recent ssh host key conflict failures have been in rackspace, they must be struggling with rogue virtual machines in their network again16:20
fungihberaud: i don't think we can reqnqueue that one, it failed after building and publishing release artifacts to tarballs.o.o and puppetforge... it didn't hit the error until it was collecting logs at the end of the job16:23
hberaudAh I see16:23
*** ricolin_ is now known as ricolin17:49
opendevreviewMerged openstack/releases master: [trove] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79568218:20
opendevreviewMerged openstack/releases master: [designate] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565018:48
opendevreviewMerged openstack/releases master: [freezer] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79565118:50
opendevreviewMerged openstack/releases master: [zaqar] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79568618:54
opendevreviewMerged openstack/releases master: [vitrage] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79568318:56
opendevreviewMerged openstack/releases master: [tacker] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/79567818:59
*** diablo_rojo is now known as Guest244621:51
*** diablo_rojo is now known as Guest245723:20

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!