FBR add getfedora.org redirects
Hello folks! I would like to submit a Freeze Break Request to add redirects[1] from getfedora.org to the new website[2] on fedoraproject.org. This will need to be applied during F38 launch on Tuesday. Can I get some +1s? [1]: https://pagure.io/fedora-infra/ansible/pull-request/1372 [2]: https://fedoraproject.org/ Thanks! -darknao ___ 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: FBR: add phsmoura to ability to ack/nack in nagios
+1 from me On Thu, Oct 20, 2022 at 8:09 PM Stephen Smoogen wrote: > > https://pagure.io/fedora-infra/ansible/pull-request/1232 > > -- > 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
FBR: add phsmoura to ability to ack/nack in nagios
https://pagure.io/fedora-infra/ansible/pull-request/1232 -- 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: FBR: DNS update
+1 from me. Thanks smooge On Thu, Sep 8, 2022 at 9:10 PM Kevin Fenzi wrote: > On Thu, Sep 08, 2022 at 11:27:16AM -0400, Stephen Smoogen wrote: > > Currently the ipv6for osuosl.org is not functioning and I would like to > > take them out of DNS. When looking at it, I found that the getfedora.org > > was in this state: > > ``` > > disable proxy09.fedoraproject.org > > disable proxy11.fedoraproject.org > > enable proxy11.fedoraproject.org > > disable proxy02.fedoraproject.org > > enable proxy02.fedoraproject.org > > disable proxy04.fedoraproject.org > > disable proxy06.fedoraproject.org > > enable proxy06.fedoraproject.org > > disable proxy13.fedoraproject.org > > enable proxy13.fedoraproject.org > > disable proxy03.fedoraproject.org > > enable proxy03.fedoraproject.org > > disable proxy12.fedoraproject.org > > enable proxy12.fedoraproject.org > > disable proxy01.iad2.fedoraproject.org > > disable proxy101.iad2.fedoraproject.org > > disable proxy101.iad2.fedoraproject.org > > ``` > > > > My change to the cmds files is to add proxy06.fedoraproject.org and > proxy09 > > to the disable list and remove all others from getfedora.org. Then > execute > > a change and cleanup. > > It's too bad we can't just disable them for ipv6, but leave them in for > ipv4. ;( > > Oh well, Hopefully it will be fixed soo. +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
Re: FBR: DNS update
On Thu, Sep 08, 2022 at 11:27:16AM -0400, Stephen Smoogen wrote: > Currently the ipv6for osuosl.org is not functioning and I would like to > take them out of DNS. When looking at it, I found that the getfedora.org > was in this state: > ``` > disable proxy09.fedoraproject.org > disable proxy11.fedoraproject.org > enable proxy11.fedoraproject.org > disable proxy02.fedoraproject.org > enable proxy02.fedoraproject.org > disable proxy04.fedoraproject.org > disable proxy06.fedoraproject.org > enable proxy06.fedoraproject.org > disable proxy13.fedoraproject.org > enable proxy13.fedoraproject.org > disable proxy03.fedoraproject.org > enable proxy03.fedoraproject.org > disable proxy12.fedoraproject.org > enable proxy12.fedoraproject.org > disable proxy01.iad2.fedoraproject.org > disable proxy101.iad2.fedoraproject.org > disable proxy101.iad2.fedoraproject.org > ``` > > My change to the cmds files is to add proxy06.fedoraproject.org and proxy09 > to the disable list and remove all others from getfedora.org. Then execute > a change and cleanup. It's too bad we can't just disable them for ipv6, but leave them in for ipv4. ;( Oh well, Hopefully it will be fixed soo. +1 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
FBR: DNS update
Currently the ipv6for osuosl.org is not functioning and I would like to take them out of DNS. When looking at it, I found that the getfedora.org was in this state: ``` disable proxy09.fedoraproject.org disable proxy11.fedoraproject.org enable proxy11.fedoraproject.org disable proxy02.fedoraproject.org enable proxy02.fedoraproject.org disable proxy04.fedoraproject.org disable proxy06.fedoraproject.org enable proxy06.fedoraproject.org disable proxy13.fedoraproject.org enable proxy13.fedoraproject.org disable proxy03.fedoraproject.org enable proxy03.fedoraproject.org disable proxy12.fedoraproject.org enable proxy12.fedoraproject.org disable proxy01.iad2.fedoraproject.org disable proxy101.iad2.fedoraproject.org disable proxy101.iad2.fedoraproject.org ``` My change to the cmds files is to add proxy06.fedoraproject.org and proxy09 to the disable list and remove all others from getfedora.org. Then execute a change and cleanup. -- 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: FBR: Add nb to PAGURE_ADMIN_USERS
+1 On Wed, Apr 27, 2022 at 10:28 PM Neal Gompa wrote: > On Wed, Apr 27, 2022 at 5:11 PM Nick Bebout wrote: > > > > I was working on a ticket mattdm filed about some spammers in Pagure. > I'd like to add myself to PAGURE_ADMIN_USERS and run the Pagure playbook. > > > > PR here: https://pagure.io/fedora-infra/ansible/pull-request/1048 > > > > +1 here > > -- > 真実はいつも一つ!/ Always, there's only one truth! > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: Add nb to PAGURE_ADMIN_USERS
On Wed, Apr 27, 2022 at 5:11 PM Nick Bebout wrote: > > I was working on a ticket mattdm filed about some spammers in Pagure. I'd > like to add myself to PAGURE_ADMIN_USERS and run the Pagure playbook. > > PR here: https://pagure.io/fedora-infra/ansible/pull-request/1048 > +1 here -- 真実はいつも一つ!/ Always, there's only one truth! ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: Add nb to PAGURE_ADMIN_USERS
I was working on a ticket mattdm filed about some spammers in Pagure. I'd like to add myself to PAGURE_ADMIN_USERS and run the Pagure playbook. PR here: https://pagure.io/fedora-infra/ansible/pull-request/1048 nb ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: update openshift ssl certs
On Wed, Apr 27, 2022 at 03:53:54PM +0100, Mark O'Brien wrote: > Hi All, > > The certs for our openshift 3 clusters in both stg and prod are out of > date. I have created new ones and I have a PR here to update the name in > ansible: > > https://pagure.io/fedora-infra/ansible/pull-request/1045# > > I will need to run the proxies playbook to deploy these as well. > > I have also updated the ocp stg certs which are due to expire next week. > > +1/-1's welcome +1 please. We should also make sure all of these are in nagios or otherwise let us know before they expire. 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: update openshift ssl certs
Hi All, The certs for our openshift 3 clusters in both stg and prod are out of date. I have created new ones and I have a PR here to update the name in ansible: https://pagure.io/fedora-infra/ansible/pull-request/1045# I will need to run the proxies playbook to deploy these as well. I have also updated the ocp stg certs which are due to expire next week. +1/-1's welcome Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: New IP for University of Southern Indiana mirror
This had the required +1's so I merged and ran it Mark On Tue, Mar 29, 2022 at 1:57 AM Nick Bebout wrote: > My mirror at USI will be becoming public and it's IP is changing. I'd > like to add the new IP and run the playbook. > > Can I get +1's for > https://pagure.io/fedora-infra/ansible/pull-request/1017 please? > > nb > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: New IP for University of Southern Indiana mirror
My mirror at USI will be becoming public and it's IP is changing. I'd like to add the new IP and run the playbook. Can I get +1's for https://pagure.io/fedora-infra/ansible/pull-request/1017 please? nb ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: update mirror ip addresses for kernel.org
Thanks all! Merged and run On Tue 22 Mar 2022, 15:45 Pierre-Yves Chibon, wrote: > On Tue, Mar 22, 2022 at 02:34:57PM +, Mark O'Brien wrote: > > Hi All, > > > > We have had a request from the people at mirrors.kernel.org to update > their > > IP address: https://pagure.io/fedora-infrastructure/issue/10598 > > > > This PR should take care of it > > https://pagure.io/fedora-infra/ansible/pull-request/1010 > > > > I would also need to run the download playbook to apply the change. > > > > Let the +1/-1's flow please. > > +1 for me as well > > > Pierre > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: update mirror ip addresses for kernel.org
On Tue, Mar 22, 2022 at 02:34:57PM +, Mark O'Brien wrote: > Hi All, > > We have had a request from the people at mirrors.kernel.org to update their > IP address: https://pagure.io/fedora-infrastructure/issue/10598 > > This PR should take care of it > https://pagure.io/fedora-infra/ansible/pull-request/1010 > > I would also need to run the download playbook to apply the change. > > Let the +1/-1's flow please. +1 for me as well Pierre 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: update mirror ip addresses for kernel.org
+1 this is needed for release as kernel.org is a major offloader. On Tue, 22 Mar 2022 at 10:35, Mark O'Brien wrote: > Hi All, > > We have had a request from the people at mirrors.kernel.org to update > their IP address: https://pagure.io/fedora-infrastructure/issue/10598 > > This PR should take care of it > https://pagure.io/fedora-infra/ansible/pull-request/1010 > > I would also need to run the download playbook to apply the change. > > Let the +1/-1's flow please. > > Thanks, > Mark > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: update mirror ip addresses for kernel.org
Hi All, We have had a request from the people at mirrors.kernel.org to update their IP address: https://pagure.io/fedora-infrastructure/issue/10598 This PR should take care of it https://pagure.io/fedora-infra/ansible/pull-request/1010 I would also need to run the download playbook to apply the change. Let the +1/-1's flow please. Thanks, Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: OCP4 storage configuration
Hi everyone. My name is Alejandro Senges aka Alex, I'm from Venezuela, actually living in Montevideo Uruguay. I am studying low level c programming and have some experience with python. I would like to start participating in some coding tasks as an apprentice here. Is that possible? On Fri, Mar 11, 2022, 16:16 Kevin Fenzi wrote: > On Fri, Mar 11, 2022 at 04:31:31PM +, Mark O'Brien wrote: > > Hi All, > > > > I am asking for forgiveness here. We did this work earlier today and only > > realised afterward that a freeze break should have been requested. > > > > OCP worker node worker06.ocp.iad2.fedoraproject.org had its installed > > software raid removed. This node was then added to OCP as a local volume > to > > allow OCP take control of the storage and manage it as part of its local > > volume set. > > +1 > > But we never really decided if ocp4 is frozen or not... :) > > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: OCP4 storage configuration
On Fri, Mar 11, 2022 at 04:31:31PM +, Mark O'Brien wrote: > Hi All, > > I am asking for forgiveness here. We did this work earlier today and only > realised afterward that a freeze break should have been requested. > > OCP worker node worker06.ocp.iad2.fedoraproject.org had its installed > software raid removed. This node was then added to OCP as a local volume to > allow OCP take control of the storage and manage it as part of its local > volume set. +1 But we never really decided if ocp4 is frozen or not... :) 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: OCP4 storage configuration
Thanks for the notification. +1 for the change (post) On Fri, 11 Mar 2022 at 11:32, Mark O'Brien wrote: > Hi All, > > I am asking for forgiveness here. We did this work earlier today and only > realised afterward that a freeze break should have been requested. > > OCP worker node worker06.ocp.iad2.fedoraproject.org had its installed > software raid removed. This node was then added to OCP as a local volume to > allow OCP take control of the storage and manage it as part of its local > volume set. > > Apologies, > Mark > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: OCP4 storage configuration
Hi All, I am asking for forgiveness here. We did this work earlier today and only realised afterward that a freeze break should have been requested. OCP worker node worker06.ocp.iad2.fedoraproject.org had its installed software raid removed. This node was then added to OCP as a local volume to allow OCP take control of the storage and manage it as part of its local volume set. Apologies, Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: Update oz on certain aarch64 builders
+1 to this On Fri, 4 Mar 2022 at 16:27, Mohan Boddu wrote: > Hello, > > Due to a bug in initial-setup [0] we need to update oz to 0.18.1-2 on > some aarch64 builders. The list is obtained by running > > $ koji list-hosts --enabled --arch armhfp --channel image --arch aarch64 > > Hosts: > buildhw-a64-01.iad2.fedoraproject.org > buildhw-a64-02.iad2.fedoraproject.org > buildhw-a64-03.iad2.fedoraproject.org > buildhw-a64-06.iad2.fedoraproject.org > buildhw-a64-11.iad2.fedoraproject.org > buildhw-a64-19.iad2.fedoraproject.org > buildhw-a64-20.iad2.fedoraproject.org > buildhw-a64-21.iad2.fedoraproject.org > buildhw-a64-22.iad2.fedoraproject.org > buildhw-a64-23.iad2.fedoraproject.org > buildhw-a64-24.iad2.fedoraproject.org > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=2057600 > > Thanks. > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: Update oz on certain aarch64 builders
On Fri, Mar 04, 2022 at 04:26:27PM -0500, Mohan Boddu wrote: > Hello, > > Due to a bug in initial-setup [0] we need to update oz to 0.18.1-2 on > some aarch64 builders. The list is obtained by running > > $ koji list-hosts --enabled --arch armhfp --channel image --arch aarch64 > > Hosts: > buildhw-a64-01.iad2.fedoraproject.org > buildhw-a64-02.iad2.fedoraproject.org > buildhw-a64-03.iad2.fedoraproject.org > buildhw-a64-06.iad2.fedoraproject.org > buildhw-a64-11.iad2.fedoraproject.org > buildhw-a64-19.iad2.fedoraproject.org > buildhw-a64-20.iad2.fedoraproject.org > buildhw-a64-21.iad2.fedoraproject.org > buildhw-a64-22.iad2.fedoraproject.org > buildhw-a64-23.iad2.fedoraproject.org > buildhw-a64-24.iad2.fedoraproject.org > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=2057600 +1. It's to fix a blocker, so we have to do it or we would never release. ;) 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: Update oz on certain aarch64 builders
Hello, Due to a bug in initial-setup [0] we need to update oz to 0.18.1-2 on some aarch64 builders. The list is obtained by running $ koji list-hosts --enabled --arch armhfp --channel image --arch aarch64 Hosts: buildhw-a64-01.iad2.fedoraproject.org buildhw-a64-02.iad2.fedoraproject.org buildhw-a64-03.iad2.fedoraproject.org buildhw-a64-06.iad2.fedoraproject.org buildhw-a64-11.iad2.fedoraproject.org buildhw-a64-19.iad2.fedoraproject.org buildhw-a64-20.iad2.fedoraproject.org buildhw-a64-21.iad2.fedoraproject.org buildhw-a64-22.iad2.fedoraproject.org buildhw-a64-23.iad2.fedoraproject.org buildhw-a64-24.iad2.fedoraproject.org [0] https://bugzilla.redhat.com/show_bug.cgi?id=2057600 Thanks. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: [FBR] Update pagure to 5.13.3
On Mon, Nov 01, 2021 at 04:04:52PM +0100, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > This morning, I have cut a new release of pagure: 5.13.3 with the following > changelog: > - Warn users when a PR contains some characters > - srcfpo theme: Change "Packages" link to new packages website (Brendan Early) > - srcfpo theme: left-align the lines in description (Zbigniew > Jędrzejewski-Szmek) > - fas user url updated for new accounts system (Mark O Brien) > - Change fas link from admin.fp.o to accounts.fp.o (Lenka Segura) > - Remove message about 60 day key length (Ken Dreyer) > - Escape $ to fix Jenkins interpolation warning (#5178) (Anatoli Babenia) > - Fix another invalid width/height attribute (Anatoli Babenia) > - Fix missing space before src in
Re: [FBR] Update pagure to 5.13.3
On Mon, Nov 01, 2021 at 11:07:26AM -0400, Neal Gompa wrote: > On Mon, Nov 1, 2021 at 11:06 AM Pierre-Yves Chibon > wrote: > > > > Good Morning Everyone, > > > > This morning, I have cut a new release of pagure: 5.13.3 with the following > > changelog: > > - Warn users when a PR contains some characters > > - srcfpo theme: Change "Packages" link to new packages website (Brendan > > Early) > > - srcfpo theme: left-align the lines in description (Zbigniew > > Jędrzejewski-Szmek) > > - fas user url updated for new accounts system (Mark O Brien) > > - Change fas link from admin.fp.o to accounts.fp.o (Lenka Segura) > > - Remove message about 60 day key length (Ken Dreyer) > > - Escape $ to fix Jenkins interpolation warning (#5178) (Anatoli Babenia) > > - Fix another invalid width/height attribute (Anatoli Babenia) > > - Fix missing space before src in
Re: [FBR] Update pagure to 5.13.3
On Mon, Nov 1, 2021 at 11:06 AM Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > This morning, I have cut a new release of pagure: 5.13.3 with the following > changelog: > - Warn users when a PR contains some characters > - srcfpo theme: Change "Packages" link to new packages website (Brendan Early) > - srcfpo theme: left-align the lines in description (Zbigniew > Jędrzejewski-Szmek) > - fas user url updated for new accounts system (Mark O Brien) > - Change fas link from admin.fp.o to accounts.fp.o (Lenka Segura) > - Remove message about 60 day key length (Ken Dreyer) > - Escape $ to fix Jenkins interpolation warning (#5178) (Anatoli Babenia) > - Fix another invalid width/height attribute (Anatoli Babenia) > - Fix missing space before src in
[FBR] Update pagure to 5.13.3
Good Morning Everyone, This morning, I have cut a new release of pagure: 5.13.3 with the following changelog: - Warn users when a PR contains some characters - srcfpo theme: Change "Packages" link to new packages website (Brendan Early) - srcfpo theme: left-align the lines in description (Zbigniew Jędrzejewski-Szmek) - fas user url updated for new accounts system (Mark O Brien) - Change fas link from admin.fp.o to accounts.fp.o (Lenka Segura) - Remove message about 60 day key length (Ken Dreyer) - Escape $ to fix Jenkins interpolation warning (#5178) (Anatoli Babenia) - Fix another invalid width/height attribute (Anatoli Babenia) - Fix missing space before src in
Re: FBR: fix download cron on download-cc-rdu
Merging and deploying. On Mon, 18 Oct 2021 at 16:53, Kevin Fenzi wrote: > > +1 here. > > kevin > -- > On Mon, Oct 18, 2021 at 03:12:44PM -0400, Stephen John Smoogen wrote: > > https://pagure.io/fedora-infra/ansible/pull-request/834 > > > > -- Forwarded message - > > From: (Cron Daemon) > > Date: Mon, 18 Oct 2021 at 15:00 > > Subject: Cron /usr/local/bin/lock-wrapper > > sync-up-downloads "/usr/local/bin/sync-up-centos" > > To: > > > > > > /usr/local/bin/lock-wrapper: line 50: /usr/local/bin/sync-up-centos: > > No such file or directory > > > > > > -- > > Stephen J Smoogen. > > I've seen things you people wouldn't believe. Flame wars in > > sci.astro.orion. I have seen SPAM filters overload because of Godwin's > > Law. All those moments will be lost in time... like posts on a BBS... > > time to shutdown -h now. > > ___ > > 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 on the list, report it: > > https://pagure.io/fedora-infrastructure > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure -- Stephen J Smoogen. I've seen things you people wouldn't believe. Flame wars in sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law. All those moments will be lost in time... like posts on a BBS... time to shutdown -h now. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: fix download cron on download-cc-rdu
+1 here. kevin -- On Mon, Oct 18, 2021 at 03:12:44PM -0400, Stephen John Smoogen wrote: > https://pagure.io/fedora-infra/ansible/pull-request/834 > > -- Forwarded message - > From: (Cron Daemon) > Date: Mon, 18 Oct 2021 at 15:00 > Subject: Cron /usr/local/bin/lock-wrapper > sync-up-downloads "/usr/local/bin/sync-up-centos" > To: > > > /usr/local/bin/lock-wrapper: line 50: /usr/local/bin/sync-up-centos: > No such file or directory > > > -- > Stephen J Smoogen. > I've seen things you people wouldn't believe. Flame wars in > sci.astro.orion. I have seen SPAM filters overload because of Godwin's > Law. All those moments will be lost in time... like posts on a BBS... > time to shutdown -h now. > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: fix download cron on download-cc-rdu
+1 looks good to me On Mon 18 Oct 2021, 20:15 Stephen John Smoogen, wrote: > https://pagure.io/fedora-infra/ansible/pull-request/834 > > -- Forwarded message - > From: (Cron Daemon) > Date: Mon, 18 Oct 2021 at 15:00 > Subject: Cron /usr/local/bin/lock-wrapper > sync-up-downloads "/usr/local/bin/sync-up-centos" > To: > > > /usr/local/bin/lock-wrapper: line 50: /usr/local/bin/sync-up-centos: > No such file or directory > > > -- > Stephen J Smoogen. > I've seen things you people wouldn't believe. Flame wars in > sci.astro.orion. I have seen SPAM filters overload because of Godwin's > Law. All those moments will be lost in time... like posts on a BBS... > time to shutdown -h now. > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: fix download cron on download-cc-rdu
https://pagure.io/fedora-infra/ansible/pull-request/834 -- Forwarded message - From: (Cron Daemon) Date: Mon, 18 Oct 2021 at 15:00 Subject: Cron /usr/local/bin/lock-wrapper sync-up-downloads "/usr/local/bin/sync-up-centos" To: /usr/local/bin/lock-wrapper: line 50: /usr/local/bin/sync-up-centos: No such file or directory -- Stephen J Smoogen. I've seen things you people wouldn't believe. Flame wars in sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law. All those moments will be lost in time... like posts on a BBS... time to shutdown -h now. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: maintainer-test: create f35 instance and vpn settings
On Mon, Oct 11, 2021 at 6:05 PM Kevin Fenzi wrote: > On Mon, Oct 11, 2021 at 05:09:09PM +0100, Mark O'Brien wrote: > > Hi All, > > > > I would like to create a maintainer test instance in AWS. Below I > > have a dns patch and an ansible PR for your consideration. > > > > This will also require a playbook run on the batcave for the vpn > > settings > > > > As always all input is greatly appreciated. > > > > > > DNS: > https://gist.github.com/markobrien1/4f283c2d4c8f9d70d7f26263185cf481 > > > > Ansible: > > https://pagure.io/fedora-infra/ansible/pull-request/824#request_diff > > looks good. Do we want to do a f34 one too while we are at it? :) > I am hoping to get Pedro to that one after showing him this one. Opportunity to knowledge share > > +1 > > Thanks ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: maintainer-test: create f35 instance and vpn settings
On Mon, Oct 11, 2021 at 05:09:09PM +0100, Mark O'Brien wrote: > Hi All, > > I would like to create a maintainer test instance in AWS. Below I > have a dns patch and an ansible PR for your consideration. > > This will also require a playbook run on the batcave for the vpn > settings > > As always all input is greatly appreciated. > > > DNS: https://gist.github.com/markobrien1/4f283c2d4c8f9d70d7f26263185cf481 > > Ansible: > https://pagure.io/fedora-infra/ansible/pull-request/824#request_diff looks good. Do we want to do a f34 one too while we are at it? :) +1 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: maintainer-test: create f35 instance and vpn settings
Hi All, I would like to create a maintainer test instance in AWS. Below I have a dns patch and an ansible PR for your consideration. This will also require a playbook run on the batcave for the vpn settings As always all input is greatly appreciated. DNS: https://gist.github.com/markobrien1/4f283c2d4c8f9d70d7f26263185cf481 Ansible: https://pagure.io/fedora-infra/ansible/pull-request/824#request_diff Thanks, Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: F35 Beta is Go
Hi, Since F35 beta is go now, we can enable bodhi for automated pushes and set the 35 bodhi status to post beta. https://pagure.io/fedora-infra/ansible/pull-request/814 +1's please, Thanks. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: To enable automated signing for f36-openh264 tag
Hi, The PR [0] will enable automated signing for f36-openh264 tag which is needed to update the openh264 repos for rawhide/f36 and also fix issues in f35. Currently the pungi compose is failing due to missing signed rpms, this will fix that issue. +1's please Thanks. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: run batcave playbook for rbac
Thanks for the +1s I have run the playbook On Tue, Sep 21, 2021 at 3:32 PM Mikolaj Izdebski wrote: > +1 > > On Tue, Sep 21, 2021 at 4:10 PM Mark O'Brien wrote: > > > > Hi All, > > > > I am requesting permissions to run the batcave > > playbook to update rbac permissions to allow the > > sysadmin-analysis group run the logserver playbook > > as requested in this ticket: > > > > https://pagure.io/fedora-infrastructure/issue/10231 > > > > As always comments/+1's welcome > > > > Thanks, > > Mark > > ___ > > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: run batcave playbook for rbac
+1 On Tue, Sep 21, 2021 at 4:10 PM Mark O'Brien wrote: > > Hi All, > > I am requesting permissions to run the batcave > playbook to update rbac permissions to allow the > sysadmin-analysis group run the logserver playbook > as requested in this ticket: > > https://pagure.io/fedora-infrastructure/issue/10231 > > As always comments/+1's welcome > > Thanks, > Mark > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: run batcave playbook for rbac
On Tue, Sep 21, 2021 at 03:08:12PM +0100, Mark O'Brien wrote: > Hi All, > > I am requesting permissions to run the batcave > playbook to update rbac permissions to allow the > sysadmin-analysis group run the logserver playbook > as requested in this ticket: > > https://pagure.io/fedora-infrastructure/issue/10231 > > As always comments/+1's welcome +1 for me Pierre 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: run batcave playbook for rbac
Hi All, I am requesting permissions to run the batcave playbook to update rbac permissions to allow the sysadmin-analysis group run the logserver playbook as requested in this ticket: https://pagure.io/fedora-infrastructure/issue/10231 As always comments/+1's welcome Thanks, Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: Enable CentOS Stream in MirrorManager
On Mon, Sep 06, 2021 at 08:01:40PM +0200, Adrian Reber wrote: > Over the last weeks we prepared adding CentOS Stream to Fedora's > MirrorManager instance and are now at a point where we would like to > push the changes to ansible. > > The current state can be seen at: > > http://mirrors.stg.centos.org/metalink?repo=centos-baseos-9-stream=x86_64 > > (https just broke over the weekend) > > To enable CentOS Stream in MirrorManager not only configuration file > changes are necessary, but it also requires an update of all software > components. This is mainly due to the fact that CentOS Stream is using > an empty topdir. (topdir in MirrorManager are things like 'epel/' or > 'fedora/linux' or 'fedora-secondary/'). > > Unfortunately all code assumed that topdir is not '' and hard-coded the > removal of a slash all over the place. > > All corresponding projects have been update to handle empty topdirs. > > To apply https://pagure.io/fedora-infra/ansible/pull-request/775 for > prod I need this FBR. > > There are risks doing code changes like this during a freeze. So far I > have not seen any problems in staging, but staging is not using using > MirrorManager as thoroughly as prod. I don't expect any major problems > with this change. > > I hope someone from the CentOS team can weigh if this is very time > critical to get running or if we can wait until after the freeze. This is now active and I am able to use it on my CentOS Stream 9 VM with: metalink=https://mirrors.centos.org/metalink?repo=centos-baseos-9-stream=x86_64 metalink=https://mirrors.centos.org/metalink?repo=centos-appstream-9-stream=x86_64 metalink=https://mirrors.centos.org/metalink?repo=centos-crb-9-stream=x86_64 Let me know if something does not work as expected. Adrian ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: Enable CentOS Stream in MirrorManager
On Mon, Sep 06, 2021 at 08:01:40PM +0200, Adrian Reber wrote: > Over the last weeks we prepared adding CentOS Stream to Fedora's > MirrorManager instance and are now at a point where we would like to > push the changes to ansible. > > The current state can be seen at: > > http://mirrors.stg.centos.org/metalink?repo=centos-baseos-9-stream=x86_64 > > (https just broke over the weekend) I fixed that. Sorry about that. ;( > To enable CentOS Stream in MirrorManager not only configuration file > changes are necessary, but it also requires an update of all software > components. This is mainly due to the fact that CentOS Stream is using > an empty topdir. (topdir in MirrorManager are things like 'epel/' or > 'fedora/linux' or 'fedora-secondary/'). > > Unfortunately all code assumed that topdir is not '' and hard-coded the > removal of a slash all over the place. > > All corresponding projects have been update to handle empty topdirs. > > To apply https://pagure.io/fedora-infra/ansible/pull-request/775 for > prod I need this FBR. Also this may need a bit more work on proxies. Something like: diff --git a/playbooks/include/proxies-reverseproxy.yml b/playbooks/include/proxies-reverseproxy.yml index d771a0144..a2e0788cd 100644 --- a/playbooks/include/proxies-reverseproxy.yml +++ b/playbooks/include/proxies-reverseproxy.yml @@ -366,7 +366,6 @@ website: mirrors.centos.org destname: mirrormanager-mirrorlist proxyurl: http://localhost:10002 -when: env == "staging" - role: httpd/reverseproxy website: download.fedoraproject.org diff --git a/playbooks/include/proxies-websites.yml b/playbooks/include/proxies-websites.yml index 99fef15cb..fb144733f 100644 --- a/playbooks/include/proxies-websites.yml +++ b/playbooks/include/proxies-websites.yml @@ -158,8 +158,7 @@ server_aliases: - mirrors.stg.centos.org cert_name: "{{mirrors_centos_org_cert_name}}" -SSLCertificateChainFile: mirrors.stg.centos.org.intermediate.cert -when: env == "staging" +SSLCertificateChainFile: "mirrors{{env_suffix}}.centos.org.intermediate.cert" - role: httpd/website site_name: src.fedoraproject.org > > There are risks doing code changes like this during a freeze. So far I > have not seen any problems in staging, but staging is not using using > MirrorManager as thoroughly as prod. I don't expect any major problems > with this change. > > I hope someone from the CentOS team can weigh if this is very time > critical to get running or if we can wait until after the freeze. I think it would be safe to do at this point, but if we can hold off until after freeze thats of course great. 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: Enable CentOS Stream in MirrorManager
Over the last weeks we prepared adding CentOS Stream to Fedora's MirrorManager instance and are now at a point where we would like to push the changes to ansible. The current state can be seen at: http://mirrors.stg.centos.org/metalink?repo=centos-baseos-9-stream=x86_64 (https just broke over the weekend) To enable CentOS Stream in MirrorManager not only configuration file changes are necessary, but it also requires an update of all software components. This is mainly due to the fact that CentOS Stream is using an empty topdir. (topdir in MirrorManager are things like 'epel/' or 'fedora/linux' or 'fedora-secondary/'). Unfortunately all code assumed that topdir is not '' and hard-coded the removal of a slash all over the place. All corresponding projects have been update to handle empty topdirs. To apply https://pagure.io/fedora-infra/ansible/pull-request/775 for prod I need this FBR. There are risks doing code changes like this during a freeze. So far I have not seen any problems in staging, but staging is not using using MirrorManager as thoroughly as prod. I don't expect any major problems with this change. I hope someone from the CentOS team can weigh if this is very time critical to get running or if we can wait until after the freeze. Adrian ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: add fedora-messaging queues for CentOS Stream robosignatory
PR has been merged and playbook run. On Wed, Sep 1, 2021 at 8:06 PM Stephen John Smoogen wrote: > On Wed, 1 Sept 2021 at 14:40, kevin wrote: > > > > On Wed, Sep 01, 2021 at 09:25:02AM -0500, Brian Stinson wrote: > > > Hi Folks, > > > > > > We'd like to have a separate fedora-messaging queue for our > robosignatory installation in CentOS Stream: > > > https://pagure.io/fedora-infra/ansible/pull-request/772 > > > > > > I hope this turns out to be low impact, and Mark was also looking at > generating certificates for this. > > > > > > +1s from sysadmins or releng are greatly appreciated > > > > +1 here. > > This can be merged. > > -- > Stephen J Smoogen. > I've seen things you people wouldn't believe. Flame wars in > sci.astro.orion. I have seen SPAM filters overload because of Godwin's > Law. All those moments will be lost in time... like posts on a BBS... > time to shutdown -h now. > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: add fedora-messaging queues for CentOS Stream robosignatory
On Wed, 1 Sept 2021 at 14:40, kevin wrote: > > On Wed, Sep 01, 2021 at 09:25:02AM -0500, Brian Stinson wrote: > > Hi Folks, > > > > We'd like to have a separate fedora-messaging queue for our robosignatory > > installation in CentOS Stream: > > https://pagure.io/fedora-infra/ansible/pull-request/772 > > > > I hope this turns out to be low impact, and Mark was also looking at > > generating certificates for this. > > > > +1s from sysadmins or releng are greatly appreciated > > +1 here. This can be merged. -- Stephen J Smoogen. I've seen things you people wouldn't believe. Flame wars in sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law. All those moments will be lost in time... like posts on a BBS... time to shutdown -h now. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: add fedora-messaging queues for CentOS Stream robosignatory
On Wed, Sep 01, 2021 at 09:25:02AM -0500, Brian Stinson wrote: > Hi Folks, > > We'd like to have a separate fedora-messaging queue for our robosignatory > installation in CentOS Stream: > https://pagure.io/fedora-infra/ansible/pull-request/772 > > I hope this turns out to be low impact, and Mark was also looking at > generating certificates for this. > > +1s from sysadmins or releng are greatly appreciated +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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: add fedora-messaging queues for CentOS Stream robosignatory
Hi Folks, We'd like to have a separate fedora-messaging queue for our robosignatory installation in CentOS Stream: https://pagure.io/fedora-infra/ansible/pull-request/772 I hope this turns out to be low impact, and Mark was also looking at generating certificates for this. +1s from sysadmins or releng are greatly appreciated -- Brian ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: add ipa host group for openshift hosts
On Tue, Aug 31, 2021 at 03:47:43PM +0100, Mark O'Brien wrote: > Hi All, > > I have a Freeze break request for review. I would like to add a host group > for the openshift hosts in ipa so that we can give access to the > sysadmin-openshift team. > > https://pagure.io/fedora-infra/ansible/pull-request/768# > > Any +1's from sysadmin-main/releng greatly appreciated > > p.s. if this sounds familiar to you it is because this pull request was > supposed to do that originally but I didn't realise the hostgroup didn't > yet exist Yeah, I +1ed it in the PR. 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: add ipa host group for openshift hosts
Hi All, I have a Freeze break request for review. I would like to add a host group for the openshift hosts in ipa so that we can give access to the sysadmin-openshift team. https://pagure.io/fedora-infra/ansible/pull-request/768# Any +1's from sysadmin-main/releng greatly appreciated p.s. if this sounds familiar to you it is because this pull request was supposed to do that originally but I didn't realise the hostgroup didn't yet exist Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: os control access for sysadmin-openshift
On Wed, Aug 25, 2021 at 05:13:25PM +0100, Mark O'Brien wrote: > Hi All, > > As per https://pagure.io/fedora-infrastructure/issue/10186 > > Could I get some reviews/+1's on this PR. It will allow for the work to > continue > on the deployment of the openshift 4 cluster for Fedora. > > https://pagure.io/fedora-infra/ansible/pull-request/761 +1 here, seems reasonable. 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: os control access for sysadmin-openshift
Hi All, As per https://pagure.io/fedora-infrastructure/issue/10186 Could I get some reviews/+1's on this PR. It will allow for the work to continue on the deployment of the openshift 4 cluster for Fedora. https://pagure.io/fedora-infra/ansible/pull-request/761 Thanks all, Mark ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: Updating pungi on compose-x86-01.iad2.fp.o to pungi-4.2.8-1.fc33.infra.1.noarch
On Tue, Mar 09, 2021 at 11:18:21PM -0500, Mohan Boddu wrote: > Hi, > > I am updating pungi on compose-x86-01.iad2.fp.o to > pungi-4.2.8-1.fc33.infra.1.noarch to match it with the one installed > on compose-branched01.iad2.fp.o for running beta RC's. I am doing this > proactively rather than waiting for the FBR approval to get the RC > going. Yeah, retroactive +1 we want this to match. 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: Updating pungi on compose-x86-01.iad2.fp.o to pungi-4.2.8-1.fc33.infra.1.noarch
Hi, I am updating pungi on compose-x86-01.iad2.fp.o to pungi-4.2.8-1.fc33.infra.1.noarch to match it with the one installed on compose-branched01.iad2.fp.o for running beta RC's. I am doing this proactively rather than waiting for the FBR approval to get the RC going. Thanks, Mohan Boddu. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: FBR: To add i3 spin pungi config to F34
On Tue, Feb 23, 2021 at 02:28:39PM -0500, Mohan Boddu wrote: > Hi, > > i3 spin is a new deliverable for F34 and this PR [1] adds the needed > config for generating the i3 live iso as part of nightly compose. > > Please give your +1's. > > [1] https://pagure.io/pungi-fedora/pull-request/1012 +1 here, but might be good to get a ack from Adam that it doesn't break fedfind or need any adjustments to it's names. :) 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 on the list, report it: https://pagure.io/fedora-infrastructure
FBR: To add i3 spin pungi config to F34
Hi, i3 spin is a new deliverable for F34 and this PR [1] adds the needed config for generating the i3 live iso as part of nightly compose. Please give your +1's. [1] https://pagure.io/pungi-fedora/pull-request/1012 Thanks, Mohan Boddu. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: [FBR] Bump the IoT stable keys to fedora-33
On Wed, Oct 28, 2020 at 11:56:11AM +0100, Patrick Uiterwijk wrote: > Hi, > > Can I get acks for the following patch to move the stable IoT composes > to the Fedora 33 key? > (Note: there's a single "empty" line change as well, that was a line > with purely whitespace, which my IDE automatically cleans up.) +1 for me as well Pierre > commit 3ee8dd3f9e883414c7846d115d2926f73ec9ea99 (HEAD -> master) > Author: Patrick Uiterwijk > Date: Wed Oct 28 11:26:44 2020 +0100 > > Bump the IoT stable keys to fedora-33 > > Signed-off-by: Patrick Uiterwijk > > diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 > b/roles/robosignatory/templates/robosignatory.toml.j2 > index 6a933bda9..70fde0d55 100644 > --- a/roles/robosignatory/templates/robosignatory.toml.j2 > +++ b/roles/robosignatory/templates/robosignatory.toml.j2 > @@ -380,7 +380,7 @@ handlers = ["console"] > key = "{{ (env == 'production')|ternary('fedora-34', 'testkey') > }}" > keyid = "{{ (env == 'production')|ternary('45719a39', > 'd300e724') }}" > type = "modular" > - > + > # ELN Mass Rebuild > > [[consumer_config.koji_instances.primary.tags]] > @@ -445,13 +445,13 @@ handlers = ["console"] > > [consumer_config.ostree_refs."fedora/stable/x86_64/iot"] > directory = "/mnt/fedora_koji/koji/compose/iot/repo/" > -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" > +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" > [consumer_config.ostree_refs."fedora/stable/aarch64/iot"] > directory = "/mnt/fedora_koji/koji/compose/iot/repo/" > -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" > +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" > [consumer_config.ostree_refs."fedora/stable/armhfp/iot"] > directory = "/mnt/fedora_koji/koji/compose/iot/repo/" > -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" > +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" > > [consumer_config.ostree_refs."fedora/29/x86_64/atomic-host"] > directory = "/mnt/fedora_koji/koji/compose/ostree/repo/" > ___ > 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 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
Re: [FBR] Bump the IoT stable keys to fedora-33
> Can I get acks for the following patch to move the stable IoT composes > to the Fedora 33 key? > (Note: there's a single "empty" line change as well, that was a line > with purely whitespace, which my IDE automatically cleans up.) +1 from me > Thanks, > Patrick > > > commit 3ee8dd3f9e883414c7846d115d2926f73ec9ea99 (HEAD -> master) > Author: Patrick Uiterwijk > Date: Wed Oct 28 11:26:44 2020 +0100 > > Bump the IoT stable keys to fedora-33 > > Signed-off-by: Patrick Uiterwijk > > diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 > b/roles/robosignatory/templates/robosignatory.toml.j2 > index 6a933bda9..70fde0d55 100644 > --- a/roles/robosignatory/templates/robosignatory.toml.j2 > +++ b/roles/robosignatory/templates/robosignatory.toml.j2 > @@ -380,7 +380,7 @@ handlers = ["console"] > key = "{{ (env == 'production')|ternary('fedora-34', 'testkey') > }}" > keyid = "{{ (env == 'production')|ternary('45719a39', > 'd300e724') }}" > type = "modular" > - > + > # ELN Mass Rebuild > > [[consumer_config.koji_instances.primary.tags]] > @@ -445,13 +445,13 @@ handlers = ["console"] > > [consumer_config.ostree_refs."fedora/stable/x86_64/iot"] > directory = "/mnt/fedora_koji/koji/compose/iot/repo/" > -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" > +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" > [consumer_config.ostree_refs."fedora/stable/aarch64/iot"] > directory = "/mnt/fedora_koji/koji/compose/iot/repo/" > -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" > +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" > [consumer_config.ostree_refs."fedora/stable/armhfp/iot"] > directory = "/mnt/fedora_koji/koji/compose/iot/repo/" > -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" > +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" > > [consumer_config.ostree_refs."fedora/29/x86_64/atomic-host"] > directory = "/mnt/fedora_koji/koji/compose/ostree/repo/" > ___ > 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 ___ 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
[FBR] Bump the IoT stable keys to fedora-33
Hi, Can I get acks for the following patch to move the stable IoT composes to the Fedora 33 key? (Note: there's a single "empty" line change as well, that was a line with purely whitespace, which my IDE automatically cleans up.) Thanks, Patrick commit 3ee8dd3f9e883414c7846d115d2926f73ec9ea99 (HEAD -> master) Author: Patrick Uiterwijk Date: Wed Oct 28 11:26:44 2020 +0100 Bump the IoT stable keys to fedora-33 Signed-off-by: Patrick Uiterwijk diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 b/roles/robosignatory/templates/robosignatory.toml.j2 index 6a933bda9..70fde0d55 100644 --- a/roles/robosignatory/templates/robosignatory.toml.j2 +++ b/roles/robosignatory/templates/robosignatory.toml.j2 @@ -380,7 +380,7 @@ handlers = ["console"] key = "{{ (env == 'production')|ternary('fedora-34', 'testkey') }}" keyid = "{{ (env == 'production')|ternary('45719a39', 'd300e724') }}" type = "modular" - + # ELN Mass Rebuild [[consumer_config.koji_instances.primary.tags]] @@ -445,13 +445,13 @@ handlers = ["console"] [consumer_config.ostree_refs."fedora/stable/x86_64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" [consumer_config.ostree_refs."fedora/stable/aarch64/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" [consumer_config.ostree_refs."fedora/stable/armhfp/iot"] directory = "/mnt/fedora_koji/koji/compose/iot/repo/" -key = "{{ (env == 'production')|ternary('fedora-32', 'testkey') }}" +key = "{{ (env == 'production')|ternary('fedora-33', 'testkey') }}" [consumer_config.ostree_refs."fedora/29/x86_64/atomic-host"] directory = "/mnt/fedora_koji/koji/compose/ostree/repo/" ___ 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
Re: [FBR] upgrade mediawiki-skin-fedora to 0.09 on wiki0{1,2}
On Fri, Oct 09, 2020 09:49:03 +0200, Pierre-Yves Chibon wrote: > On Thu, Oct 08, 2020 at 09:43:35AM -0700, Kevin Fenzi wrote: > > On Thu, Oct 08, 2020 at 05:05:06PM +0200, Pierre-Yves Chibon wrote: > > > > > > +1, but it would sure be nice to test in staging first. ;) > > Got staging to work and upgraded the theme there: > https://stg.fedoraproject.org/wiki/Fedora_Project_Wiki (see just above > "History", "View Source", "View" at the top right of the page). > > How does it look? Looks good to me. Hard to miss. Thanks very much :) -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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
Re: [FBR] upgrade mediawiki-skin-fedora to 0.09 on wiki0{1,2}
On Thu, Oct 08, 2020 at 09:43:35AM -0700, Kevin Fenzi wrote: > On Thu, Oct 08, 2020 at 05:05:06PM +0200, Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > > > I have just tagged and release the version 0.09 of the mediawiki-skin-fedora > > package. > > It contains two changes: > > - a fix to the CoC link in the footer > > - adding the last edit date near the top of the pages > > (fixes https://pagure.io/fedora-infrastructure/issue/8636 ) > > > > The changes can be reviewed at: > > https://pagure.io/fedora-mediawikitheme/commits/ > > > > The RPM has been built and is in the f32-infra-stg tag already: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=53004452 > > > > I'd like to move that rpm to the f32-infra tag, update that package on both > > wiki01 and wiki02 and reload apache afterward. > > > > > > Thoughts? > > +1, but it would sure be nice to test in staging first. ;) Got staging to work and upgraded the theme there: https://stg.fedoraproject.org/wiki/Fedora_Project_Wiki (see just above "History", "View Source", "View" at the top right of the page). How does it look? Pierre ___ 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
Re: [FBR] upgrade mediawiki-skin-fedora to 0.09 on wiki0{1,2}
On Thu, Oct 08, 2020 at 05:05:06PM +0200, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > I have just tagged and release the version 0.09 of the mediawiki-skin-fedora > package. > It contains two changes: > - a fix to the CoC link in the footer > - adding the last edit date near the top of the pages > (fixes https://pagure.io/fedora-infrastructure/issue/8636 ) > > The changes can be reviewed at: > https://pagure.io/fedora-mediawikitheme/commits/ > > The RPM has been built and is in the f32-infra-stg tag already: > https://koji.fedoraproject.org/koji/taskinfo?taskID=53004452 > > I'd like to move that rpm to the f32-infra tag, update that package on both > wiki01 and wiki02 and reload apache afterward. > > > Thoughts? +1, but it would sure be nice to test in staging first. ;) Of course we need to get staging wiki working, but I think that would be a good thing to do. 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
[FBR] upgrade mediawiki-skin-fedora to 0.09 on wiki0{1,2}
Good Morning Everyone, I have just tagged and release the version 0.09 of the mediawiki-skin-fedora package. It contains two changes: - a fix to the CoC link in the footer - adding the last edit date near the top of the pages (fixes https://pagure.io/fedora-infrastructure/issue/8636 ) The changes can be reviewed at: https://pagure.io/fedora-mediawikitheme/commits/ The RPM has been built and is in the f32-infra-stg tag already: https://koji.fedoraproject.org/koji/taskinfo?taskID=53004452 I'd like to move that rpm to the f32-infra tag, update that package on both wiki01 and wiki02 and reload apache afterward. Thoughts? Pierre ___ 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
Re: FBR: put new proxies in action
This has now been merged On Mon, Sep 28, 2020 at 8:13 PM Stephen John Smoogen wrote: > > +1 after review. > > On Mon, 28 Sep 2020 at 09:22, Mark O'Brien wrote: > >> Hi All, >> >> Attached is a DNS patch to put some new proxy servers in Europe, Asia >> Pacific and Africa. The servers are up and running and passing all nagios >> checks. This patch would start directing the regional traffic toward the >> servers >> >> Just a note, the do-domains script would also need to be run on this. I >> left it out so as not to clutter the patch. >> >> >> Any +1's or comments are appreciated. >> >> Thanks, >> Mark >> >> ___ >> 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 >> > > > -- > Stephen J Smoogen. > > ___ > 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 > ___ 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
Re: FBR: put new proxies in action
+1 after review. On Mon, 28 Sep 2020 at 09:22, Mark O'Brien wrote: > Hi All, > > Attached is a DNS patch to put some new proxy servers in Europe, Asia > Pacific and Africa. The servers are up and running and passing all nagios > checks. This patch would start directing the regional traffic toward the > servers > > Just a note, the do-domains script would also need to be run on this. I > left it out so as not to clutter the patch. > > > Any +1's or comments are appreciated. > > Thanks, > Mark > > ___ > 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 > -- Stephen J Smoogen. ___ 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
Re: FBR: put new proxies in action
On Mon, Sep 28, 2020 at 02:22:21PM +0100, Mark O'Brien wrote: > Hi All, > > Attached is a DNS patch to put some new proxy servers in Europe, Asia > Pacific and Africa. The servers are up and running and passing all nagios > checks. This patch would start directing the regional traffic toward the > servers > > Just a note, the do-domains script would also need to be run on this. I > left it out so as not to clutter the patch. > > > Any +1's or comments are appreciated. So the pagure.io and cloud.fedoraproject.org ones are probibly not needed anymore, but I guess it doesn't hurt to update them for now. +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
FBR: put new proxies in action
Hi All, Attached is a DNS patch to put some new proxy servers in Europe, Asia Pacific and Africa. The servers are up and running and passing all nagios checks. This patch would start directing the regional traffic toward the servers Just a note, the do-domains script would also need to be run on this. I left it out so as not to clutter the patch. Any +1's or comments are appreciated. Thanks, Mark From aab55f26915c6812c1084379ef785e7dde2def17 Mon Sep 17 00:00:00 2001 From: Mark O'Brien Date: Mon, 28 Sep 2020 13:14:35 + Subject: [PATCH] put new aws proxies in action --- cloud.fedoraproject.org.cfg | 47 ++ fedoraproject.org.cfg | 51 + getfedora.org.cfg | 51 + pagure.io.cfg | 51 + 4 files changed, 200 insertions(+) diff --git a/cloud.fedoraproject.org.cfg b/cloud.fedoraproject.org.cfg index ae15b6005..8b9739b44 100644 --- a/cloud.fedoraproject.org.cfg +++ b/cloud.fedoraproject.org.cfg @@ -37,6 +37,13 @@ config_opts['def_proxy_ttl'] = '60' # IN A 13.125.120.8; proxy31 (APAC/AWS) # IN A 18.185.136.17 ; proxy32 (EU/AWS) #IN A 13.244.141.152 ; proxy33 (AFR/AWS) +# IN A 13.250.126.156 ; proxy34 (SA/AWS) +# IN A 13.125.120.8; proxy35 (EU/AWS) +# IN A 18.185.136.17 ; proxy36 (EU/AWS) +#IN A 13.244.141.152 ; proxy37 (APAC/AWS) +# IN A 13.125.120.8; proxy38 (APAC/AWS) +# IN A 18.185.136.17 ; proxy39 (AFR/AWS) +#IN A 13.244.141.152 ; proxy40 (SA/AWS) ipv4_proxy = { '38.145.60.20':{ 'regions': ['DEFAULT', 'NA', 'EU', 'APAC', 'AFR'], @@ -104,6 +111,26 @@ ipv4_proxy = { 'regions': ['DEFAULT', 'AFR'], 'names': ['proxy33', 'proxy33.fedoraproject.org']}, +'18.130.159.183':{ +'regions': ['EU'], +'names': ['proxy35', + 'proxy35.fedoraproject.org']}, +'18.159.254.57':{ +'regions': ['EU'], +'names': ['proxy36', + 'proxy36.fedoraproject.org']}, +'13.233.183.170':{ +'regions': ['APAC'], +'names': ['proxy37', + 'proxy37.fedoraproject.org']}, +'13.212.21.54':{ +'regions': ['APAC'], +'names': ['proxy38', + 'proxy38.fedoraproject.org']}, +'13.244.109.203':{ +'regions': ['AFR'], +'names': ['proxy39', + 'proxy39.fedoraproject.org']}, '10.3.163.74':{ 'regions': ['IAD2'], 'names': ['proxy01', @@ -180,6 +207,26 @@ ipv6_proxy = { 'regions': ['DEFAULT', 'AFR'], 'names': ['proxy33', 'proxy33.fedoraproject.org']}, + '2a05:d01c:c6a:cc03:263a:8409:b961:7e02':{ + 'regions': ['EU'], + 'names': ['proxy35', + 'proxy35.fedoraproject.org']}, + '2a05:d014:10:7803:f774:4d7c:e277:a457':{ + 'regions': ['EU'], + 'names': ['proxy36', + 'proxy36.fedoraproject.org']}, + '2406:da1a:fcb:2f01:f381:af1a:f922:c519':{ + 'regions': ['APAC'], + 'names': ['proxy37', + 'proxy37.fedoraproject.org']}, + '2406:da18:39f:a01:8c16:c226:1274:7098':{ + 'regions': ['APAC'], + 'names': ['proxy38', + 'proxy38.fedoraproject.org']}, + '2406:da11:911:f403:5bba:652:9218:ecef':{ + 'regions': ['AFR'], + 'names': ['proxy39', + 'proxy39.fedoraproject.org']}, } config_opts['ipv4_proxy'] = ipv4_proxy diff --git a/fedoraproject.org.cfg b/fedoraproject.org.cfg index f4dfc9904..f23f5e284 100644 --- a/fedoraproject.org.cfg +++ b/fedoraproject.org.cfg @@ -37,6 +37,13 @@ config_opts['def_proxy_ttl'] = '60' # IN A 13.125.120.8; proxy31 (APAC/AWS) # IN A 18.185.136.17 ; proxy32 (EU/AWS) #IN A 13.244.141.152 ; proxy33 (AFR/AWS) +#IN A 13.250.126.156 ; proxy34 (SA/AWS) +#IN A 13.125.120.8; proxy35 (EU/AWS) +#IN A 18.185.136.17 ; proxy36 (EU/AWS) +#IN A 13.244.141.152 ; proxy37 (APAC/AWS) +#IN A 13.125.120.8; proxy38 (APAC/AWS) +#IN A 18.185.136.17 ; proxy39 (AFR/AWS) +#IN A 13.244.141.152 ; proxy40 (SA/AWS) ipv4_proxy = { '38.145.60.20':{ 'regions': ['DEFAULT', 'NA', 'EU', 'APAC', 'AFR'], @@ -104,6 +111,30 @@ ipv4_proxy = { 'regions': ['DEFAULT', 'AFR'], 'names': ['proxy33', 'proxy33.fedoraproject.org']}, +'13.244.141.152':{ +'regions': ['DEFAULT', 'AFR'], +'names': ['proxy33', + 'proxy33.fedoraproject.org']}, +'18.130.159.183':{ +'regions': ['EU'], +'names': ['proxy35', + 'proxy35.fedoraproject.org']}, +'18.159.254.57':{ +'regions': ['EU'], +'names': ['proxy36', +
Re: FBR
+1 lgtm On Thu, Sep 24, 2020 at 4:45 PM Pierre-Yves Chibon wrote: > On Thu, Sep 24, 2020 at 10:28:56AM -0400, Stephen John Smoogen wrote: > > On Thu, 24 Sep 2020 at 10:24, Pierre-Yves Chibon > > wrote: > > > > > On Thu, Sep 24, 2020 at 10:11:11AM -0400, Stephen John Smoogen wrote: > > > > Need to fix opendkim on bastion > > > > > > > > I merged a fix in https://pagure.io/fedora-infrastructure/issue/9250 > but > > > > have not run the playbook for bastion to push this out yet. I would > like > > > to > > > > get a +1 or -1 on this before doing that. [I can remove the merge > also if > > > > that is better.] > > > > > > Would you have a link to the commit(s) with the fix? > > > > > > > > Durh > > > > https://pagure.io/fedora-infra/ansible/pull-request/260 > > Thanks! > > Seems to be only copr related, right? > > +1 for me > > > Pierre > ___ > 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 > ___ 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
Re: FBR
On Thu, Sep 24, 2020 at 10:28:56AM -0400, Stephen John Smoogen wrote: > On Thu, 24 Sep 2020 at 10:24, Pierre-Yves Chibon > wrote: > > > On Thu, Sep 24, 2020 at 10:11:11AM -0400, Stephen John Smoogen wrote: > > > Need to fix opendkim on bastion > > > > > > I merged a fix in https://pagure.io/fedora-infrastructure/issue/9250 but > > > have not run the playbook for bastion to push this out yet. I would like > > to > > > get a +1 or -1 on this before doing that. [I can remove the merge also if > > > that is better.] > > > > Would you have a link to the commit(s) with the fix? > > > > > Durh > > https://pagure.io/fedora-infra/ansible/pull-request/260 Thanks! Seems to be only copr related, right? +1 for me Pierre ___ 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
Re: FBR
On Thu, 24 Sep 2020 at 10:24, Pierre-Yves Chibon wrote: > On Thu, Sep 24, 2020 at 10:11:11AM -0400, Stephen John Smoogen wrote: > > Need to fix opendkim on bastion > > > > I merged a fix in https://pagure.io/fedora-infrastructure/issue/9250 but > > have not run the playbook for bastion to push this out yet. I would like > to > > get a +1 or -1 on this before doing that. [I can remove the merge also if > > that is better.] > > Would you have a link to the commit(s) with the fix? > > Durh https://pagure.io/fedora-infra/ansible/pull-request/260 > > Pierre > ___ > 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 > -- Stephen J Smoogen. ___ 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
Re: FBR
On Thu, Sep 24, 2020 at 10:11:11AM -0400, Stephen John Smoogen wrote: > Need to fix opendkim on bastion > > I merged a fix in https://pagure.io/fedora-infrastructure/issue/9250 but > have not run the playbook for bastion to push this out yet. I would like to > get a +1 or -1 on this before doing that. [I can remove the merge also if > that is better.] Would you have a link to the commit(s) with the fix? Pierre ___ 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
FBR
Need to fix opendkim on bastion I merged a fix in https://pagure.io/fedora-infrastructure/issue/9250 but have not run the playbook for bastion to push this out yet. I would like to get a +1 or -1 on this before doing that. [I can remove the merge also if that is better.] -- Stephen J Smoogen. ___ 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
Re: FBR: increase koji ram to 32 GB
This has been done. On Mon, 21 Sep 2020 at 16:02, Kevin Fenzi wrote: > On Mon, Sep 21, 2020 at 03:51:31PM -0400, Stephen John Smoogen wrote: > > Currently koji01 and koji02 are using 16 GB and need 32 GB . Bump each > > guest in ansible and via virsh commands. > > +1. we have tons of free memory there, should use it. > > 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 > -- Stephen J Smoogen. ___ 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
Re: FBR: increase koji ram to 32 GB
On Mon, Sep 21, 2020 at 03:51:31PM -0400, Stephen John Smoogen wrote: > Currently koji01 and koji02 are using 16 GB and need 32 GB . Bump each > guest in ansible and via virsh commands. +1. we have tons of free memory there, should use it. 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
Re: FBR: increase koji ram to 32 GB
On Mon, Sep 21, 2020 at 3:52 PM Stephen John Smoogen wrote: > > > Currently koji01 and koji02 are using 16 GB and need 32 GB . Bump each guest > in ansible and via virsh commands. > +1 -- 真実はいつも一つ!/ Always, there's only one truth! ___ 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
Re: FBR: increase koji ram to 32 GB
On Mon, 21 Sep 2020 at 15:51, Stephen John Smoogen wrote: > > Currently koji01 and koji02 are using 16 GB and need 32 GB . Bump each > guest in ansible and via virsh commands. > > -- > Stephen J Smoogen. > > diff --git a/inventory/group_vars/koji b/inventory/group_vars/koji index 91d7c1b3b..ec3d910b0 100644 --- a/inventory/group_vars/koji +++ b/inventory/group_vars/koji @@ -1,7 +1,7 @@ --- # Define resources for this group of hosts here. lvm_size: 3 -mem_size: 16384 +mem_size: 32768 num_cpus: 16 -- Stephen J Smoogen. ___ 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
FBR: increase koji ram to 32 GB
Currently koji01 and koji02 are using 16 GB and need 32 GB . Bump each guest in ansible and via virsh commands. -- Stephen J Smoogen. ___ 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
Re: FBR: Fix DKIM signing for aws and fedorahosted
On Wed, Sep 02, 2020 at 03:03:24PM -0400, Stephen John Smoogen wrote: > diff --git a/roles/opendkim/files/SigningTable > b/roles/opendkim/files/SigningTable > index 84cb8f78f..81cad91f3 100644 > --- a/roles/opendkim/files/SigningTable > +++ b/roles/opendkim/files/SigningTable > @@ -15,6 +15,10 @@ > *@fedoraproject.org bastion-iad._domainkey.fedoraproject.org > *@lists.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > *@stg.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > +*@aws.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > +*@fedorahosted.org bastion-iad._domainkey.fedoraproject.org > +*@lists.fedorahosted.org bastion-iad._domainkey.fedoraproject.org > +pag...@pkgs.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > pag...@pagure.io bastion._domainkey.pagure.io Looks good. +1 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
Re: FBR: Fix DKIM signing for aws and fedorahosted
On Wed, Sep 2, 2020 at 3:03 PM Stephen John Smoogen wrote: > > diff --git a/roles/opendkim/files/SigningTable > b/roles/opendkim/files/SigningTable > index 84cb8f78f..81cad91f3 100644 > --- a/roles/opendkim/files/SigningTable > +++ b/roles/opendkim/files/SigningTable > @@ -15,6 +15,10 @@ > *@fedoraproject.org bastion-iad._domainkey.fedoraproject.org > *@lists.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > *@stg.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > +*@aws.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > +*@fedorahosted.org bastion-iad._domainkey.fedoraproject.org > +*@lists.fedorahosted.org bastion-iad._domainkey.fedoraproject.org > +pag...@pkgs.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > pag...@pagure.io bastion._domainkey.pagure.io LGTM +1 > > # NON-WILDCARD EXAMPLE > > > -- > Stephen J Smoogen. > > ___ > 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 ___ 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
Re: FBR: Fix DKIM signing for aws and fedorahosted
On Wed, Sep 2, 2020 at 3:03 PM Stephen John Smoogen wrote: > > diff --git a/roles/opendkim/files/SigningTable > b/roles/opendkim/files/SigningTable > index 84cb8f78f..81cad91f3 100644 > --- a/roles/opendkim/files/SigningTable > +++ b/roles/opendkim/files/SigningTable > @@ -15,6 +15,10 @@ > *@fedoraproject.org bastion-iad._domainkey.fedoraproject.org > *@lists.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > *@stg.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > +*@aws.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > +*@fedorahosted.org bastion-iad._domainkey.fedoraproject.org > +*@lists.fedorahosted.org bastion-iad._domainkey.fedoraproject.org > +pag...@pkgs.fedoraproject.org bastion-iad._domainkey.fedoraproject.org > pag...@pagure.io bastion._domainkey.pagure.io > > # NON-WILDCARD EXAMPLE > +1 -- 真実はいつも一つ!/ Always, there's only one truth! ___ 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
FBR: Fix DKIM signing for aws and fedorahosted
diff --git a/roles/opendkim/files/SigningTable b/roles/opendkim/files/SigningTable index 84cb8f78f..81cad91f3 100644 --- a/roles/opendkim/files/SigningTable +++ b/roles/opendkim/files/SigningTable @@ -15,6 +15,10 @@ *@fedoraproject.org bastion-iad._domainkey.fedoraproject.org *@lists.fedoraproject.org bastion-iad._domainkey.fedoraproject.org *@stg.fedoraproject.org bastion-iad._domainkey.fedoraproject.org +*@aws.fedoraproject.org bastion-iad._domainkey.fedoraproject.org +*@fedorahosted.org bastion-iad._domainkey.fedoraproject.org +*@lists.fedorahosted.org bastion-iad._domainkey.fedoraproject.org +pag...@pkgs.fedoraproject.org bastion-iad._domainkey.fedoraproject.org pag...@pagure.io bastion._domainkey.pagure.io # NON-WILDCARD EXAMPLE -- Stephen J Smoogen. ___ 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
Re: FBR: Pre GA tasks
+1 here from the updated diff On Fri, 24 Apr 2020 at 20:33, Stephen John Smoogen wrote: > > Reviewed updated diff. +1 > > > On Fri, 24 Apr 2020 at 12:41, Mohan Boddu wrote: > >> Hi, >> >> On Fri, Apr 24, 2020 at 12:33 PM Kevin Fenzi wrote: >> > >> > On Fri, Apr 24, 2020 at 12:26:06PM -0400, Mohan Boddu wrote: >> > > Hi, >> > > >> > > The following changes are needed for pre ga tasks, please review them. >> > > >> > > Thanks. >> > >> > 2 things: >> > >> > I do not think we want to change pkgdb-gnome-software-collections.json >> > today. If we do, gnome-software will start offering f32 updates to >> > people before release. >> > >> > I don't think we want to set Frozen: False yet, thats the infra freeze, >> > it's still on until next wed. >> >> Thanks Kevin, here's the updated diff. >> >> > >> > Otherwise looks ok to me. >> > >> > 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 >> ___ >> 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 >> > > > -- > Stephen J Smoogen. > > ___ > 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 > ___ 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
Re: FBR: reboot ppc9-02
On Sat, 25 Apr 2020 at 00:33, Kevin Fenzi wrote: > ppc9-02 is in a odd state. Guests are running ok, but the host itself is > hanging any ansible runs against it. :( Usually this is a sign of some > stuck hardware. > > I've disabled the builders on it and once builds finish on them I would > like to update and reboot ppc9-02. Due to existing builds this may be > later this weekend... > > +1s? > +1 from me > 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 > ___ 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
Re: FBR: Fix DNS to match closer zones
On Sun, 26 Apr 2020 at 17:43, Stephen John Smoogen wrote: > Currently several countries are getting routed to proxies which are timing > out for them. This should 'fix' some though I expect we will need to break > this out further per continental region. > > diff --git a/roles/dns/files/named.conf b/roles/dns/files/named.conf > index c8b95b9..135ec69 100644 > --- a/roles/dns/files/named.conf > +++ b/roles/dns/files/named.conf > @@ -610,7 +610,7 @@ view "RDU2" { > > // The zones > view "NA" { > -match-clients { US; CA; MX; }; > +match-clients { US; CA; MX; BM; GL; }; > recursion no; > // no rate-limit on internal requests > rate-limit { > @@ -636,9 +636,10 @@ view "NA" { > }; > > > -// This is not "EU" countries, I just wanted a short way to represent > Europe. > +// This should have been EME and during the next freeze break should be > made as such. > view "EU" { > -match-clients { AT; BE; BG; CY; CZ; DE; DK; EE; ES; FI; FR; GR; > HU; IT; LT; LU; LV; MT; NL; PL; PT; RO; RU; SE; UA; GB; IE; IS; NO; }; > + match-clients { AD; AL; AT; AX; BA; BE; BG; CH; CZ; DE; DK; EE; > ES; FI; FO; FR; GB; GG; GI; GR; HR; HU; IE; IM; IS; IT; JE; LI; LT; LU; LV; > MC; ME; MK; MT; NL; NO; PL; PT; RO; RS; RU; SE; SI; SJ; SK; SM; UA; VA; AE; > AM; AZ; BH; CY; GE; IL; IQ; JO; KW; LB; OM; QA; SA; TR; YE; }; > + > recursion no; > zone "fedoraproject.org" { > type master; > @@ -660,7 +661,7 @@ view "EU" { > }; > > view "APAC" { > -match-clients { AE; AF; AM; AU; AZ; BD; BH; BN; BT; CC; CN; CX; > CY; GE; HK; ID; IL; IN; IO; IQ; IR; JO; JP; KG; KH; KP; KR; KW; KZ; LA; LB; > LK; MM; MN; MO; MV; MY; NP; NZ; OM; PH; PK; PS; QA; RU; SA; SG; SY; TH; TJ; > TL; TM; TR; TW; UZ; VN; YE; }; > +match-clients { AF; BD; BN; BT; CN; HK; ID; IN; JP; KG; KH; KZ; > LA; LK; MM; MN; MO; MV; MY; NP; PH; PK; SG; TH; TJ; TL; TM; UZ; VN; AS; AU; > CC; CK; CX; FJ; FM; GU; HM; KI; MH; MP; NC; NF; NR; NU; NZ; PF; PG; PN; PW; > SB; TK; TO; TV; UM; VU; WF; WS; } > recursion no; > zone "fedoraproject.org" { > type master; > > +1 > > -- > Stephen J Smoogen. > > ___ > 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 > ___ 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
Re: FBR: Fix DNS to match closer zones
On Sun, 26 Apr 2020 at 14:40, Kevin Fenzi wrote: > On Sun, Apr 26, 2020 at 11:33:45AM -0400, Stephen John Smoogen wrote: > > Currently several countries are getting routed to proxies which are > timing > > out for them. This should 'fix' some though I expect we will need to > break > > this out further per continental region. > > Is there somewhere you are getting these values? > > It seems fine enough to me, but also potentially disruptive... but I > guess we can back it out soon if it causes problems. > > So it looks like the original list was made from https://github.com/lukes/ISO-3166-Countries-with-Regional-Codes which put most of the Middle East in Asia. I compared it to https://gist.github.com/richjenks/15b75f1960bc3321e295 which listed things a little closer to major regional networks. I then grepped, sorted from the first list Western Asia and looked to see if they were EMEA in the second list. > So, +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 > -- Stephen J Smoogen. ___ 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
Re: FBR: Fix DNS to match closer zones
On Sun, Apr 26, 2020 at 11:33:45AM -0400, Stephen John Smoogen wrote: > Currently several countries are getting routed to proxies which are timing > out for them. This should 'fix' some though I expect we will need to break > this out further per continental region. Is there somewhere you are getting these values? It seems fine enough to me, but also potentially disruptive... but I guess we can back it out soon if it causes problems. So, +1 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
FBR: Fix DNS to match closer zones
Currently several countries are getting routed to proxies which are timing out for them. This should 'fix' some though I expect we will need to break this out further per continental region. diff --git a/roles/dns/files/named.conf b/roles/dns/files/named.conf index c8b95b9..135ec69 100644 --- a/roles/dns/files/named.conf +++ b/roles/dns/files/named.conf @@ -610,7 +610,7 @@ view "RDU2" { // The zones view "NA" { -match-clients { US; CA; MX; }; +match-clients { US; CA; MX; BM; GL; }; recursion no; // no rate-limit on internal requests rate-limit { @@ -636,9 +636,10 @@ view "NA" { }; -// This is not "EU" countries, I just wanted a short way to represent Europe. +// This should have been EME and during the next freeze break should be made as such. view "EU" { -match-clients { AT; BE; BG; CY; CZ; DE; DK; EE; ES; FI; FR; GR; HU; IT; LT; LU; LV; MT; NL; PL; PT; RO; RU; SE; UA; GB; IE; IS; NO; }; + match-clients { AD; AL; AT; AX; BA; BE; BG; CH; CZ; DE; DK; EE; ES; FI; FO; FR; GB; GG; GI; GR; HR; HU; IE; IM; IS; IT; JE; LI; LT; LU; LV; MC; ME; MK; MT; NL; NO; PL; PT; RO; RS; RU; SE; SI; SJ; SK; SM; UA; VA; AE; AM; AZ; BH; CY; GE; IL; IQ; JO; KW; LB; OM; QA; SA; TR; YE; }; + recursion no; zone "fedoraproject.org" { type master; @@ -660,7 +661,7 @@ view "EU" { }; view "APAC" { -match-clients { AE; AF; AM; AU; AZ; BD; BH; BN; BT; CC; CN; CX; CY; GE; HK; ID; IL; IN; IO; IQ; IR; JO; JP; KG; KH; KP; KR; KW; KZ; LA; LB; LK; MM; MN; MO; MV; MY; NP; NZ; OM; PH; PK; PS; QA; RU; SA; SG; SY; TH; TJ; TL; TM; TR; TW; UZ; VN; YE; }; +match-clients { AF; BD; BN; BT; CN; HK; ID; IN; JP; KG; KH; KZ; LA; LK; MM; MN; MO; MV; MY; NP; PH; PK; SG; TH; TJ; TL; TM; UZ; VN; AS; AU; CC; CK; CX; FJ; FM; GU; HM; KI; MH; MP; NC; NF; NR; NU; NZ; PF; PG; PN; PW; SB; TK; TO; TV; UM; VU; WF; WS; } recursion no; zone "fedoraproject.org" { type master; -- Stephen J Smoogen. ___ 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
Re: FBR: reboot ppc9-02
+! On Fri, 24 Apr 2020 at 18:24, Kevin Fenzi wrote: > ppc9-02 is in a odd state. Guests are running ok, but the host itself is > hanging any ansible runs against it. :( Usually this is a sign of some > stuck hardware. > > I've disabled the builders on it and once builds finish on them I would > like to update and reboot ppc9-02. Due to existing builds this may be > later this weekend... > > +1s? > > 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 > -- Stephen J Smoogen. ___ 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
FBR: Reboot of ppc09-02
Server has some problems with services and guests. We would like to reboot the system to clear some issues being seen. -- Stephen J Smoogen. ___ 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
FBR: reboot ppc9-02
ppc9-02 is in a odd state. Guests are running ok, but the host itself is hanging any ansible runs against it. :( Usually this is a sign of some stuck hardware. I've disabled the builders on it and once builds finish on them I would like to update and reboot ppc9-02. Due to existing builds this may be later this weekend... +1s? 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
Re: FBR: Pre GA tasks
Reviewed updated diff. +1 On Fri, 24 Apr 2020 at 12:41, Mohan Boddu wrote: > Hi, > > On Fri, Apr 24, 2020 at 12:33 PM Kevin Fenzi wrote: > > > > On Fri, Apr 24, 2020 at 12:26:06PM -0400, Mohan Boddu wrote: > > > Hi, > > > > > > The following changes are needed for pre ga tasks, please review them. > > > > > > Thanks. > > > > 2 things: > > > > I do not think we want to change pkgdb-gnome-software-collections.json > > today. If we do, gnome-software will start offering f32 updates to > > people before release. > > > > I don't think we want to set Frozen: False yet, thats the infra freeze, > > it's still on until next wed. > > Thanks Kevin, here's the updated diff. > > > > > Otherwise looks ok to me. > > > > 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 > ___ > 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 > -- Stephen J Smoogen. ___ 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
Re: FBR: Pre GA tasks
Hi, On Fri, Apr 24, 2020 at 12:33 PM Kevin Fenzi wrote: > > On Fri, Apr 24, 2020 at 12:26:06PM -0400, Mohan Boddu wrote: > > Hi, > > > > The following changes are needed for pre ga tasks, please review them. > > > > Thanks. > > 2 things: > > I do not think we want to change pkgdb-gnome-software-collections.json > today. If we do, gnome-software will start offering f32 updates to > people before release. > > I don't think we want to set Frozen: False yet, thats the infra freeze, > it's still on until next wed. Thanks Kevin, here's the updated diff. > > Otherwise looks ok to me. > > 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 diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 97afa7c..c8fdc31 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -150,8 +150,8 @@ ostree = { # In the case of testing, also inject the last stable updates "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/updates/f[[ release.version_int ]]-updates/compose/Everything/$basearch/os/", [% endif %] -# For F32 the compose location is going to be under /compose/branched/ -[% if release.version_int == 32 %] +# For F33 the compose location is going to be under /compose/branched/ +[% if release.version_int == 33 %] "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/" [% else %] "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/" diff --git a/roles/releng/files/branched b/roles/releng/files/branched index e3a5bd3..74f08d9 100644 --- a/roles/releng/files/branched +++ b/roles/releng/files/branched @@ -1,3 +1,3 @@ # branched compose -MAILTO=releng-c...@lists.fedoraproject.org -15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f32 && /usr/local/bin/lock-wrapper branched-compose "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary +#MAILTO=releng-c...@lists.fedoraproject.org +#15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f32 && /usr/local/bin/lock-wrapper branched-compose "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary diff --git a/roles/releng/files/cloud-updates b/roles/releng/files/cloud-updates index 8c1df3a..0ef075f 100644 --- a/roles/releng/files/cloud-updates +++ b/roles/releng/files/cloud-updates @@ -2,9 +2,9 @@ MAILTO=releng-c...@lists.fedoraproject.org 15 6 * * * root TMPDIR=`mktemp -d /tmp/CloudF30.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f30 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR -#Fedora 29 Cloud nightly compose -#MAILTO=releng-c...@lists.fedoraproject.org -#15 7 * * * root TMPDIR=`mktemp -d /tmp/CloudF29.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f29 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR +#Fedora 32 Cloud nightly compose +MAILTO=releng-c...@lists.fedoraproject.org +15 7 * * * root TMPDIR=`mktemp -d /tmp/CloudF32.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f32 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR #Fedora 31 Cloud nightly compose MAILTO=releng-c...@lists.fedoraproject.org diff --git a/roles/releng/files/container-updates b/roles/releng/files/container-updates index 769b78f..ac0dc25 100644 --- a/roles/releng/files/container-updates +++ b/roles/releng/files/container-updates @@ -6,6 +6,6 @@ MAILTO=releng-c...@lists.fedoraproject.org MAILTO=releng-c...@lists.fedoraproject.org 45 7 * * * root TMPDIR=`mktemp -d /tmp/containerF30.XX`
Re: FBR: Pre GA tasks
On Fri, Apr 24, 2020 at 12:26:06PM -0400, Mohan Boddu wrote: > Hi, > > The following changes are needed for pre ga tasks, please review them. > > Thanks. 2 things: I do not think we want to change pkgdb-gnome-software-collections.json today. If we do, gnome-software will start offering f32 updates to people before release. I don't think we want to set Frozen: False yet, thats the infra freeze, it's still on until next wed. Otherwise looks ok to me. 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
FBR: Pre GA tasks
Hi, The following changes are needed for pre ga tasks, please review them. Thanks. diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 97afa7c..c8fdc31 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -150,8 +150,8 @@ ostree = { # In the case of testing, also inject the last stable updates "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/updates/f[[ release.version_int ]]-updates/compose/Everything/$basearch/os/", [% endif %] -# For F32 the compose location is going to be under /compose/branched/ -[% if release.version_int == 32 %] +# For F33 the compose location is going to be under /compose/branched/ +[% if release.version_int == 33 %] "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/branched/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/" [% else %] "https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/" diff --git a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json index c3555df..4b197dc 100644 --- a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json +++ b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json @@ -12,14 +12,14 @@ "version": "devel" }, { - "allow_retire": true, + "allow_retire": false, "branchname": "f32", "date_created": "2014-05-14 12:36:15", "date_updated": "2020-02-11 17:07:23", "dist_tag": ".fc32", "koji_name": "f32", "name": "Fedora", - "status": "Under Development", + "status": "Active", "version": "32" }, { diff --git a/roles/releng/files/branched b/roles/releng/files/branched index e3a5bd3..74f08d9 100644 --- a/roles/releng/files/branched +++ b/roles/releng/files/branched @@ -1,3 +1,3 @@ # branched compose -MAILTO=releng-c...@lists.fedoraproject.org -15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f32 && /usr/local/bin/lock-wrapper branched-compose "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary +#MAILTO=releng-c...@lists.fedoraproject.org +#15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f32 && /usr/local/bin/lock-wrapper branched-compose "PYTHONMALLOC=debug LANG=en_US.UTF-8 ./nightly.sh" && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary diff --git a/roles/releng/files/cloud-updates b/roles/releng/files/cloud-updates index 8c1df3a..0ef075f 100644 --- a/roles/releng/files/cloud-updates +++ b/roles/releng/files/cloud-updates @@ -2,9 +2,9 @@ MAILTO=releng-c...@lists.fedoraproject.org 15 6 * * * root TMPDIR=`mktemp -d /tmp/CloudF30.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f30 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR -#Fedora 29 Cloud nightly compose -#MAILTO=releng-c...@lists.fedoraproject.org -#15 7 * * * root TMPDIR=`mktemp -d /tmp/CloudF29.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f29 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR +#Fedora 32 Cloud nightly compose +MAILTO=releng-c...@lists.fedoraproject.org +15 7 * * * root TMPDIR=`mktemp -d /tmp/CloudF32.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f32 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR #Fedora 31 Cloud nightly compose MAILTO=releng-c...@lists.fedoraproject.org diff --git a/roles/releng/files/container-updates b/roles/releng/files/container-updates index 769b78f..ac0dc25 100644 --- a/roles/releng/files/container-updates +++ b/roles/releng/files/container-updates @@ -6,6 +6,6 @@ MAILTO=releng-c...@lists.fedoraproject.org MAILTO=releng-c...@lists.fedoraproject.org 45 7 * * * root TMPDIR=`mktemp -d /tmp/containerF30.XX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f30 && LANG=en_US.UTF-8 ./container-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR -# Fedora 29 Container Updates nightly compose
Re: FBR (?) STAGING: Support Fedora ELN for Greenwave
On Thu, Apr 23, 2020 at 04:24:05PM -0400, Stephen Gallagher wrote: > Looks fine to me. Do note that staging isn't frozen ever, so we can just apply this and do whats needed to make it live (run greenwave playbook, starting new greenwave image build, deploy new pods). 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
Re: FBR (?) STAGING: Support Fedora ELN for Greenwave
LGTM +1 On Thu, Apr 23, 2020 at 4:24 PM Stephen Gallagher wrote: > > > ___ > 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 ___ 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
FBR (?) STAGING: Support Fedora ELN for Greenwave
From 6c9da110bdb380beb0192d4188725e91d2dc3549 Mon Sep 17 00:00:00 2001 From: Stephen Gallagher Date: Thu, 23 Apr 2020 16:23:00 -0400 Subject: [PATCH] STAGING: Support Fedora ELN for Greenwave Signed-off-by: Stephen Gallagher --- roles/openshift-apps/greenwave/templates/fedora.yaml | 12 1 file changed, 12 insertions(+) diff --git a/roles/openshift-apps/greenwave/templates/fedora.yaml b/roles/openshift-apps/greenwave/templates/fedora.yaml index a927ae500a1c8a3d9ab2a56542d7ebea74de82dd..68738dce40900ef081003af13f3fe0bfe66dd90b 100644 --- a/roles/openshift-apps/greenwave/templates/fedora.yaml +++ b/roles/openshift-apps/greenwave/templates/fedora.yaml @@ -52,10 +52,13 @@ rules: --- !Policy id: "taskotron_release_critical_tasks_for_testing" product_versions: - fedora-rawhide +{% if env == 'staging' %} + - fedora-eln +{% endif %} - fedora-33 - fedora-32 - fedora-31 - fedora-30 - fedora-29 @@ -67,10 +70,13 @@ rules: --- !Policy id: "taskotron_release_critical_tasks_for_stable" product_versions: - fedora-rawhide +{% if env == 'staging' %} + - fedora-eln +{% endif %} - fedora-33 - fedora-32 - fedora-31 - fedora-30 - fedora-29 @@ -131,10 +137,13 @@ rules: [] --- !Policy # openQA policies id: "openqa_release_critical_tasks_for_testing" product_versions: - fedora-rawhide +{% if env == 'staging' %} + - fedora-eln +{% endif %} - fedora-32 - fedora-31 - fedora-30 - fedora-29 decision_context: bodhi_update_push_testing @@ -145,10 +154,13 @@ rules: --- !Policy id: "openqa_release_critical_tasks_for_stable" product_versions: - fedora-rawhide +{% if env == 'staging' %} + - fedora-eln +{% endif %} - fedora-32 - fedora-31 - fedora-30 - fedora-29 decision_context: bodhi_update_push_stable -- 2.26.0 ___ 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
Re: [FBR] fix openshift
On Thu, Apr 23, 2020 at 02:35:32PM +0200, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > This morning as I was trying to build a new distgit-bugzilla-sync build in > staging, I ran into the issue that the build never started. > It seems it was related to openshift not being able to resolve correctly: > registry.redhat.io. > > Once Clément pointed me to the right direction, I adjusted staging as follow: > https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=e371f8b0ceef30639facb7ac7a70c27beb3e689c > and I was able to do a new build. > > I would like to apply the same fix to production (ie: > roles/hosts/files/os-hosts). > > Thoughts? +1 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
Re: [FBR] fix openshift
On Thu, Apr 23, 2020 at 8:35 AM Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > This morning as I was trying to build a new distgit-bugzilla-sync build in > staging, I ran into the issue that the build never started. > It seems it was related to openshift not being able to resolve correctly: > registry.redhat.io. > > Once Clément pointed me to the right direction, I adjusted staging as follow: > https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=e371f8b0ceef30639facb7ac7a70c27beb3e689c > and I was able to do a new build. > > I would like to apply the same fix to production (ie: > roles/hosts/files/os-hosts). > > Thoughts? > +1 from me. Seems small, simple, and reasonable to do. -- 真実はいつも一つ!/ Always, there's only one truth! ___ 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
Re: [FBR] fix openshift
On Thu, 23 Apr 2020 at 14:43, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > This morning as I was trying to build a new distgit-bugzilla-sync build in > staging, I ran into the issue that the build never started. > It seems it was related to openshift not being able to resolve correctly: > registry.redhat.io. > > Once Clément pointed me to the right direction, I adjusted staging as > follow: > > https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=e371f8b0ceef30639facb7ac7a70c27beb3e689c > and I was able to do a new build. > > I would like to apply the same fix to production (ie: > roles/hosts/files/os-hosts). > > Thoughts? > It is a small change and without it builds are broken so +1 from me. > Thanks, > Pierre > ___ > 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 > ___ 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