Re: Freeze break request: kernel builders
On Thu, 1 Sept 2022 at 14:58, Mikolaj Izdebski wrote: > On Thu, Sep 1, 2022 at 8:55 PM Kevin Fenzi wrote: > > > > So, last week I managed to break bkernel01 kernel builder (and we have > > been using just 02 since then). There were 2 issues: > > > > 1. I switched rawhide to use systemd-nspawn for isolation instead of > > chroot and this broke kernel builds due to ( > > https://github.com/rpm-software-management/mock/issues/140 ) > > > > 2. pesign in f36 had some issues with unlocking the smart cards. > > ( https://bugzilla.redhat.com/show_bug.cgi?id=2122777 ) > > > > The pesign maintainers fixed issue 2 this morning and I tested the > > workaround I have for issue 1 in mock on bkernel01. > > > > So, what I would like to do now is: > > > > * upgrade bkernel02 to the same pesign version as on 01 along with > > moving it to f36 (like 01 is). > > * Push a commit in ansible to adjust mock config for the workaround for > > issue 1 above. > > > > +1s or further questions? > > +1 > > +1 also thanksl > > > > kevin > > ___ > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Freeze Break Request: Increase mailman to 8 CPU
On Thu, Sep 1, 2022 at 8:16 PM Stephen Smoogen wrote: > > > I am trying to deal with some crashing issues with the mailman. It is > currently at 100% CPU usage with 4 cpus and about 12-16 waiting services at > all times. I would like to increase the number of CPUs to 8. There does not > look to be memory problems at this time so no increase is needed there. > > Actions: > update ansible > update vm system via virsh > reboot vm +1 > > -- > Stephen Smoogen, Red Hat Automotive > Let us be kind to one another, for most of us are fighting a hard battle. -- > Ian MacClaren > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Freeze break request: kernel builders
On Thu, Sep 1, 2022 at 8:55 PM Kevin Fenzi wrote: > > So, last week I managed to break bkernel01 kernel builder (and we have > been using just 02 since then). There were 2 issues: > > 1. I switched rawhide to use systemd-nspawn for isolation instead of > chroot and this broke kernel builds due to ( > https://github.com/rpm-software-management/mock/issues/140 ) > > 2. pesign in f36 had some issues with unlocking the smart cards. > ( https://bugzilla.redhat.com/show_bug.cgi?id=2122777 ) > > The pesign maintainers fixed issue 2 this morning and I tested the > workaround I have for issue 1 in mock on bkernel01. > > So, what I would like to do now is: > > * upgrade bkernel02 to the same pesign version as on 01 along with > moving it to f36 (like 01 is). > * Push a commit in ansible to adjust mock config for the workaround for > issue 1 above. > > +1s or further questions? +1 > > kevin > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Freeze break request: kernel builders
So, last week I managed to break bkernel01 kernel builder (and we have been using just 02 since then). There were 2 issues: 1. I switched rawhide to use systemd-nspawn for isolation instead of chroot and this broke kernel builds due to ( https://github.com/rpm-software-management/mock/issues/140 ) 2. pesign in f36 had some issues with unlocking the smart cards. ( https://bugzilla.redhat.com/show_bug.cgi?id=2122777 ) The pesign maintainers fixed issue 2 this morning and I tested the workaround I have for issue 1 in mock on bkernel01. So, what I would like to do now is: * upgrade bkernel02 to the same pesign version as on 01 along with moving it to f36 (like 01 is). * Push a commit in ansible to adjust mock config for the workaround for issue 1 above. +1s or further questions? kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Freeze Break Request: Increase mailman to 8 CPU
On Thu, Sep 01, 2022 at 02:16:03PM -0400, Stephen Smoogen wrote: > I am trying to deal with some crashing issues with the mailman. It is > currently at 100% CPU usage with 4 cpus and about 12-16 waiting services at > all times. I would like to increase the number of CPUs to 8. There does not > look to be memory problems at this time so no increase is needed there. > > Actions: > update ansible > update vm system via virsh > reboot vm +1 here. kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Freeze Break Request: Increase mailman to 8 CPU
I am trying to deal with some crashing issues with the mailman. It is currently at 100% CPU usage with 4 cpus and about 12-16 waiting services at all times. I would like to increase the number of CPUs to 8. There does not look to be memory problems at this time so no increase is needed there. Actions: update ansible update vm system via virsh reboot vm -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
