Welcome to the CPE team weekly project update mail!
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done. Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.
This document is currently built from individual reports rolled into a
google document which we edit and copy into a final document. We are
aware that this causes problems with some email readers, and are
working on a method to make this less problematic.
High Level Project Updates:
OSBS : aarch64 hosts ready for the deployment of an OpenShift cluster.
The Community Fire Team (CFT) is a team of people dedicated to fixing
bugs, annoyance and (small) RFE all around our applications. Their
work is tracked in taiga at:
they use #fedora-apps for discussion and coordination.
As usual, anyone is welcome to join the team, for a day, a task or more!
This week CFT has achieved the following work:
Release and deploy pagure 5.8.1
Changelog at: https://docs.pagure.org/pagure/changelog.html#id1
Release and deploy pagure-dist-git 1.5.2
Fixes enabling the pull-request only workflow on dist-git
Fix getting the CI pipeline results to show on PR on dist-git
Fix the script syncing the default assignee and CC list from dist-git
So far there were no negative feedback about the changes this script will do
Deploy the script syncing default assignee and CC list from dist-git
to bugzilla on openshift in staging
And is actively working on:
Enabling side-tag based updates in stable releases
Adding a new API endpoint to pagure to enable/disable git hooks
Adding tests for the fedora-messaging support in the JMS plugin (used
Making ansible-review work with the infrastructure's ansible repository
Fixing the mdapi integration on dist-git's package page
kojipkgs01/02 has been reinstalled
Robosign config for fcos has been updated
Team still welcomes any input and feedback on your experience with
Rawhide Gating to date as we move through our testing ahead of making
it generally available
Elections are ready to be moved to Communishift!
The move will be planned after the current elections are over.
Still no progress on kanban board last six weeks
Jlanda’s permission error in communishift should now be fixed
There may be still another permission error so the team are investigating
Still working on running local instance
Benson Muite is now working on OIDC authentication
A PR will be created on Github to test if we can see the progress
New PR from sebwoj - Porting to Fedora messaging is under review
Tests of cloud images moved to openqa
Retired vm’s and removed from ansible
Turning bare metal nodes into builders.
Fedora Docs Updates
Migrated this week (new pkg, new ansible-role):
Prepared to be migrated next week:
Kicked off : new ansible roles in progress for :
Bind to support dynamic delegated zone for acme dns-challenge
Mailman and postfix
We have our first compose gone to Red Hat Internal QA for testing
Other work still progressing on the builders
Koji production is upgraded to 1.19.1
Bodhi builds are now based on git
Changes added to Bodhi to add support for side-tags in stable releases
are pending reviews
Email with the Bugzilla-distgit sync script changes have been sent to
devel-announce for review
Link to mail
New changes to Pagure pending review:
New API endpoint to enable/disable git hooks
Ability to set dist-git in the default assignee overrides for bugzilla
Direct API interface
Button on the pagure package web interface
EPEL 8 modularity
Bodhi composes are stuck staging so this is causing a delay in testing
epel8 bodhi composes
epel8-playground-modules composes are failing right now in staging,
but the team are looking into it
Aarch64 is now racked and networked
New koji owner script was debugged
Koji client was updated
Koji was also patched for the --title option fix
Configured migrations from Ansible/Jinja template
Comments? Suggestions? Feedback? Let Us Know!
Have a great weekend!
Community Platform Engineering Team
Red Hat EMEA
On Fri, Dec 06, 2019 at 04:49:15PM +0000, Tom Hughes wrote:
> On 06/12/2019 16:41, Martin Kolman wrote:
> > On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote:
> > > I also installed the Fedora 31 GeoIP packages and ran the geoipupdate,
> > > and that DB has the correct info.
> > IIRC the infra team mentioned some issues with the new geoip database
> > being incompatible with how the service is currently implemented,
> > resulting in being stuck with an outdated database until this is resolved.
> Sounds like it maybe doesn't have support for GeoLite2 and is using the
> old MaxMind GeoLite Legacy databases which haven't been updated since
> the start of this year.
Yes, that is exactly the case.
We recently looked at this to see if we could retire the service, but it
looks like it's still needed, so we need to figure out how to get cycles
to update it.
If someone wants to work on this, let us know!
On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote:
> When installing Fedora 31 on a system, I noticed that anaconda defaulted
> to US/Pacific for the time zone, rather than the correct US/Central.
> I'm on a Google Fiber connection, and when I check Fedora's service at
> https://geoip.fedoraproject.org/city I get the info for their HQ in
> Mountain View. I'm pretty sure I got my proper location in the past.
> What geoIP service is Fedora using for this?
AFAIK the service is run as part of the Fedora infrastrucuture, due to
its potentially sensitive nature (every manual installation that has
network access will try to reach this API). It is not a third party provided
> When I check MaxMind's
> site, they give the correct info for both my IPv4 and IPv6 addresses
> (which BTW the Fedora geoIP lookup doesn't have a v6 address so only
> checks v4).
> I also installed the Fedora 31 GeoIP packages and ran the geoipupdate,
> and that DB has the correct info.
IIRC the infra team mentioned some issues with the new geoip database
being incompatible with how the service is currently implemented,
resulting in being stuck with an outdated database until this is resolved.
But I'm sure the people actually running this will know more, so CCing the Fedora infra list.
> Chris Adams <linux(a)cmadams.net>
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)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://firstname.lastname@example.org
On Mon, Apr 29, 2019 at 4:47 PM Kamil Paral <kparal(a)redhat.com> wrote:
> On Mon, Apr 29, 2019 at 11:39 AM Sinny Kumari <ksinny(a)gmail.com> wrote:
>> On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi <kevin(a)scrye.com> wrote:
>>> Or could we move f29+ all to whatever is replacing it? (taskotron?)
>> It will be nice but I am not aware of any other system in place which
>> replace checks performed by autocloud.
>> (CC'ed tflink and kparal)
>> Does taskotron provides capability to perform tests on Fedora cloud
>> Images like booting images and other basic checks?
> Theoretically it is possible using nested virt. However, Taskotron is
> going away as well. The replacement is Fedora CI:
Thanks kamil! yeah, it doesn't make sense to move to Taskotron if it is
going to be deprecated as well.
> I recommend to ask in the CI list:
> It should be possible for them to provide the infrastructure you need.
Hmm, I am not very sure if we should spend time investigating and setting
to autocloud unless we have usecases for long run. Fedora Atomic Host Two
Week releases ends with F29 EOL.
You are kindly invited to the meeting:
Fedora Infrastructure on 2019-12-05 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.