Freeze Break Request: update mock to 2.4-1.fc32.1
by Kevin Fenzi
In rawhide (and soon f33) systemd sets up a link for resolv.conf file
since we are moving to enabling systemd-resolved by default. In mock
chroots this is a broken link because systemd isn't actually running
there and creating the file it points to.
This exposes a bug in mock (or python) where shutil.copy*() ignores the
broken symlink and then breaks composes.
There is a fix in mock-2.6.
Current builders are on mock 2.4.
I have a build of 2.4 with just the fix backported.
https://koji.fedoraproject.org/koji/taskinfo?taskID=51544202
I'd like to update all the builders to mock-2.4-1.fc32.1 with the fix.
This is needed to get rawhide and branched composes happy again.
+1s?
kevin
3 years, 7 months
Tags on pull-requests
by Pierre-Yves Chibon
Good Morning Everyone,
To make it easier to find out the important pull-requests during freeze, I have
added two tags to our ansible repo:
- freeze-break-request
- post-freeze
So if you want to flag a pull-request as FBR or open the PR but note that this
can wait for after the freeze feel free to use these tags.
Hoping this helps,
Pierre
3 years, 7 months
Questions about rdiff-backup
by Manu Hernandez
Hi!
I was reading this SOP:
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/rd...
Hope you don't mind if I ask a few questions about it:
1) Why rdiff-backup? There are other alternatives present both in the
Fedora *and* CentOS/RHEL default repos like Amanda or Bacula, and lots
more if you add the EPEL repo (rsnapshot, BackupPC, Borg...)
2) The current setup uses a few tools: cron, git, ansible and
rdiff-backup. Wouldn't be simpler to use a tool that just takes care of
everything by itself?
I'm not questioning this choice, I'm just curious about this tool. I
never used it, so I'm trying to follow the reasoning of it being used to
backup the whole infrastructure.
Thank you in advance.
Best regards,
Manu
3 years, 7 months
CPE Quarterly Feedback Survey Results
by Ant Carroll
Hey folks,
I want to thank everyone that took the time to complete the survey for us.
Even more so for those of you that left comments to help give us extra info
and context, this is invaluable. The flip side is, it takes a little time
to work through and that's what we're doing right now.
A few pieces we can acknowledge off the bat though:
- Mediums of communication were overwhelmingly positive for weekly email
lists and blog posts. 76% for the emails and 46% for blog posts
respectively We're discussing how to improve these even further at the
moment as well as tweak the PO office hours and wind down the Taiga boards
as these were significantly less popular. 14% for the PO office hours and
1% for the Taiga boards.
- Transparency of decisions and communications. You want more of the former
and streamlining on the latter. We hear you and will aim to deliver this
alongside the first point above.
- Overall (82%+ reponses) you feel we did a good job since April of this
year. We appreciate the level of confidence you've shown in us and our
desire is to continuously improve this with your feedback.
Cheers,
Ant
--
Ant Carroll
Associate Manager, Software Engineering
Red Hat Waterford <http://www.redhat.com>
Communications House
Cork Road, Waterford City
ancarrol(a)redhat.com
M: +353876213163 IM: ancarrol
@redhatjobs <https://twitter.com/redhatjobs> redhatjobs
<https://www.facebook.com/redhatjobs> @redhatjobs
<https://instagram.com/redhatjobs>
<https://www.redhat.com/>
3 years, 7 months
Fedora Infra and Releng docs hackfest
by Mark O'Brien
Hey everyone,
Thanks to all who attended the docs hackfest last Friday.
For those who were unable to attend, here are the highlights.
Petr Bokoc graciously gave a demo on how we publish docs and supplied some
supporting
documentation on this hackmd https://hackmd.io/cVV89YDHRVGC0Zf-gdMlBQ
We are working on getting the video publicly available and I will send a
follow up email
with the link.
There was a good discussion on how we should present our docs going forward.
From this discussion it was decided to start moving documentation to the
repo
https://pagure.io/infra-docs-fpo. These dos will then end up on
https://docs.fedoraproject.org/
During the meeting we created the hierarchy index for the documentation and
some issues
https://pagure.io/infra-docs-fpo/issues These issues are very large tasks
so a feature branch
has been created for each one. These docs can be transferred over time.
These issues could be a good task for a new contributor as it would give
them a chance
to familiarize themselves with the documentation as they transfer it over.
Regards,
--
Mark O'Brien
Software Engineer
Community Platform Engineering
Red Hat
IRC: mobrien
3 years, 7 months
IPAM/DCIM for Fedora Infrastructure
by Pierre-Yves Chibon
ignatenkobrain wanted to share this with us as something potentially interesting
to look at.
He opened a ticket but agreed that an email thread would be better suited to
discuss this, so here it is and here below is Igor's original comment:
----
Hi folks,
This is not really request to do anything but rather heads-up from work I've
been doing in GoodData for some time. We've been searching for something that
helps us to have list of devices, their IPs and generally some kind of IP
management in one place. So we started to use netbox (I think it is originating
from DigitalOcean).
I've finally managed to package it https://src.fedoraproject.org/rpms/netbox in
Fedora. It supports LDAP and I guess can be somehow paired with Kerberos. I did
not check if it is possible to pair it with OIDC, but since it is Django should
be not very hard.
So in case you were looking for something like this - feel free to try it out
and let me know if you have any issues.
----
Original ticket: https://pagure.io/fedora-infrastructure/issue/9279
Pierre
3 years, 7 months
