Retroactive FBR : Increase packages host fedmsg backlog warning and
critical threshold
by Clement Verna
Hi,
The current threshold are a little bit low and we receive warning when
there are a lot of package updates. I have already pushed the commit
thinking that this was impacting only packages hosts which is not the
case :)
Looking for retroactive +1 ?
Thanks
Clément
diff --git a/roles/nagios_client/templates/check_fedmsg_consumers.cfg.j2
b/roles/nagios_client/templates/check_fedmsg_consumers.cfg.j2
index b64643f47..f64315820 100644
--- a/roles/nagios_client/templates/check_fedmsg_consumers.cfg.j2
+++ b/roles/nagios_client/templates/check_fedmsg_consumers.cfg.j2
@@ -54,7 +54,7 @@
command[check_fedmsg_cbacklog_hotness_backend]={{libdir}}/nagios/plugins/check_f
command[check_fedmsg_cbacklog_bodhi_backend01_hub]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub Masher 500 1000
command[check_fedmsg_cbacklog_bodhi_backend02_hub]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub UpdatesHandler 500 1000
command[check_fedmsg_cbacklog_autocloud_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub AutoCloudConsumer 100 500
-command[check_fedmsg_cbacklog_packages_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub CacheInvalidator 20000 30000
+command[check_fedmsg_cbacklog_packages_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub CacheInvalidator 30000 40000
command[check_fedmsg_cbacklog_bugyou_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub BugyouConsumer 5000 10000
command[check_fedmsg_cbacklog_pdc_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub PDCUpdater 10000 20000
command[check_fedmsg_cbacklog_mbs_backend]={{libdir}}/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub MBSConsumer 1000 2000
diff --git a/roles/nagios_server/files/nrpe/nrpe.cfg
b/roles/nagios_server/files/nrpe/nrpe.cfg
index 39235b777..2dc4df786 100644
--- a/roles/nagios_server/files/nrpe/nrpe.cfg
+++ b/roles/nagios_server/files/nrpe/nrpe.cfg
@@ -436,7 +436,7 @@
command[check_fedmsg_cbacklog_hotness_backend]=/usr/lib64/nagios/plugins/check_f
command[check_fedmsg_cbacklog_bodhi_backend01_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub Masher 500 1000
command[check_fedmsg_cbacklog_bodhi_backend02_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub UpdatesHandler 500 1000
command[check_fedmsg_cbacklog_autocloud_backend_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub AutoCloudConsumer 500 1000
-command[check_fedmsg_cbacklog_packages_backend_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub CacheInvalidator 5000 10000
+command[check_fedmsg_cbacklog_packages_backend_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub CacheInvalidator 30000 40000
command[check_fedmsg_cbacklog_bugyou_backend_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub BugyouConsumer 5000 10000
command[check_fedmsg_cbacklog_pdc_backend_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub PDCUpdater 10000 20000
command[check_fedmsg_cbacklog_mbs_backend_hub]=/usr/lib64/nagios/plugins/check_fedmsg_consumer_backlog.py
fedmsg-hub MBSConsumer 1000 2000
5 years, 8 months
FBR: Bodhi 3.5.0
by Randy Barlow
Greetings!
I would like to file a freeze break request to deploy Bodhi 3.5.0. The
infrastructure team was not notified of several changes to modular
packages until quite recently, and some of these changes required
patching to Bodhi which we were not able to complete before the freeze
began. The 3.5.0 release has these patches, and a few others as well.
You can read the changelog[0], or have a look at the diff from 3.4.0[1].
3.5.0 is deployed to staging and Patrick and I did testing on it tonight
and it is working well. I would like to deploy it tomorrow if I get the
required +1's.
In addition to deploying the release, I would like to also make the
attached changes in Ansible.
[0] https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html
[1] https://github.com/fedora-infra/bodhi/compare/3.4.0...3.5.0
5 years, 8 months
[PATCH] Exclude all Java packages from multilib
by Robert Marshall
By FESCo decision all Java packages are exempt from multilib.
See: https://pagure.io/fesco/issue/961
Signed-off-by: Robert Marshall <rmarshall(a)redhat.com>
---
roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index 769eb1853..2d27a9720 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -87,9 +87,7 @@ filter_packages = []
multilib_blacklist = {
'*': ['kernel*', 'kernel-PAE*', 'kernel*debug*',
'dmraid-devel', 'kdeutils-devel', 'mkinitrd-devel',
- 'java-1.5.0-gcj-devel', 'java-1.7.0-icedtea-devel',
- 'php-devel', 'java-1.6.0-openjdk-devel',
- 'java-1.7.0-openjdk-devel', 'java-1.8.0-openjdk-devel',
+ 'php-devel', 'java-*',
'httpd-devel', 'tomcat-native', 'php*', 'httpd',
'krb5-server', 'krb5-server-ldap', 'mod_*', 'ghc-*'
],
--
2.13.6
5 years, 8 months
FBR: Update module pungi conf with correct signing key
by Patrick マルタインアンドレアス Uiterwijk
For F28+ modular, the modules are signed by the keys of the underlying platform rather than the fedora-modular key.
+1s for this patch to set the correct key?
diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2
index 77eceb500..974c933f6 100644
--- a/roles/bodhi2/backend/templates/pungi.module.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.module.conf.j2
@@ -10,7 +10,9 @@ bootable = False
variants_file='module-variants.xml'
sigkeys = [
- 'a3cc4e62',
+[% if release.version_int == 28 %]
+ '9db62fb1',
+[% endif %]
{% if env == "staging" %}
None
{% endif %}
5 years, 8 months
FBR: Update pungi and install python3-modulemd and pdc-client on
bodhi-backend
by Patrick マルタインアンドレアス Uiterwijk
Hi,
Pungi 4.1.22 moved from py2 to py3 but is needed for modular update composes, so can I get +1s to update pungi and move the deps over to their py3 versions?
These deps are not deps of the main package because they're only needed when running module updates.
I think the biggest chance of issues would be the pungi upgrade, but we'll need to do that anyway, and is easy to revert.
Patrick
diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml
index b9cd9673d..ff87331e8 100644
--- a/roles/bodhi2/backend/tasks/main.yml
+++ b/roles/bodhi2/backend/tasks/main.yml
@@ -28,8 +28,8 @@
- pungi
- pungi-utils
- python2-koji-cli-plugins
- - python2-pdc-client
- - python2-modulemd
+ - python3-pdc-client
+ - python3-modulemd
tags:
- packages
- bodhi
5 years, 8 months
FBR: Update new-updates-sync for f28(m) updates-testing
by Patrick Uiterwijk
Hi all,
Can I get +1s to fix up new-updates-sync to fix syncing f28 to the correct
directory, and f28m (modular) as well?
Patrick
diff --git a/roles/bodhi2/backend/files/new-updates-sync
b/roles/bodhi2/backend/files/new-updates-sync
index 9ca341d79..734e6faa5 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -22,22 +22,7 @@ ATOMICDEST = '/mnt/koji/atomic/repo/'
RELEASES = {'f28': {'topic': 'fedora',
'version': '28',
'modules': ['fedora', 'fedora-secondary'],
- 'repos': {'updates': {
- 'from': 'f28-updates',
- 'ostrees': [{'ref':
'fedora/28/%(arch)s/updates/atomic-host',
- 'dest': ATOMICDEST,
- 'arches': ['x86_64', 'ppc64le',
'aarch64']},
- {'ref':
'fedora/28/x86_64/updates/workstation',
- 'dest': ATOMICDEST},
- # Hack around for the fact that ostree
on f25 doesn't know links
- {'ref': 'fedora/28/x86_64/workstation',
- 'dest': ATOMICDEST}],
- 'to': [{'arches': ['aarch64', 'x86_64', 'armhfp',
'source'],
- 'dest': os.path.join(FEDORADEST, '28')},
- {'arches': ['i386', 'ppc64', 'ppc64le',
's390x'],
- 'dest': os.path.join(FEDORAALTDEST, '28')}
- ]},
- 'updates-testing': {
+ 'repos': {'updates-testing': {
'from': 'f28-updates-testing',
'ostrees': [{'ref':
'fedora/28/%(arch)s/testing/atomic-host',
'dest': ATOMICDEST,
@@ -45,9 +30,21 @@ RELEASES = {'f28': {'topic': 'fedora',
{'ref':
'fedora/28/x86_64/testing/workstation',
'dest': ATOMICDEST}],
'to': [{'arches': ['x86_64', 'armhfp', 'source'],
- 'dest': os.path.join(FEDORADEST,
'testing', '28')},
+ 'dest': os.path.join(FEDORADEST,
'testing', '28', 'Everything')},
+ {'arches': ['aarch64', 'i386', 'ppc64',
'ppc64le', 's390x'],
+ 'dest': os.path.join(FEDORAALTDEST,
'testing', '28', 'Everything')}
+ ]}}
+ },
+ 'f28m': {'topic': 'fedora',
+ 'version': '28m',
+ 'modules': ['fedora', 'fedora-secondary'],
+ 'repos': {'updates-testing': {
+ 'from': 'f28m-updates-testing',
+ 'ostrees': [],
+ 'to': [{'arches': ['x86_64', 'armhfp', 'source'],
+ 'dest': os.path.join(FEDORADEST,
'testing', '28', 'Modular')},
{'arches': ['aarch64', 'i386', 'ppc64',
'ppc64le', 's390x'],
- 'dest': os.path.join(FEDORAALTDEST,
'testing', '28')}
+ 'dest': os.path.join(FEDORAALTDEST,
'testing', '28', 'Modular')}
]}}
},
'f27': {'topic': 'fedora',
5 years, 8 months
Fedora 28 Beta Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 28 Beta
release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 28 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2018-03-27 (or later if Beta
slips). Frozen hosts should have no changes made to them without a
sign-off on the change from at least 2 sysadmin-main or rel-eng members,
along with (in most cases) a patch of the exact change to be made to
this list.
Thanks,
kevin
5 years, 8 months
[PATCH] move to unified atomic ostree repo structure
by Dusty Mabe
We move to /compose/atomic/repo for the compose time repo and to
/atomic/repo for the production/user repo. See [1].
[1] https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject...
---
roles/bodhi2/backend/files/new-updates-sync | 30 ++++++++++++------------
roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++--
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync
index 6e7c8a072..548616a16 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -17,21 +17,21 @@ FEDORADEST = '/pub/fedora/linux/updates/'
FEDORAMODDEST = '/pub/fedora/linux/modular/updates/'
FEDORAALTDEST = '/pub/fedora-secondary/updates/'
EPELDEST = '/pub/epel/'
-ATOMICSOURCE = '/mnt/koji/compose/updates/atomic/'
-ATOMICDEST = '/mnt/koji/atomic/'
+ATOMICSOURCE = '/mnt/koji/compose/atomic/repo/'
+ATOMICDEST = '/mnt/koji/atomic/repo/'
RELEASES = {'f28': {'topic': 'fedora',
'version': '28',
'modules': ['fedora', 'fedora-secondary'],
'repos': {'updates': {
'from': 'f28-updates',
'ostrees': [{'ref': 'fedora/28/%(arch)s/updates/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '28'),
+ 'dest': ATOMICDEST,
'arches': ['x86_64', 'ppc64le', 'aarch64']},
{'ref': 'fedora/28/x86_64/updates/workstation',
- 'dest': os.path.join(ATOMICDEST, 'workstation')},
+ 'dest': ATOMICDEST},
# Hack around for the fact that ostree on f25 doesn't know links
{'ref': 'fedora/28/x86_64/workstation',
- 'dest': os.path.join(ATOMICDEST, 'workstation')}],
+ 'dest': ATOMICDEST}],
'to': [{'arches': ['aarch64', 'x86_64', 'armhfp', 'source'],
'dest': os.path.join(FEDORADEST, '28')},
{'arches': ['i386', 'ppc64', 'ppc64le', 's390x'],
@@ -40,10 +40,10 @@ RELEASES = {'f28': {'topic': 'fedora',
'updates-testing': {
'from': 'f28-updates-testing',
'ostrees': [{'ref': 'fedora/28/%(arch)s/testing/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '28'),
+ 'dest': ATOMICDEST,
'arches': ['x86_64', 'ppc64le', 'aarch64']},
{'ref': 'fedora/28/x86_64/testing/workstation',
- 'dest': os.path.join(ATOMICDEST, 'workstation')}],
+ 'dest': ATOMICDEST}],
'to': [{'arches': ['x86_64', 'armhfp', 'source'],
'dest': os.path.join(FEDORADEST, 'testing', '28')},
{'arches': ['aarch64', 'i386', 'ppc64', 'ppc64le', 's390x'],
@@ -56,13 +56,13 @@ RELEASES = {'f28': {'topic': 'fedora',
'repos': {'updates': {
'from': 'f27-updates',
'ostrees': [{'ref': 'fedora/27/%(arch)s/updates/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '27'),
+ 'dest': ATOMICDEST,
'arches': ['x86_64', 'ppc64le', 'aarch64']},
{'ref': 'fedora/27/x86_64/updates/workstation',
- 'dest': os.path.join(ATOMICDEST, 'workstation')},
+ 'dest': ATOMICDEST},
# Hack around for the fact that ostree on f25 doesn't know links
{'ref': 'fedora/27/x86_64/workstation',
- 'dest': os.path.join(ATOMICDEST, 'workstation')}],
+ 'dest': ATOMICDEST}],
'to': [{'arches': ['x86_64', 'armhfp', 'source'],
'dest': os.path.join(FEDORADEST, '27')},
{'arches': ['aarch64', 'i386', 'ppc64', 'ppc64le', 's390x'],
@@ -71,10 +71,10 @@ RELEASES = {'f28': {'topic': 'fedora',
'updates-testing': {
'from': 'f27-updates-testing',
'ostrees': [{'ref': 'fedora/27/%(arch)s/testing/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '27'),
+ 'dest': ATOMICDEST,
'arches': ['x86_64', 'ppc64le', 'aarch64']},
{'ref': 'fedora/27/x86_64/testing/workstation',
- 'dest': os.path.join(ATOMICDEST, 'workstation')}],
+ 'dest': ATOMICDEST}],
'to': [{'arches': ['x86_64', 'armhfp', 'source'],
'dest': os.path.join(FEDORADEST, 'testing', '27')},
{'arches': ['aarch64', 'i386', 'ppc64', 'ppc64le', 's390x'],
@@ -87,10 +87,10 @@ RELEASES = {'f28': {'topic': 'fedora',
'repos': {'updates': {
'from': 'f26-updates',
'ostrees': [{'ref': 'fedora/26/x86_64/updates/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '26')},
+ 'dest': ATOMICDEST},
# Hack around for the fact that ostree on f25 doesn't know links
{'ref': 'fedora/26/x86_64/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '26')}],
+ 'dest': ATOMICDEST}],
'to': [{'arches': ['x86_64', 'armhfp', 'source'],
'dest': os.path.join(FEDORADEST, '26')},
{'arches': ['aarch64', 'i386', 'ppc64', 'ppc64le'],
@@ -99,7 +99,7 @@ RELEASES = {'f28': {'topic': 'fedora',
'updates-testing': {
'from': 'f26-updates-testing',
'ostrees': [{'ref': 'fedora/26/x86_64/testing/atomic-host',
- 'dest': os.path.join(ATOMICDEST, '26')}],
+ 'dest': ATOMICDEST}],
'to': [{'arches': ['x86_64', 'armhfp', 'source'],
'dest': os.path.join(FEDORADEST, 'testing', '26')},
{'arches': ['aarch64', 'i386', 'ppc64', 'ppc64le'],
diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index 8040bb71b..0f1c8ecc0 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -126,7 +126,7 @@ ostree = {
[% endif %]
"https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/"
]
- "ostree_repo": "/mnt/koji/compose/updates/atomic",
+ "ostree_repo": "/mnt/koji/compose/atomic/repo",
"tag_ref": False,
"arches": ["x86_64",
[% if release.version_int >= 27 %]
@@ -154,7 +154,7 @@ ostree = {
[% endif %]
"https://kojipkgs{{ env_suffix }}.fedoraproject.org/compose/[[ release.version_int ]]/latest-Fedora-[[ release.version_int ]]/compose/Everything/$basearch/os/"
]
- "ostree_repo": "/mnt/koji/compose/updates/atomic",
+ "ostree_repo": "/mnt/koji/compose/atomic/repo",
"tag_ref": False,
"arches": ["x86_64"],
"failable": ["x86_64"]
--
2.14.3
5 years, 8 months
