Monday, 2022-05-09

opendevreviewIan Wienand proposed openstack/project-config master: Add opendev/infra-vhd-util-deb repository  https://review.opendev.org/c/openstack/project-config/+/84105400:59
*** ysandeep|out is now known as ysandeep|rover04:58
dpawlikgmann: pong ;)05:55
*** soniya29 is now known as soniya29|ruck06:13
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Handle exception: TOO_MANY_REQUESTS  https://review.opendev.org/c/openstack/ci-log-processing/+/84106806:56
*** soniya29 is now known as soniya29|ruck06:58
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Handle exception: TOO_MANY_REQUESTS  https://review.opendev.org/c/openstack/ci-log-processing/+/84106807:00
*** soniya29 is now known as soniya29|ruck07:19
*** ysandeep|rover is now known as ysandeep|rover|lunch07:20
*** jpena|off is now known as jpena07:30
*** soniya29 is now known as soniya29|ruck07:38
tkajinamhello. I've seen a few job failure caused by an issue with name resolution. does anybody have idea about this ? https://zuul.opendev.org/t/openstack/build/be7045d94cdd4c82898e787ed61c38b4/log/job-output.txt#2228-223207:43
tkajinamthe same job passed previously in the same repo and I suspect something specific to some regions07:43
tkajinamsorry, not in the same repo but in a different repo07:43
tkajinameg. https://zuul.opendev.org/t/openstack/build/4d33248b434448dfa0d551c215c0f4ff07:44
*** soniya29|ruck is now known as soniya29|ruck|lunch07:57
*** soniya29|ruck|lunch is now known as soniya29|ruck08:23
*** ysandeep|rover|lunch is now known as ysandeep|rover08:23
*** rlandy|out is now known as rlandy10:24
*** dviroel_ is now known as dviroel\11:14
*** dviroel\ is now known as dviroel11:14
fungitkajinam: i agree, it looks like some sort if name resolution problem from that node. resolv.conf seems to have a correct entry pointing to localhost, but unbound.log is empty in both the broken and working examples so i can't draw much of a conclusion from that, and i don't see anything relevant for it in syslog either11:49
*** ysandeep|rover is now known as ysandeep|rover|break11:57
*** ysandeep|rover|break is now known as ysandeep|rover12:57
*** dasm|off is now known as dasm13:27
*** soniya29 is now known as soniya29|ruck14:06
*** soniya29|ruck is now known as soniya29|ruck|dinner14:54
dpawlikianw, fungi, clarkb: hey, is it possible to release new diskimage builder? 15:06
dpawlikThis patch https://review.opendev.org/c/openstack/diskimage-builder/+/840825 will be good to be included in official release15:06
dpawlikof course if it is possible15:06
*** dviroel is now known as dviroel|lunch15:10
fungidpawlik: yeah, usually ianw tags dib releases, though i can if it's too urgent to wait for apac daylight hours. looks like that change and an adjustment to the containerfile testing are the only things which have merged since 3.20.0, so it could be a 3.20.1 patch release15:10
dpawlikfungi: if it wasn't a problem, I would like to ask you to release it... but if you are busy, it can wait :) 15:13
fungii have a meeting coming up momentarily, but can look at doing it after 16:30 utc15:14
clarkbI think 3.21.0 was planned15:14
clarkbbut I need to pull the code and chck outstanding changes15:15
dpawlikso maybe let's wait for  ianw15:15
clarkbyes 3.21.0 has already happened15:16
fungier, 3.21.0 already happened; i meant 3.21.115:16
clarkblooking at https://review.opendev.org/c/openstack/diskimage-builder/+/840825 I don't think the change is bad, but I think users of the base images that tell cloud init to not genrate keys should speak upstream and have them correct that15:17
clarkbits bad for base images to have baked in keys beacuse then all the hosts havethe same key. Therefore they shouldn't ship with keys and toggle the option to generate at boot15:18
dpawlikclarkb: IIUC the key will be generate after first boot...15:20
clarkbdpawlik: yes the change above forces that to happen because your base image cloud-init config apparently does not do this. I'm saying that is likely a bug in your base image and you should consider talking to them about it15:21
clarkbits fine to workaroudn that in dib, but its always good to pushes fixes as far up as possible to fix things for as many people as possible15:21
dpawlikclarkb: now I get. Yeah, I agree. This one seems to be a workaround. Maybe Tengu report/ask other communities if they can fix that... 15:24
Tenguoh, that terrible cloud-init addition blocking the actual sshd-keygen.service?15:28
clarkbwell the commit says that some base images have a cloud init config that prevents generating new keys. That is a bug imo for most cloud init installations15:30
clarkbbecause baking host keys into an image is a bad idea. And if you don't bake keys in and don't generate them on startup ssh won't work15:30
clarkbthe only place it makes sense is if you are intentionally disabling ssh15:30
*** soniya29|ruck|dinner is now known as soniya29|ruck15:36
Tenguclarkb: the issue surfaced in the rdo provided image. The cloud-init config was removing the existing keys, but the generation was disabled - probably because it was expecting the sshd-keygen.service to kick in.15:37
Tengubut starting with cloud-init-22, they actually disabled the sshd-keygen.service with a Condition...15:37
Tenguso it wasn't working anymore.15:37
clarkbright so that would be a bug in their image. We can fix it in dib thats fine. but rdo shoudl fix it too15:37
TenguI've checked the officials CentOS images, and they were cleaned.15:38
Tengusure. but at that time, we needed an actual fix. And ensuring within DIB things were correct wasn't a bad option. BUT... apparently the cloud-init element isn't used in tripleo X(15:38
Tenguwhich is "a bit annoying".15:38
Tengunot sure how rdo got that config in, if they just took a pretty old image and didn't update it for instance.15:39
Tenguhence https://review.opendev.org/c/openstack/tripleo-common/+/84106715:39
Tengu(for the element addition - it needs proper testing)15:39
*** ysandeep|rover is now known as ysandeep|out16:09
*** soniya29|ruck is now known as soniya29|out16:12
*** dviroel|lunch is now known as dviroel16:24
fungimmm, so just to confirm, tagging dib 3.21.1 won't immediately solve the problem for tripleo because that element isn't used?16:40
clarkboh they may be relying on the base image's config and not mixing in the element? ya so maybe we just wait on ianw then?16:42
*** jpena is now known as jpena|off17:17
*** dviroel is now known as dviroel|afk20:43
ianwo/ sorry for delay ... reading21:13
ianwdid we end up that tripleo doesn't use it anyway and a dib release won't help?  21:16
fungiianw: i think Tengu and dpawlik would need to confirm that for certain. seems like maybe they want to use it, in which case they'll need that eventually21:32
ianwi can just do a 3.21.1 release, doesn't seem we need to bump nodepool or anything then21:51
fungii don't think so, no, since it doesn't seem likely to be a change which would affect most known nodepool users21:57
*** rlandy is now known as rlandy|bbl22:13
opendevreviewMerged openstack/project-config master: Add opendev/infra-vhd-util-deb repository  https://review.opendev.org/c/openstack/project-config/+/84105422:14
*** dasm is now known as dasm|off22:16
*** cloudnull8 is now known as cloudnull23:04
opendevreviewIan Wienand proposed openstack/openstack-zuul-jobs master: [wip] add generic infra-deb package build role  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/84117723:44
opendevreviewIan Wienand proposed openstack/openstack-zuul-jobs master: [wip] add vhd-util job  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/84117823:58

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