On Sat, Apr 27, 2024 at 04:42:50PM GMT, Peter Robinson wrote:
> On Fri, 26 Apr 2024 at 22:06, Jonathan Steffan
> wrote:
> >
> > Kevin,
> >
> > Awesome. Once we sort out how we are going to support [releng] Issue #10765
> > (systemd-boot signing) will this upgrade enable us to consider signing
>
Hey folks.
Just a heads up that I have migrated sigul to the new 1.2 version with
rhel9 vault/bridge.
Please let me know if you see any signing issues in the coming days.
It seems to be processing as expected, so hopefully everything will be
transparent to everyone, and look for some nice
On Thu, Apr 25, 2024 at 08:46:17PM GMT, Paul Maconi wrote:
> Hello everyone! My name is Paul Maconi, aka @aggraxis on matrix, across
> the FAS, and a bunch of other places. I attended the meeting earlier
> today. Thank you again for the warm welcome.
Welcome again. Nice seeing you around...
With the release of Fedora 40 yesterday, infrastructure freeze is now
over.
Our next freeze is for Fedora 41 beta, currently scheduled for
2024-08-20.
kevin
signature.asc
Description: PGP signature
--
___
infrastructure mailing list --
Thanks everyone.
I got the builders updated. Hopefully that will do the right thing for
now. ;)
kevin
signature.asc
Description: PGP signature
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email
In the run up to f40 final we were using a koji with a patch to _not_
enable the builroot repo when making containers via kiwi plugin.
This was to fix the fact that pulling from the buildroot repo pulls
unsigned rpms, making all the rpms installed in the container unsigned.
Foolishly, I pulled a
On Thu, Apr 18, 2024 at 07:40:11PM GMT, darknao wrote:
> Hi o/
>
> I would like to retire the old labs.fedoraproject.org website and redirect it
> to the new one on the main site at https://fedoraproject.org/labs/
>
> If possible, the redirect would be enabled on F40 release day so we don't
>
When I did the updates before final freeze, I missed updating the
builders with the latest koji package from the f39-infra tag.
At the time for some reason I thought it didn't matter, because the
patches were all hub related, but turns out thats not the case.
2 of the patches affect builders:
*
On Sat, Apr 06, 2024 at 04:34:05PM +0100, jdie...@gmail.com wrote:
> On Tue, 2024-04-02 at 16:55 -0700, Kevin Fenzi wrote:
> > On Tue, Apr 02, 2024 at 09:28:31PM +0100, Jonathan Dieter wrote:
> > > * Alternatively, we could update whatever's calling createrepo_c
> > >
On Wed, Apr 03, 2024 at 05:22:52PM +0530, Aditi Mishra wrote:
> Hello,
>
> Just for the information, I'm very new to fedora but want to contribute in
> the development of future fedora.
>
> Below are my specfications:
>
> IRC handle: aditiLinux
>
> * Skills that I can offer:
>
> -
On Tue, Apr 02, 2024 at 09:28:31PM +0100, Jonathan Dieter wrote:
> On Sat, 2024-03-30 at 09:39 -0700, Kevin Fenzi wrote:
> > On Fri, Mar 29, 2024 at 11:32:10PM +, Jonathan Dieter wrote:
> > > On Wed, 2024-03-27 at 09:12 -0700, Kevin Fenzi wrote:
> > > > Our next
On Tue, Apr 02, 2024 at 09:39:46PM +0200, Miroslav Suchý wrote:
> Dne 02. 04. 24 v 7:45 odp. Kevin Fenzi napsal(a):
> > On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
> > > Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
> > > > FYI I plan to con
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 40
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 40 when it's available.
You can see a list of hosts that do not freeze by checking out
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
> Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
> > FYI I plan to continue in AWS cleanup on Friday.
> >
> > I waited till Freeze is over - just to be safe. And now I want to delete
> > the old AMIs. Likely in several waves.
On Tue, Apr 02, 2024 at 01:21:55AM +0200, Miroslav Suchý wrote:
> Here comes January edition of resources running in AWS. It's a snapshot of
> resources running today.
>
> Per request of Miro Vadkerti I grouped it by (FedoraGroup, region,
> ServiceName). I will try to make it more compact next
On Mon, Apr 01, 2024 at 09:45:18PM +0200, Miroslav Suchý wrote:
> This is without AMIs and Snapshots that still produce looong list.
>
> Region: us-west-1
> Volumes - [id name (attached to instance, owner)]:
> * vol-0d7702fbe7ab94c6f N/A (famna.fedorainfracloud.org, N/A)
Oops. Thiw was me. I
On Fri, Mar 29, 2024 at 11:32:10PM +, Jonathan Dieter wrote:
> On Wed, 2024-03-27 at 09:12 -0700, Kevin Fenzi wrote:
> > Our next freeze is for Fedora 40 Final, currently scheduled for
> > 2024-04-02, which is NEXT TUESDAY!
>
> Could you please update fedora-
Hey folks, started a discussion thread:
https://discussion.fedoraproject.org/t/planning-for-infra-and-releng-hackfest-at-flock-2024/110244
Please read and reply over there (or I guess here if you really must ;)
kevin
signature.asc
Description: PGP signature
--
With the release of Fedora 40 Beta yesterday,
infrastructure freeze is now over.
Our next freeze is for Fedora 40 Final, currently scheduled for
2024-04-02, which is NEXT TUESDAY!
kevin
signature.asc
Description: PGP signature
--
___
infrastructure
I'd like to update koji on builders.
This build (
https://koji.fedoraproject.org/koji/buildinfo?buildID=2423765 )
has added:
* A fix to make kiwi builds only use passed repos if there is one passed
https://pagure.io/koji/pull-request/4061 ).
I have tested this in staging and it does fix the
On Wed, Mar 20, 2024 at 12:41:49PM +1000, Ryan Lerch wrote:
> Working on switching kerneltest over to openshift, and the final step
> is to update the proxies:
>
> https://pagure.io/fedora-infra/ansible/pull-request/1872
>
> and then also run the iplison playbook so the oidc config gets copied
>
On Thu, Mar 14, 2024 at 09:58:47AM +0100, Miroslav Suchý wrote:
> FYI I plan to continue in AWS cleanup on Friday.
>
> I waited till Freeze is over - just to be safe. And now I want to delete the
> old AMIs. Likely in several waves. Going from oldest to ~2021.
Sure, but note that freeze is only
Planned Outage - fedora.im / chat.fedoraproject.org matrix server - 2024-03-14
07:00 UTC
There will be an outage starting at 2024-03-14 07:00UTC,
which will last approximately 1 hour.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
On Wed, Mar 06, 2024 at 11:18:25PM -, Ryan Bach wrote:
> I want to know because maybe we can see hyperkitty updated after that.
It should be the day after the Beta is released.
We missed next week's 'early' date, so the next target is a week from
next tuesday.
Note though that
Thanks. This is done now.
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:
We need a newer pungi version that adds support for kiwi and has changes
for osbuild arm minimal. These are both things we are trying to land for
beta.
There's a 4.6.2 release upstream that we need.
So, I'd like to build this for f39 (which our compose hosts are) and
update them.
If something
Hey everyone.
The koji builders are currently using 6.7.6-200.fc39, which is mostly
fine, but on i386 builds there's some kind of memory issue and (some)
builds run out of memory and fail. ;(
See: https://pagure.io/fedora-infrastructure/issue/11775
I'd like to upgrade the buildhw-x86*
On Fri, Mar 01, 2024 at 04:20:30PM +0100, Miroslav Suchý wrote:
> This is without AMIs and Snapshots that still produce looong list.
>
> Region: ap-southeast-1
> Instances: (name, id, owner)
> * proxy38 (i-0a1ee820c765d573c, N/A)
> Volumes - [id name (attached to instance, owner)]:
> *
Greetings.
We are now in the infrastructure freeze leading up to the Fedora 40
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 40 Beta when it's available.
You can see a list of hosts that do not freeze by
Planned Outage - koji upgrade - 2024-02-21 21:00 UTC
There will be an outage starting at 2024-02-21 21:00 UTC,
which will last approximately 3 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2024-02-21 21:00UTC'
On Wed, Feb 14, 2024 at 02:20:39PM +0100, Sandro wrote:
> Hi,
>
> Some script running on pkgs01.iad2.fedoraproject.org sends a report titled
> "Packages Restricting Arches" to arch-exclu...@lists.fp.o every night
> (between 04:00 and 05:00 UTC)[1]. I was wondering where I could find that
>
On Mon, Feb 12, 2024 at 08:40:32PM +0100, Miroslav Suchý wrote:
> Dne 09. 02. 24 v 20:34 Miroslav Suchý napsal(a):
> > > I think we should leave "GA" images. Even thought they are EOL for the
> > > most part, I think it's still possibly nice to be able to spin one up to
> > > test something or the
On Mon, Feb 12, 2024 at 11:10:57AM -0500, Dusty Mabe wrote:
>
>
> On 2/12/24 05:14, Miroslav Suchý wrote:
> > I was wondering why I cannot tag some images in AWS and I found that some
> > GA images in AWS have different owner.
> >
> > I.e. all our images has
> >
> > Owner account ID
On Mon, Feb 12, 2024 at 09:04:25AM -0500, Stephen Smoogen wrote:
> On Mon, 12 Feb 2024 at 06:12, Marius Schwarz wrote:
>
> > Hi,
> >
> > as die Infrastructure ML did not react ( or could not react ;) ), I
> > requested the removal at that antispam blacklist.
> >
> >
> I did not see any email to
On Thu, Feb 08, 2024 at 05:09:27PM +0100, Miroslav Suchý wrote:
> Yesterday I finally deleted all Fedora-AtomicHost AMIs and associated
> snapshots (it took whole night to finish).
>
> This time, I know we have to start with AMIs first (and only then delete
> snapshots).
>
> Where I can
On Wed, Feb 07, 2024 at 02:49:01PM +0100, Miroslav Suchý wrote:
> This is a resource from AWS that does not have propper tag:
>
> Region: eu-west-1
> Volumes - [id name (attached to instance, owner)]:
> * vol-0e5efafe67ed944ad N/A (apps-containerization, N/A)
>
> Can the owner please tag (or
There will be an outage starting at 2024-02-07 22:00UTC,
which will last approximately 6 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2024-02-07 22:00UTC'
Reason for outage:
We will be applying updates and
On Thu, Dec 21, 2023 at 01:19:46PM -0700, Tim Flink wrote:
> What are the general rules around default bugzilla assignee for packages? I'm
> trying to set the default assignee for rocm-cmake to rocm-packagers-sig but
> keep getting an error:
>
> Unable to update the bugzilla assignee(s):
Just a gentle reminder that the holiday season is coming up.
Many contributors have more time to work on things,
others are spending time away with friends and family.
When you push changes during the holidays be extra aware
of anything that might cause outages or breakage that might
pull
On Sat, Dec 02, 2023 at 10:57:11PM +0100, Miroslav Suchý wrote:
> Dne 02. 12. 23 v 22:45 Miroslav Suchý napsal(a):
> > I wonder - do we have written retention policy for our images? Do we
> > want to keep the old one? Public ones? Private ones?
>
> It seems that Fedora Atomic Host is EOLed since
I'm happy to announce that We have approved a new member in our
sysadmin-main group:
praiskup
This is the core group of trusted folks that high level access to most
everything in fedora infrastructure.
As many of you know, he's wrangled copr for quite some time, as well as
taking on other
o.
So thats:
[#meeting-3:fedoraproject.org](https://matrix.to/#/%23meeting-3%3Afedoraproject.org)
kevin
--
>
> Chris
>
> wt., 28 lis 2023 o 01:29 Kevin Fenzi napisał(a):
>
> > On Mon, Nov 27, 2023 at 07:18:55PM +0100, Krzysztof Kuberski wrote:
> > > Hello,
> &
On Mon, Nov 27, 2023 at 07:18:55PM +0100, Krzysztof Kuberski wrote:
> Hello,
>
> I wish to help in contributing at Fedora, below some informations about me
>
> IRC - DeviC3
>
> Skills/job:
> Actually, I'm working as sysadmin in the RHEL environment and a secondary
> job as LSE in the same
On Thu, Nov 23, 2023 at 04:38:01PM +0100, Miroslav Suchý wrote:
>
> I had time to investigate it a bit:
Thanks for digging into it.
...snip...
>
> Based on this founding I propose:
>
> 1) Delete **all** snapshots without FedoraGroup tag older than - let say -
> 2021. This way we can
Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC
There will be an outage starting at 2023-11-17 13:00UTC,
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d
Greetings everyone.
Now that fedora 39 is out the door, I'd like to schedule some
retirements of a few old services:
fedmsg-irc: This is a old fedmsg process that send fedmsg's to IRC.
Currently we have one running in production and one in staging, both on
rhel7 vm's that we would like to
On Mon, Nov 06, 2023 at 10:22:57PM +0100, Miroslav Suchý wrote:
> Dne 06. 11. 23 v 20:45 Kevin Fenzi napsal(a):
> > Can we get what volume they are snapshots of? Perhaps the volume name
> > would help us figure things out?
>
> Most of the 6GiB volumes like snap-098326d4
With the release of Fedora 39 yesterday, infrastructure freeze is now
over.
Our next freeze is for Fedora 40 beta, currently scheduled for
2024-02-20.
kevin
signature.asc
Description: PGP signature
___
infrastructure mailing list --
On Thu, Nov 02, 2023 at 10:32:20AM +0100, Miroslav Suchý wrote:
> We have (almost) all instances and volumes properly tagged. Now let check
> Snapshots.
Thanks for continuing to drive this forward. ;)
> OMG - there are A LOT of them. The list has 97k lines! Because of the size I
> will not
On Mon, Oct 30, 2023 at 08:46:04PM +0100, Miroslav Suchý wrote:
> From
>
> https://us-east-1.console.aws.amazon.com/iamv2/home?region=us-east-2#/home
>
> Attention: Extended Deadline for Updating Your Access Permissions - December
> 11, 2023
> AWS has discontinued use of old IAM permissions for
On Wed, Oct 11, 2023 at 08:13:50AM -0500, Blake Ridgway wrote:
> Good day Fedora Infrastructure team,
>
> I'm Blake Ridgway. My IRC alias is /Zormak/ and my Matrix alias is
> /@blakeridgway:fedora.im. /I am reaching out to introduce myself to the
> Fedora Infrastructure team and express my
On Thu, Oct 05, 2023 at 11:27:56AM -0400, Stephen Smoogen wrote:
> On Wed, 4 Oct 2023 at 11:52, Kevin Fenzi wrote:
>
> > We tried to get everything working with the new flatpak building setup
> > before freeze, but at the last minute we ran into some issues between
> >
We tried to get everything working with the new flatpak building setup
before freeze, but at the last minute we ran into some issues between
bodhi and the metadata that flatpak builds store in koji. We got several
things sorted out yesterday before freeze, but there's still an issue
with the
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 39
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 39 when it's available.
You can see a list of hosts that do not freeze by checking out
On Mon, Sep 25, 2023 at 05:38:44AM +0200, Miroslav Suchý wrote:
> Now when we have all instances and volumes tagged. I can say who is using
> what resources. Below you will find the aggregated overview of resources we
> are using in AWS.
>
> If you will not mind, I plan to send this overview
On Fri, Sep 22, 2023 at 02:32:00PM +0200, Miroslav Suchý wrote:
> = Current status
>
> We have almost everything tagged with FedoraGroup. There are some small
> leftovers (see bottom of this email).
>
> If no one stop me (or tag it) I will delete them by end of next week.
Awesome. Thanks
With the release of Fedora 39 Beta yesterday, infrastructure freeze is now over.
Our next freeze is for Fedora 39 final release, currently scheduled for
2023-10-03.
kevin
signature.asc
Description: PGP signature
___
infrastructure mailing list --
On Thu, Sep 14, 2023 at 01:35:58PM +0200, Miroslav Suchý wrote:
> I have cleanup a lot. I notified Testing farm, they will tag their resource
> soon.
>
> BTW if you are in CC, then you likely own one of the resources in AWS.
> Please add tag FedoraGroup=* to it. Otherwise it may be deleted.
>
>
On Wed, Sep 13, 2023 at 09:22:27AM +0200, Miroslav Suchý wrote:
> When cleaning the old volumes I find strange error
>
> This volume:
>
> https://ap-southeast-1.console.aws.amazon.com/ec2/home?region=ap-southeast-1#VolumeDetails:volumeId=vol-495d4a40
>
> i.e. vol-495d4a40 in ap-southeast-1
>
>
On Wed, Sep 13, 2023 at 11:17:41AM +0200, Miroslav Suchý wrote:
> Dne 05. 09. 23 v 17:11 Kevin Fenzi napsal(a):
> > So, I think it would be ok to just do anytime, but you can wait until
> > after freeze if you want to be extra careful.
>
>
> Freeze is over. I migrated a
at 12:23 PM Pierre-Yves Chibon
> wrote:
>
> > On Tue, Sep 05, 2023 at 11:35:19AM -0700, Kevin Fenzi wrote:
> > > On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote:
> > > > Hello all, it took us a few years but we are finally getting rid of
>
On Mon, Sep 11, 2023 at 02:40:18PM +0200, Miroslav Suchý wrote:
> Dne 11. 09. 23 v 6:45 Fabian Arrotin napsal(a):
> > AFAIK the ec2 instances in the .centos.org domain are all tagged though,
> > so do you have a list of ec2 instances/volumes that are really from
> > centos and not tagged properly
On Fri, Sep 08, 2023 at 01:45:02AM +0200, Miroslav Suchý wrote:
> Dne 07. 09. 23 v 20:49 Kevin Fenzi napsal(a):
> > Nice! I think dkirwan should know about Discourse-test and mobrien
> > should know about mobrien-test, and I think the rest are centos ones?
>
> Due d
The new fedora-repo-zdicts-2309.1-1.fc38 update has f39 zchunk
dictionaries, which should make the zchunk deltas better for f39.
I'd like to update compose-branched01/compose-rawhide01/compose-x86_01
so we can get this advantage.
I think this is a pretty low impact change and we can always just
On Thu, Sep 07, 2023 at 11:07:15AM -0400, Neal Gompa wrote:
> On Thu, Sep 7, 2023 at 10:15 AM Michal Konecny wrote:
> >
> > So I contacted William Dettelback from quay.io Team about the feedback I
> > got here.
> >
> > This is the e-mail I sent:
> > ```
> > 1) Mock switched to
On Thu, Sep 07, 2023 at 11:28:18AM +0200, Pavel Raiskup wrote:
> JFYI, I just updated the script Mirek had, and created a simple cron job
> on one of our staging VMs that collects some AWS instance statistics.
> Result is hosted here:
>
>
On Wed, Sep 06, 2023 at 06:56:36AM -0400, Stephen Smoogen wrote:
> On Wed, 6 Sept 2023 at 06:51, Sandro wrote:
>
> > On 05-09-2023 21:53, Kevin Fenzi wrote:
> > > I already have the cert ready to push into ansible-private, just need
> > > +1's to run the proxie
Took a look and fixed a number of fedora ones:
> Region: ca-central-1
> Instances:
> Volumes - [id (attached to instance)]:
> * vol-067b5f163d2320171 (cloud-fedora-34-aws-ssd)
> * vol-07a41964b391cbe75 (cloud-fedora-34-aws-ssd)
> * vol-05fa6f0557ab1e44b (cloud-fedora-34-aws-ssd)
> *
On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote:
> Hello all, it took us a few years but we are finally getting rid of the PDC
> project. Thanks to the ARC research we identified use cases in our tooling
> and proposed solution.
>
> The essential functionalities currently provided by
On Mon, Sep 04, 2023 at 01:57:34PM -0400, Neal Gompa wrote:
> On Mon, Sep 4, 2023 at 12:47 PM Pavel Raiskup wrote:
> >
> > On pondělí 4. září 2023 15:35:41 CEST Michal Konecny wrote:
> > > Hi everyone,
> > >
> > > I finished investigation for migration from registry.fp.o to quay.io. It
> > > is
On Fri, Sep 01, 2023 at 02:59:12PM +0200, Michal Konecny wrote:
> Hi everyone,
>
> I did a cleaning in Fedora infra groups in both Github (fedora-infra
> organization https://github.com/fedora-infra) and Pagure (fedora-infra group
> https://pagure.io/group/fedora-infra). I removed the people that
On Mon, Sep 04, 2023 at 08:30:26AM +0200, Fabian Arrotin wrote:
> On 03/09/2023 20:59, Miroslav Suchý wrote:
> > According our SOP
> > https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/aws-access/#_role_and_user_policies
> >
> > Users MUST tag resources with their FedoraGroup tag
On Sun, Sep 03, 2023 at 09:33:49PM +0200, Miroslav Suchý wrote:
> FYI
>
> after I moved manually most of the big volumes to gp3 at the beginning of
> summer, I finally get to write script that converts all the remaining
> volumes.
>
> I run it for two minor regions:
>
> ap-south-1
> Migrating
On Tue, Aug 15, 2023 at 03:06:36PM -0600, Tim Flink wrote:
>
> Has there been a conclusion to this? The AI/ML SIG is looking to request a
> FAS group to manage access to the sigs/ai-ml project in GitLab but we're not
> sure what to request for a name.
>
> Thanks,
>
> Tim
Somehow I didn't
On Mon, Aug 28, 2023 at 01:05:16AM -, Ryan Bach wrote:
> > On Sat, Aug 26, 2023 at 03:28:26AM -, Ryan Bach wrote:
> >
> > Yes? Did you have a question here?
> >
> > I did post here and also in discussion...
> >
> > kevin
> I guess. Will hyperkitty be updated after the freeze is over?
On Sat, Aug 26, 2023 at 03:28:26AM -, Ryan Bach wrote:
> > Greetings.
> >
> > We are now in the infrastructure freeze leading up to the Fedora 39
> > Beta release. This is a pre release freeze.
> >
> > We do this to ensure that our infrastructure is stable and ready to
> > release the Fedora
Greetings.
We are now in the infrastructure freeze leading up to the Fedora 39
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 39 Beta when it's available.
You can see a list of hosts that do not freeze by
I've started a hackmd doc to track this:
https://hackmd.io/DB-c7z5sQqGHx2me9PWsVg
kevin
signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to
Planned Outage - Sever updates/reboots - 2023-08-16 21:00 UTC
There will be an outage starting at 2023-08-16 21:00 UTC,
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2023-08-16
I'm happy to announce that We have approved a new member in our
sysadmin-main group:
adamwill - Adam Williamson
This is the core group of trusted folks that high level access to most
everything in fedora infrastructure.
Adam has been around for a long time and has setup and run Fedora's
OpenQA
On Fri, Aug 04, 2023 at 02:04:22PM +0200, Fabian Arrotin wrote:
> On 04/08/2023 08:49, Ryan Lerch wrote:
> > On Fri, Aug 4, 2023 at 4:41 PM Fabian Arrotin
> > wrote:
> > >
> > > On 04/08/2023 02:25, Ryan Lerch wrote:
> > > > I just would get a discussion started with the process of
> > > >
On Mon, Aug 07, 2023 at 01:43:09PM +0200, Michal Konecny wrote:
> How the FAS and Gitlab groups are synced? Do we need to have them named
> same?
It's via SAML2 and the groups _can_ be named anything, but we should
really use a convention.
Basically on the gitlab side you tell it:
this saml2
On Mon, Aug 07, 2023 at 07:13:13AM +0100, Igor Jagec wrote:
> On Sun, 6 Aug 2023, 19:33 Kevin Fenzi, wrote:
>
> > We just finished our flocktofedora conference, and ran a workshop there
> > on onboarding and mentoring. So, you're arriving at a great time to help
> > us wi
On Fri, Aug 04, 2023 at 01:29:17PM +, Seth wrote:
> Hi there,
>
> I'm Seth, an A level student in the UK, currently studying Computer Science,
> Business Studies and Biology.
>
> I've been using Linux for a good few years and Fedora has been the
> distribution I've stuck with the longest,
I'm happy to announce that We have approved a new member in our
sysadmin-main group:
darknao - Francois Andrieu
This is the core group of trusted folks that high level access to most
everything in fedora infrastructure.
Francois has done of ton of things around Fedora infrastructure. From
On Wed, Jul 19, 2023 at 02:31:57PM -0400, Patrick Creech wrote:
> Hi there! I popped into the meeting last week and said "Hi", but figured I
> should also send this out as well.
>
> IRC: pcreech
>
> Since my last introduction[0] the primary thing that has changed is that I
> moved into doing
This is now done and I think everything is working.
I am sure I missed some things, so do file tickets/let us know when you
see things that are broken. ;)
kevin
signature.asc
Description: PGP signature
___
infrastructure mailing list --
Hey folks. I keep putting it off, but I need to move it forward, so I am
proposing to move batcave01 to rhel9 tomorrow, starting at 21UTC.
My plan is roughly:
- sync data from batcave01 to batcave02
- at 21UTC take down services on batcave01
- sync data again
- take batcave01 down.
- rename
On Tue, Jul 11, 2023 at 08:42:31AM +0200, Aurelien Bompard wrote:
> So, something broke, I forgot that the bodhi user also publishes to the
> org.fedoraproject.{env}.pungi.
> I fixed that now but there were quite a few messages rejected during my
> night. It may be necessary to restart the
On Thu, Jul 06, 2023 at 02:18:04PM -, Kamil Aronowski wrote:
> Thanks for the reply, Kevin. It means a lot to me, as I no longer feel alone
> with this issue. I'll try the mock configuration later on, so I do not
> overcomplicate things right now - once a basic config works for me, I'll then
Thanks for driving this forward!
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
On Wed, Jul 05, 2023 at 11:29:27AM -, Kamil Aronowski wrote:
> Hello people. I need some help from the good folks who maintain the Fedora
> servers responsible for building a bootchain securely, i.e. GRUB2 or the
> kernel. For instance, the bkernel01.iad2.fedoraproject.org server.
Happy to
On Thu, Jun 29, 2023 at 05:02:50PM +0300, Yanko Kaneti wrote:
> Hello,
>
> Have a strange f38 i686 buildroot setup failure in koji
> https://koji.fedoraproject.org/koji/taskinfo?taskID=102741271
>
> ...
> DEBUG util.py:442: Error unpacking rpm package
> shadow-utils-2:4.13-6.fc38.i686
> DEBUG
On Fri, May 26, 2023 at 04:28:56PM +0200, seddik alaoui ismaili wrote:
> Hi folks,
>
> We decided to add cron to compress some merged logs. So I realize that we
> didn't have any Ansible role to do this.
> Currently we manage cron tasks separately in the component's role, and IMO
> it will be
Planned Outage - Server updates/reboots - 2023-05-17 21:00 UTC
There will be an outage starting at 2023-05-17 21:00 UTC
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2023-05-17
On Sat, May 13, 2023 at 10:11:36PM -, Reon Beon wrote:
> Nice.
yep. Many thanks to Neil and Michael for working on it.
Just waiting on the epel9 branch/build and we can look at upgrading.
kevin
signature.asc
Description: PGP signature
___
On Sun, May 07, 2023 at 08:31:37AM +, Mattia Verga wrote:
> I'm unsure if this is something desired or if it is better to open a
> formal ticket on [releng|infra].
>
> Looking in the compose directories of Koji I've noticed that there seem
> to be a lot of garbage leftover from old stuff:
>
On Wed, May 03, 2023 at 06:54:33PM -0600, Tim Flink wrote:
> We're looking to deploy an instance of ReportPortal [1] for displaying and
> analyzing the output of automated tests in Fedora.
>
> This aligns with the goals of Testing Farm and instead of having it hosted
> with the other Fedora
On Thu, Apr 27, 2023 at 08:25:48AM +1000, Ryan Lerch wrote:
>
> This is my top pick!
The one reason why I don't like this choice is that pagure.io was
supposed to be distribution agnostic. Just an open source forge.
Thats why you see 'fedora-infrastructure' and 'fedora-kickstarts' and
such as
On Wed, Apr 26, 2023 at 01:38:05PM +0200, Michal Konecny wrote:
> Regarding the #3, how do you find spam projects now? Could the script do the
> same?
I find them manually. Go to pagure.io, browse projects and sort by 'most
recent'. About 99% of the first 4-5 pages are clearly spam. They are
1 - 100 of 3203 matches
Mail list logo
