Wednesday, 2024-05-29

opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_masakari master: Add tag to enable targeting of post-install config elements only  https://review.opendev.org/c/openstack/openstack-ansible-os_masakari/+/91969007:02
noonedeadpunkwhat do we need to land before branching actually?07:11
noonedeadpunkI see like ironic and trove patches for qmanager kinda07:11
noonedeadpunkaha, rabbitmq flags07:14
andrewbonneyI think those and ideally the k8s related ones assuming we can get through the capi job which jrosser is still investigating intermittent fails for07:14
jrossernoonedeadpunk: I had one query on the trove patch too07:16
noonedeadpunkyep, answered it07:16
noonedeadpunkguestagent is kinda amphora thing for trove07:16
jrossergreat will look again shortly07:16
noonedeadpunkso it runs on a vm07:16
jrosseraah ok07:17
noonedeadpunkunless I'm very wrong about something07:17
jrosserbut the service end also needs to connect to its different mq?07:17
noonedeadpunkok, that is a good point actually07:18
jrosserthat’s what I was thinking that for trove there might be two totally separate mq? and we use the same shm07:18
noonedeadpunkyeah07:18
noonedeadpunkbut.... how we did that07:19
noonedeadpunkhuh07:22
noonedeadpunkhow that worked lol07:22
noonedeadpunkbut it apparently did as I had trove back then deployed and working07:24
noonedeadpunkI'm gonna deploy trove in some poc very shortly, so will extra test this different rabbit part....07:43
noonedeadpunkso yeah, it could be worth to have a different hostname for guestagent just in case....07:47
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_trove master: Define unique hostname for QManager  https://review.opendev.org/c/openstack/openstack-ansible-os_trove/+/92045507:50
jrosserif it turns out to be wrong in some way it's only a config override needed to fix it until we can patch a bug07:52
jrosseris this made more complicated by the need for a 2nd rabbit instance being optional07:53
* jrosser not really knowing if the shm/qmanager is per queue or per connection to rabbit07:54
noonedeadpunkI guess it's just a need of 2nd rabbit which makes it complicated07:54
noonedeadpunkso it's kinda per process thread07:54
noonedeadpunkso - connection 07:54
jrosserso if we have two things (services) on the same host using the same queue they still need unique shm07:55
jrosserwhich i guess is where this all started07:55
noonedeadpunkyeah07:58
andrewbonneyLooks like all CI is failing cloning keystone at the moment08:18
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Enable oslomsg_rabbit_queue_manager by default  https://review.opendev.org/c/openstack/openstack-ansible/+/92071508:19
noonedeadpunkdoh08:19
noonedeadpunkbut kinda how.... that should be coming from zuul?08:20
noonedeadpunkgit clone --filter=blob:none --quiet file:///openstack/src/opendev.org/openstack/keystone failing, yeah08:22
jrossernoonedeadpunk: its git safe dirs? fatal: detected dubious ownership in repository at '/openstack/src/opendev.org/openstack/keystone/.git10:54
jrosserTo add an exception for this directory, call: git config --global --add safe.directory /openstack/src/opendev.org/openstack/keystone/.git10:55
jrosseri wonder why this starts only now10:55
noonedeadpunkhuh10:56
noonedeadpunkI thought we were adding smth globally10:56
* noonedeadpunk still kinda away at event10:56
jrosserit's odd as it doesnt happen in the jammy upgrade job10:56
noonedeadpunkand kinda tough to reproduce locally10:57
noonedeadpunkso we have that I guess now: https://opendev.org/openstack/openstack-ansible/commit/efa153ea159af13ce5539e423371f2642c9592ef10:58
noonedeadpunkmaybe it needs to be more global now....10:58
jrosserthat would cover the metal jobs to make that more global10:59
jrosserbut lxc is whole other thing https://review.opendev.org/c/openstack/openstack-ansible/+/920715?tab=change-view-tab-header-zuul-results-summary10:59
jrosserhere we go https://github.com/git/git/commit/f4aa8c8bb11dae6e769cd930565173808cbb69c811:04
noonedeadpunkpf11:07
jrosseri think there was a point release of git for jammy yesterday11:07
noonedeadpunkthat would explain it all11:08
noonedeadpunkI wonder, if it woud make sense to do smth with zuul job of placing repos actually...11:08
jrosserstill for lxc when we do not build wheels that setting needs to be in all the service containers11:09
jrosserits a client setting rather than at the source of the repo11:09
noonedeadpunkyeah, true11:10
noonedeadpunkfor containers its indeed worse kinda11:10
noonedeadpunkI was just thinking that nodepool VM is still managed by zuul, so...11:11
noonedeadpunkbut yeah, won't help us11:11
jrosserwe can add a task in openstack_hosts perhaps11:12
jrosserand some variable11:12
noonedeadpunkI was thinking if we can kinda pass a client file with alredy existing vars...11:13
noonedeadpunkAs I assume we do bind map zuul prepared repos to containers?11:14
noonedeadpunksorry, I'm kinda brain-farting today11:14
jrosserthat right they are bind mount in /openstack to the same place in containers as on the host, i think11:16
jrosserso that the repo setup is identical between metal and lxc jobs11:16
jrosseri can try to make a patch later11:19
noonedeadpunkok, would be very much appreciated, as I'm on internal meetup for next 2 days, so really hard to do smth...11:23
fricklerthx for the pointer to the git update, seems kolla is affected, too12:39
jrosserfrickler: did you end up doing safe.directory = * ?15:22
jrosseri dont thing you can do safe.directory = /all/my/repos/*15:23
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Allow openstack_hosts role to configure git safe.directory entries  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075715:37
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Configure all directories to be safe for git clone in CI  https://review.opendev.org/c/openstack/openstack-ansible/+/92075815:42
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Do not mark all directories as safe for git clone by default  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075915:45
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Allow openstack_hosts role to configure git safe.directory entries  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075716:02
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Do not mark all directories as safe for git clone by default  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075916:03
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Do not mark all directories as safe for git clone by default  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075916:03
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Do not mark all directories as safe for git clone by default  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075916:26
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Allow openstack_hosts role to configure git safe.directory entries  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075716:50
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Do not mark all directories as safe for git clone by default  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92075916:50
fricklerjrosser: didn't look into a solution yet17:36
jrosseri ended up with brute force safe.directory = "*"17:36

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