Just a quick heads up (I am not really here today/this week):
Last week the tpm module in autosign01 failed. robosignatory normally
binds to a tpm so if any keys/files were copied off to somewhere else,
they would be useless, because they require that exact machines tpm to
Thanks to Patrick from the iot team, things are back and working, but in
a degraded state. Basically currently robosign is requiring passphrases
be manually input by an admin on any restart (and then keeping that
information in the kernel keyring).
I'm out this week, Patrick is also out for a while, so I would urge us
to not make autosign mods right now. As soon as we are back, we can
evaluate if getting the tpm replaced is the way to go or other measues.
In Openstack we have long list of images, which can be deleted. Or likely deleted.
These are clearly old, and I will wipe it away on Monday unless somebody say otherwise:
Fedora Cloud Base 25
Fedora base 161216
F24 Cloud Base release
Fedora 24 Cloud base test day
Fedora 24 Atomic test day
F23 Alpha RC2.2
Raw F23 Alpha RC2 Base Image
F23 Alpha RC2 Base Image
Then there is a list of weird images. I will **not** delete them. If it is yours and you do not need them, please delete it:
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
Happy Friday everyone!
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 can give.
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:
*F31 Upgrades & Reinstallations*
Updated s390x buildvm’
Updated ppc9-01 to f31 and all guests to f31, added on bug about qemu in
f31 on ppc64le not being able to do pseries-4.1 guests (the default),
switched to pseries-4.0. https://bugzilla.redhat.com/show_bug.cgi?id=1769600
Re-installed buildvm-aarch64-01/02/03 and buildvm-armv7-01/02/03 with f31
and worked though issues with composes on them.
Rawhide Gating: <https://github.com/fedora-infra/bodhi/projects/3>
Bodhi 5.0 has been deployed for a week now and we are getting some feedback
on the new UI
We hope to incorporate some of this feedback in the 5.1 release
5.1 will include a fix needed by the CI pipeline
Ci pipeline on fedora-messaging
JMS plugin has been updated
That broke datagrepper: unix timestamp are in seconds, not milliseconds and
postgresql doesn’t like the year 51850
Fedora-messaging client on resultsdb had broke
Open ticket is for monitoring:
83x performance patch submitted as a pull request and is awaiting review.
Once the 83x patch is merged, we hope that it will be possible to make a
It is possible that it will still be too slow so our next idea for
improvement involves changing the API that nodes use to synchronize objects
with each other.
Blocking issue was fixed https://pagure.io/fedora-infrastructure/issue/8253
Bcotton confirmed the fix is now in place - thanks Ben!
No progress on kanban board last four weeks
Jlanda is still hitting permission error in communishift
Working on running local instance
Benson Muite is now working on OIDC authentication
By creating a PR on Github, we should be able to see the progress
New PR from sebwoj - Porting to Fedora messaging
Magazine article posted after getting bounced between commblog and magazine
a few times.
On track for December 1 modernpaste shutdown
GDPR and privacy centric conversations are ongoing with respect to
The team have been testing migrating away from Repospanner
Wrote a PoC migration script (taking care also of requests/tickets/forks
RCM confirmed that it works
Next step is testing on https://git.stg.centos.org and we hope to have an
ETA on a migration time soon
Scoping meetings are ongoing
Introduction of a dedicated team for community issues:
The CPE Team have created a dedicated team to work through a backlog of
issues that are affecting the community.
The team has a 6 week plan ahead of them this side of the New Year
Check out our Kanban board:
Our first priority task is to fix the bugzilla sync script
Got its own upstream project:
We will be working on these items secondary to other work we have but will
try to get some of these issues resolved soon!
EPEL 8 modularity:
Modules are building in stg koji
Tagging is working
Bodhi testing is blocked on
Nest steps are to test epel8 playground module composing
Comments? Suggestions? Feedback? Let Us Know!
Have a great weekend!
Community Platform Engineering Team
Red Hat EMEA
The packages app is running on Fedora 30, and its dependencies are not
available in Fedora 31+ as I understand it.
This means it has about 7 months before we need to do something about
it, or shut it off.
Do we know if it can run on RHEL 7?
I have just disabled the openshift-apps playbooks from running in the
master playbook run (see
The reason behind is that the openshift-apps playbook are written to
trigger a new build and a new deployment of the application at each run,
this means that every time the master.yml playbook is run we build a
version of the application and deploy it.
Since a few of our applications are using source-to-image to build the
container directly from git it means that a master.yml run can deploy new
code into production without the maintainer of that application being aware
I wanted to raise awareness of this problem and ask the following
Do we need to have the openshift-apps in the master.yml ? If yes how do we
prevent the run from deploying unwanted changes in production ?
The infrastructure team will be having its weekly meeting tomorrow,
2019-11-21 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
We will use it over the week before the meeting to gather status and
info and discussion items and so forth, then use it in the irc meeting
to transfer information to the meetbot logs.
### Meeting start stuff
#startmeeting Infrastructure (2019-11-14)
#chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny
### Determine who the next chair is
#topic Next chair
#info magic eight ball says:
2019-11-28 - holiday, NO MEETING!
2019-12-26 - NO MEETING
2020-01-02 - NO MEETING
2020-01-09 - ??
### Let new people say hello
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
### Status / Information / Trivia / Announcements
(We put things here we want others on the team to know, but don't need
(Please use ```#info (the thing - your name)```
#topic announcements and information
### Things we should discuss
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use ```#topic your discussion topic - your username)```
#info pingou is on call 2019-11-14->2019-11-21
#info kevin is on call 2019-11-21->2019-11-28
#info smooge is on call 2019-11-28->2019-12-05
## .oncalltakeeu .oncalltakeus
#info Summary of last week: (from current oncall )
#topic Monitoring discussion
#info Go over existing out items and fix
#topic Tickets discussion
#info Fedora CoreOS Team requests
#topic backlog discussion
#info go over our backlog and discuss and determine priority
#info topic: provision new aarch64 builders
#info topic: ansible: enable ansible-report as a hook
Go thru each ticket one by one
#topic Community Fires Team
### Put all topics for discussion under here
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
### Learn about some application or setup in infrastructure
(This section, each week we get 1 person to talk about an application
or setup that we have. Just going over what it is, how to contribute,
ideas for improvement, etc. Whoever would like to do this, just add
the i/nfo in this section. In the event we don't find someone to teach
about something, we skip this section and just move on to open floor.)
### Meeting end stuff
#topic Open Floor
Stephen J Smoogen.
You are kindly invited to the meeting:
Fedora Infrastructure on 2019-11-21 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.