New Member
by Daren Hammer
Hello,
My name is Daren. I am a full time web applications developer and a
computer science student in my junior year. I have dabbled in python for
about 2 years now and really enjoy it. I am a new fedora OS user and was
looking for some ways that I could contribute.
--
Thanks,
Daren
4 years, 4 months
Problems using fedpkg
by J. Scheurich
Hi,
When trying
$ kinit mufti11(a)FEDORAPROJECT.ORG
Password for mufti11(a)FEDORAPROJECT.ORG:
$ fedpkg clone vcglib
Cloning into 'vcglib'...
No such repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
review request
https://bugzilla.redhat.com/show_bug.cgi?id=1677989
$
i had no success.
Is something wrong ?
so long
MUFTI
4 years, 4 months
autosign / robosignatory status
by Kevin Fenzi
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
be there.
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.
Thanks,
kevin
4 years, 4 months
[PATCH] robosignatory.toml.j2: bump FCOS artifacts signing key to f31
by Jonathan Lebon
From: Jonathan Lebon <jonathan(a)jlebon.com>
FCOS is now rebased to f31. Bump the signing key accordingly.
Signed-off-by: Jonathan Lebon <jonathan(a)jlebon.com>
---
roles/robosignatory/templates/robosignatory.toml.j2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/robosignatory/templates/robosignatory.toml.j2 b/roles/robosignatory/templates/robosignatory.toml.j2
index 8126648c9..520ec72ee 100644
--- a/roles/robosignatory/templates/robosignatory.toml.j2
+++ b/roles/robosignatory/templates/robosignatory.toml.j2
@@ -476,7 +476,7 @@ handlers = ["console"]
[consumer_config.coreos]
bucket = "fcos-builds"
- key = "{{ (env == 'production')|ternary('fedora-30', 'testkey') }}"
+ key = "{{ (env == 'production')|ternary('fedora-31', 'testkey') }}"
[consumer_config.coreos.aws]
access_key = "{{ fcos_builds_releng_aws_access_id }}"
--
2.23.0
4 years, 4 months
OpenStack images cleanup
by Miroslav Suchý
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-28-1.1.ppc64
Fedora-Cloud-Base-28-1.1.ppc64le
Fedora-Cloud-Base-28-1.1.x86_64
Fedora-Cloud-Base-Rawhide-20180423.n.0.x86_64
Fedora-Cloud-Base-28_Beta-1.3.x86_64
Fedora-Cloud-Base-28_Beta-1.1.ppc64le
Fedora-Cloud-Base-28_Beta-1.1.x86_64
Fedora-Cloud-Base-28-20180320.n.0.x86_64
Fedora-Cloud-Base-28-20180310.n.0.x86_64
Fedora-Cloud-Base-27-1.6.ppc64
taskotron-f26-20171114
Fedora-Cloud-Base-27-1.6.x86_64.qcow2
Fedora-Atomic-27-1.6.ppc64le.qcow2
taskotron-f26-20171107
Fedora-Atomic-27_Beta-1.5
Fedora-Cloud-Base-27_Beta-1.5
Fedora-Cloud-Base-27-20170910.n.0.x86_64
Fedora-Cloud-Base-26-1.4.x86_64
Fedora-Cloud-Base-26-20170625.n.0.x86_64.qcow2
Fedora-Atomic-26-20170623.n.0.x86_64.qcow2
Fedora-Cloud-Base-26_Beta-1.4.ppc64le
Fedora-Cloud-Base-26_Beta-1.4.x86_64
Fedora-Atomic-25-20170327.0.x86_64.qcow2
Fedora-Cloud-Base-26_Alpha-1.2.x86_64
Fedora-Cloud-Base-26_Alpha-1.1.x86_64
Fedora-Cloud-Base-Rawhide-20170315.n.0.x86_64
Fedora-Cloud-Base-26-20170308.n.0
Fedora-Atomic-25-20170228.0.x86_64.qcow2
Fedora-Cloud-Base-Rawhide-20170227.n.0.x86_64.qcow2
Fedora Cloud Base 25
Fedora-Atomic-25-20170209.2.x86_64.qcow2
Fedora-Atomic-25-20170210.0.x86_64.qcow2
Fedora-Atomic-25-20170114.0.x86_64.qcow2
Fedora-Atomic-25-20170124.1.x86_64.qcow2
Fedora base 161216
Fedora-Cloud-Base-25-1.2.ppc64le.qcow2
Fedora-Cloud-Base-25-1.2.ppc64.qcow2
Fedora-Cloud-Base-25-1.3.x86_64
Fedora-Cloud-Base-25-1.2
Fedora-Cloud-Base-25-1.1.x86_64
Fedora-Cloud-Base-25_Beta-1.2.ppc64le.qcow2
Fedora-Cloud-Base-24-1.2.ppc64le.qcow2
Fedora-Cloud-Base-24-20161106.0.i386.qcow2
Fedora-Cloud-Base-25_Beta-1.2.ppc64.qcow2
Fedora-Cloud-Base-24-1.2.ppc64.qcow2
Fedora-Atomic-24-20161025.0.x86_64.qcow2
Fedora-Atomic-25-20161023.n.0.x86_64.qcow2
Fedora-Cloud-Base-25-20161023.n.0.x86_64.qcow2
Fedora-Cloud-Base-25-20161012
Fedora-Cloud-Base-25_Beta-1.1.x86_64.qcow2
Fedora-Atomic-25-20161005
Fedora-25-20161002
Fedora-Atomic-25-20160928
Fedora-Atomic-25-20160927
F24 Cloud Base release
Fedora24Base
Fedora24Atomic
fed-cloud-24-ppc64le
Fedora-Cloud-Base-24-1.2.x86_64.qcow2
Fedora-Cloud-Base-24 (Final)
Fedora-Atomic-24-20160602
Fedora-Atomic-24-20160523.n.0.x86_64.qcow2
Fedora-Atomic-24-20160521
Fedora 24 Cloud base test day
Fedora 24 Atomic test day
Fedora-Cloud-Base-24_Alpha-7.x86_64.qcow2
Fedora-Cloud-Base-23-20160410.x86_64.qcow2
Fedora-Cloud-Atomic-23-20160409.x86_64.qcow2
Fedora-Cloud-Base-24_Alpha-7.x86_64.qcow2
Fedora-Cloud-Atomic-Vagrant-23-20160116.x86_64.vagrant-libvirt.box
Fedora-Cloud-Atomic-23-20160116.x86_64.qcow2
Fedora-Cloud-Base-23-20160116.i386.qcow2
Fedora-Cloud-Base-23-20160116.x86_64.qcow2
Fedora-Cloud-Atomic-23-20160128.x86_64.qcow2
Fedora-Cloud-Base-rawhide-20160116.x86_64.qcow2
Fedora-Cloud-Base-rawhide-20160107.x86_64.qcow2
Fedora-Cloud-Atomic-23-20151224.x86_64.qcow2
Fedora-Cloud-Base-23-20151030.x86_64
Fedora-Cloud-Base-23-20151030.i386.qcow2
Fedora-Cloud-Base-23-20151030.x86_64.qcow2
Fedora-Cloud-Base-23_Beta_RC1-20150915.x86_64.qcow2
Fedora-Cloud-Base-23_Beta_TC4-20150907.i386.qcow2
F23 Alpha RC2.2
Fedora-Cloud-Base-23_Alpha-20150806.2.x86_64
Fedora-Cloud-Base-23_Alpha-20150806.1.x86_64
Raw F23 Alpha RC2 Base Image
F23 Alpha RC2 Base Image
Fedora-Cloud-Base-23_Alpha-20150805.x86_64
Fedora-Cloud-Base-22-20150521.x86_64
Fedora-Cloud-Atomic-22-20150521.x86_64
Fedora-Cloud-Base-22-20150521.x86_64.qcow2
Fedora-Cloud-Base-22-20150521.i386.qcow2
Fedora-Cloud-Base-22_Beta-20150415.x86_64
Fedora-Cloud-Atomic-22_Beta-20150415.x86_64
Fedora-Cloud-Base-22_Alpha-20150305.x86_64
Fedora-Cloud-Atomic-22_Alpha-20150305.x86_64
Fedora-Cloud-Base-20141203-21.i386
Fedora-Cloud-Base-20141203-21.x86_64
Fedora-x86_64-20-20140407
Fedora-x86_64-20-20131211.1
Fedora-Cloud-Base-20141203-21
fedora-cloud-64-20-20140407
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:
kushal-networkd1
ubuntu
kevintest6
rawhide-09-8
tguha-atomic-24
RC13-raw
RC13-qcow
Ubuntu 14.04
kdtest
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
4 years, 4 months
CPE Weekly: 2019-11-22
by Aoife Moloney
Happy Friday everyone!
Welcome to the CPE team weekly project update mail!
Background:
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.
Note:
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:
*Fedora:*
*F31 Upgrades & Reinstallations*
Updated s390x buildvm’
Updated buildvmhost-s390x-01
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:
https://pagure.io/fedora-infrastructure/issue/8392
repoSpanner <https://github.com/repoSpanner/repoSpanner>
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
release/deployment.
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.
*Application Retirements*
Elections
Blocking issue was fixed https://pagure.io/fedora-infrastructure/issue/8253
Bcotton confirmed the fix is now in place - thanks Ben!
Fedocal
No progress on kanban board last four weeks
https://teams.fedoraproject.org/project/fedora-calendar/kanban
Jlanda is still hitting permission error in communishift
https://pagure.io/fedora-infrastructure/issue/8274
Working on running local instance
Nuancier
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
Pastebin
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
application handovers
*CentOS:*
The team have been testing migrating away from Repospanner
Wrote a PoC migration script (taking care also of requests/tickets/forks
repositories)
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
*CentOS Stream*
Scoping meetings are ongoing
*Misc*
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:
https://teams.fedoraproject.org/project/community-fire-team/kanban
Our first priority task is to fix the bugzilla sync script
Got its own upstream project:
https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/
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
https://github.com/fedora-infra/bodhi/issues/3779
Nest steps are to test epel8 playground module composing
Comments? Suggestions? Feedback? Let Us Know!
Have a great weekend!
Aoife
--
Aoife Moloney
Feature Driver
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
4 years, 4 months
OpenShift-apps playbooks in the master.yml playbook
by Clement Verna
Hey all,
I have just disabled the openshift-apps playbooks from running in the
master playbook run (see
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/master.y...
).
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
of it.
I wanted to raise awareness of this problem and ask the following
questions.
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 ?
Thanks
Clément
4 years, 4 months