01:06 <bdbaddog> @tardyp: Just forwarded the eamil directly to you from hover.

01:36 <flx[m]> how can I make the libvirt qemu worker over ssh working?

01:37 <flx[m]> my worker configuration looks like this:

01:37 <flx[m]> worker.LibVirtWorker('libvirt-worker', 'testpw', uri="qemu+ssh://<user>@<domain>:<port>/system", hd_image='/home/buildbot/minion1', base_image='/home/buildbot/base_image')

01:37 <flx[m]> buildbot shows the libvirt worker as offline

01:38 <flx[m]> though it starts

01:48 <flx[m]> Foxboron: thanks for sharing your configs :)

08:30 <Foxboron> flx[m]: nps :)

08:31 <cmouse> flx[m]: well, a latent worker is offline until it starts

08:31 <cmouse> for bb, a worker is something actively running BuildbotWorker

09:34 <flx[m]> Oh well

09:39 <flx[m]> cmouse: I think buildbot should show somewhere that the vm host is up and running. So you have a list of running nodes and it's also a confirmation for "configuration works".

09:40 <cmouse> flx[m]: i'm sure pull requests for this are welcome

09:50 <flx[m]> Is the libvirt/SSH connection permanent? Or does the master only connect to libvirt when a command should be issued and then it's closed again?

09:51 <cmouse> latter.

09:51 <cmouse> it's considered as "api endpoint"

09:52 <flx[m]> Hm, that makes it harder

09:55 <flx[m]> Well, we could just let the master connect frequently and see if that works

09:56 <flx[m]> As a keepalive

09:56 <flx[m]> On the other side, any reason why the connection is not permanent?

09:58 <cmouse> why would it be permanent?

10:19 <flx[m]> I don't know. I'm just thinking about what would make sense.

10:21 <flx[m]> What does buildbot use for SSH? The Python paramiko library or the native SSH implementation?

10:29 <mjw> Hi, I tried to subscribe to subscribe to devel@buildbot.net to discuss an issue we are seeing with our buildbot instance and show how we are working around it.

10:30 <mjw> But neither my subscription request, nor my email seem to have arrived at the list.

10:30 <mjw> Here is a CC to our own mailinglist:

10:30 <mjw> https://sourceware.org/pipermail/buildbot/2022q2/000014.html

10:34 <cmouse> mjw: you could try opening that as pull request on https://github.com/buildbot/buildbot ?

10:36 <mjw> cmouse, sorry, don't have a github account.

10:36 <mjw> Part of the reason to use buildbot is precisely so we don't have to rely on corporate controlled proprietary services :)

10:41 <cmouse> "oh well"

10:42 <cmouse> lets hope some bb dev picks it up from irc then

10:42 <mjw> will do!

10:43 <mjw> BTW. I am really impressed by buildbot.

10:43 <mjw> We have been running our instance for a couple of months now, doing 150+ builds a day. And this was the only issue we encountered.

10:44 <mjw> and it was only noticeable after some weeks.

10:55 <mjw> O, you can also pull it from my server if you want:

10:55 <mjw> https://code.wildebeest.org/git/user/mjw/buildbot/commit/?h=docker-py-close