Hi all,
Yesterday I released a new version of bodhi to production.
Please file any issues that you encounter here:
https://github.com/fedora-infra/bodhi/issues/new
Thanks,
luke
2.1.8
-
Pull Requests
- (@lmacken)#771, push: Only attempt to push unlocked updates
This upgrade has been deployed.
We'll be starting an updates push shortly to see what kind of
performance gain we've achieved.
Thanks!
luke
On Thu, Mar 24, 2016 at 12:25:36PM -0600, Stephen John Smoogen wrote:
> +1 from me
>
> On Mar 24, 2016 12:22, "Luke Macken" <lma
On Thu, Mar 24, 2016 at 07:32:42PM +0100, Pierre-Yves Chibon wrote:
> On Thu, Mar 24, 2016 at 12:22:04PM -0600, Luke Macken wrote:
> > Hi all,
> >
> > I'd like to push out a production bodhi upgrade, along with some ansible
> > changes that will change the permissio
Hi all,
I'd like to push out a production bodhi upgrade, along with some ansible
changes that will change the permissions of how the masher is run.
The latest bodhi code contains a number of fairly important bug fixes,
and a couple of minor enhancements:
Apologizes for the delay, but I finally got a chance to make an initial
pass at updating the Bodhi SOP to reflect the changes in 2.0::
https://infrastructure.fedoraproject.org/infra/docs/bodhi.rst
luke
signature.asc
Description: PGP signature
___
Hi folks,
I just pushed a new version of bodhi to production. This contains fixes for
some long-standing issues related to the handling of obsolete updates.
2.1.7
-
Pull Requests
- (@lmacken)#767, validators: Gracefully handle attempts to edit
updates that don't exist
Hi folks,
I just spun up a new bugfix release of bodhi and pushed it to production.
The last release contained a bug that caused a snowball effect and a number of
updates were ejected from the last couple of pushes. This issue should
hopefully be resolved.
2.1.5
-
Pull Requests
-
Hi folks,
I pushed a new version of Bodhi to production yesterday. This contains a few
small bug fixes, additional {submitted,modified,approved,pushed}_before query
parameters, as well as a masher enhancement to fix a tagging bug that can
happen when 2 builds for the same package get pushed at
On Wed, Dec 02, 2015 at 12:14:42PM +0100, Pierre-Yves Chibon wrote:
> Good morning everyone,
>
> I would like to start gathering our thoughts about python3 in our apps.
>
> To my knowledge, we currently have two applications that are python3 (only):
> - Mailman3 core (as in hyperkitty is still
Hi folks,
I just pushed out a new release of Bodhi to production. This contains a number
of bug fixes and user-facing enhancements that have piled up since the freeze.
If you recently had trouble editing an update to add a newer build, please give
it another shot. A number of people have hit
On Thu, Oct 22, 2015 at 03:14:47PM -0600, Stephen John Smoogen wrote:
> +1. Roll back should be just comment the lines out again, correct?
Correct.
luke
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
On Wed, Oct 21, 2015 at 10:34:50AM -0400, Ralph Bean wrote:
> This things warns about not being able to log and it emails pingou every half
> hour.
>
> Can I get two +1s to apply it?
Patch looks sane to me. +1
luke
signature.asc
Description: PGP signature
Hi all,
I just pushed a new version of bodhi to production. This release contains a
number of bug fixes, as well as a new cron jobs for expiring buildroot
overrides and commenting on updates after they reach the minimum amount of time
in testing. There is also a new "Masher status" page.
2.1.2
On Tue, Apr 07, 2015 at 11:24:01AM -0400, Ralph Bean wrote:
We need to cut a new release of the-new-hotness to deal with a change
in anitya's api. The 'Github' backend got renamed to the 'GitHub'.
(see the difference?).
The new release would include only these changes:
Pushed to stg+prod.
Thanks!
luke
On Mon, Mar 02, 2015 at 03:11:00PM -0500, Ralph Bean wrote:
On Mon, Mar 02, 2015 at 12:25:48PM -0700, Luke Macken wrote:
The F22 pre/post beta settings never made it to the bodhi frontend
config in ansible.
Attached is a patch that should fix
https
The F22 pre/post beta settings never made it to the bodhi frontend
config in ansible.
Attached is a patch that should fix https://fedorahosted.org/bodhi/ticket/772
Thanks,
luke
From 2318ccb429c0afe0996d332cfa8be75426b5222f Mon Sep 17 00:00:00 2001
From: Luke Macken lmac...@redhat.com
Date: Mon
Hi folks,
Just as heads up, I pushed out this patch to remove the WSGI
maximum-requests limit from the bodhi app servers. I'm hoping that this
will resolve some of the random 500 errors that people have been hitting
lately.
On Mon, Oct 20, 2014 at 01:33:58PM -0400, Ralph Bean wrote:
On Sat, Oct 18, 2014 at 07:17:15PM +0200, Pierre-Yves Chibon wrote:
The official dates are from Dec 4th to Dec 9th, as in, we start working on
the
4th and finish on the 8th, thus departure on the 9th, so arrival dates
should be
Hi all,
I wish to update the bodhi-server package on bodhi01/02 servers with the
latest package that I deployed to the releng machines weeks ago. All
it'll take is this command:
sudo -i ansible-playbook --extra-vars=target='bodhi' package='bodhi-server'
$(pwd)/update_packages.yml
At the moment
Hi all,
Due to a bug in a recent bodhi release, the EPEL masher is currently
unable to complete a push.
The bug is due to it hashing the i386 repodata, but polling x86_64 on
the master mirror. I will fix this properly in the next bodhi release,
but in the mean time we can easily work around the
Looks good to me, +1.
luke
On Thu, Sep 04, 2014 at 01:08:16PM -0700, Ralph Bean wrote:
I'm seeking two +1s to apply some work I did and tested in staging to
the production proxies.
The gist is that we currently proxy persistent tcp connections for the
fedmsg firehose through our proxies to
Hi,
I would like to push out another bodhi release today that contains a couple
more fixes for EPEL-7. This release will let us configure different arches for
specific releases (eg: no i386 for epel7).
I will only need to update releng04 and relepel01.
Bodhi patches:
I submitted a pull request to bodhi to get things working with the new
EPEL7 tagging schema. I'd like to spin up a new release and get it
deployed today to enable EPEL7 updates.
https://github.com/fedora-infra/bodhi/pull/87
There are plenty of places in the code that bodhi has to see if it's
On Fri, Aug 29, 2014 at 11:15:08AM -0600, Kevin Fenzi wrote:
On Fri, 29 Aug 2014 11:09:43 -0600
Luke Macken lmac...@redhat.com wrote:
I submitted a pull request to bodhi to get things working with the new
EPEL7 tagging schema. I'd like to spin up a new release and get it
deployed today
On Wed, Mar 26, 2014 at 08:37:09PM +0800, Christopher Meng wrote:
Hi,
Today when I submitted updates I met:
500 Internal error
The server encountered an unexpected condition which prevented it from
fulfilling the request.
I've tried about 50 times but failed still.
Can someone
On Fri, Dec 20, 2013 at 03:11:17PM +0100, Pierre-Yves Chibon wrote:
So, what I would like to ask is:
* what do you think of the project? Worth pursuing or not?
Love it. Totally worth pursuing :)
* Where should it live?
I'm all for keeping it distro-agnostic, but having a Powered by OpenShift
I'd like to update the bodhi masher on releng04 and relepel01 to
hopefully fix an annoying bug in the updateinfo.xml that causes a yum
warning.
https://bugzilla.redhat.com/show_bug.cgi?id=960642
The changes are isolated to the updateinfo metadata specific code, and
it is easy to revert if it
On Wed, Nov 06, 2013 at 02:04:06PM -0800, Toshio Kuratomi wrote:
On Wed, Nov 06, 2013 at 02:47:26PM -0700, Luke Macken wrote:
I'd like to update the bodhi masher on releng04 and relepel01 to
hopefully fix an annoying bug in the updateinfo.xml that causes a yum
warning.
https
There's a bug in the bodhi masher that is allowing for duplicate notices
to appear in the updateinfo.xml, which causes annoying yum warnings.
https://bugzilla.redhat.com/show_bug.cgi?id=960642
I wish to update the bodhi masher with a small change that may
potentially fix the issue, but also
On Tue, May 21, 2013 at 12:46:26PM +0200, Vít Ondruch wrote:
This [1] advisory was pushed into stable. Why Bodhi did not closed the
associated ticket in BZ [2]?
Thanks for pointing this out, Vít. I wrote some scripts[0] that were
supposed to clean up these stray bugs from the time we upgraded
On Thu, May 16, 2013 at 12:49:47PM -0400, Ralph Bean wrote:
On Thu, May 16, 2013 at 10:33:38AM -0600, Kevin Fenzi wrote:
Can we test this in stg first? Then if all goes well do it in prod?
+1 if we can do that to make sure there's no thinkos in the script,
etc.
(we should be able
We're currently hitting request timeouts when trying to push updates due
to recent python-fedora changes. I've prepared a simple hotfix to
increase the BodhiClient timeout to 300 seconds.
https://fedorahosted.org/fedora-infrastructure/ticket/3755
luke
On Wed, Apr 17, 2013 at 11:10:32AM -0600, Kevin Fenzi wrote:
On Wed, 17 Apr 2013 13:00:38 -0400
Luke Macken lmac...@redhat.com wrote:
We're currently hitting request timeouts when trying to push updates
due to recent python-fedora changes. I've prepared a simple hotfix to
increase
I setup Bodhi in staging to log to syslog instead of to stderr, which
ends up in /var/log/httpd/error_log.
The logs now appear in
/var/log/hosts/HOST/YEAR/MONTH/DAY/apps.log on log02, and in the
merged log /var/log/merged/apps.log.
In an effort to start building a Best Practices for Infra Apps,
The bodhi masher that runs our periodic jobs (releng04) never got updated to
handle the f18 pre/post beta updates policy. This means that even though bodhi
is properly enforcing the mandatory 3 days in testing, it's still sending
emails after 7 days. This is a very low-risk change that will
Python hash seed randomization is now enabled across all of our mod_wsgi
apps in production.
luke
On Mon, Jul 16, 2012 at 06:51:14PM -0400, Luke Macken wrote:
I just pushed out a hotfix to enable Python hash seed randomization on
all of our mod_wsgi applications in staging. The implementation
I just pushed out a hotfix to enable Python hash seed randomization on
all of our mod_wsgi applications in staging. The implementation details
of the change can be found in this ticket:
https://fedorahosted.org/fedora-infrastructure/ticket/3169
I am hopeful that this won't break anything,
On Tue, Jun 12, 2012 at 05:03:48PM -0600, Kevin Fenzi wrote:
* Setup a simple IDS of some kind?
- Notice non standard traffic in our internal nets
I'm definitely excited about getting an IDS deployed. I made an attempt
at it a few years ago with prelude+prewikka, but it wasn't able to
On Thu, Jan 19, 2012 at 03:25:02PM -0500, seth vidal wrote:
On Thu, 19 Jan 2012 15:11:41 -0500
seth vidal skvi...@fedoraproject.org wrote:
Summary from the meeting:
Today in the infrastructure meeting we started talking about how to
move the new packages and tagger apps into
During the meeting today, Seth asked me to write up details on the
interdependencies of the services that we're currently running on
community01.dev.
Indexer Cron Job
- Runs nightly, hits Koji, downloads RPMs using yum from the master
mirror.
- Creates a xapian
I would like to do a minor bugfix release for fedoracommunity, as soon
as possible. This release contains the following changes:
- Fixes to our bodhi/koji/pkgdb connectors to work with koji's new dist tag
scheme
- A couple more cvs-git link fixes
This update will fix a bunch of broken
Excerpts from Toshio Kuratomi's message of Tue Aug 23 12:42:01 -0400 2011:
On Tue, Aug 23, 2011 at 12:28:55PM -0400, Luke Macken wrote:
I would like to do a minor bugfix release for fedoracommunity, as soon
as possible. This release contains the following changes:
- Fixes to our
Excerpts from seth vidal's message of Wed Aug 17 15:53:42 -0400 2011:
On Wed, 2011-08-17 at 13:01 -0600, Stephen John Smoogen wrote:
4. Talk to something like github if we can meet up and grow something
togehter?
I agree with jesse that github, being closed source, is a complete
Excerpts from Stephen John Smoogen's message of Tue Jul 05 17:44:46 -0400 2011:
No not http://fedoracommunity.org but
https://admin.fedoraproject.org/community/ It has been in beta for 2
years now. What do we need to do to finish it (maybe make it
start.fedoraproject.org?) or put it aside for
Excerpts from Máirín Duffy's message of Wed Jul 06 18:06:13 -0400 2011:
On Wed, 2011-07-06 at 21:53 +, Luke Macken wrote:
Personally, I still use fedoracommunity on a regular basis, and find it
to be extremely useful in many ways. Right now we do not have any idea
as to how many people
Excerpts from seth vidal's message of Mon Jun 20 10:31:02 -0400 2011:
other ideas?
It would be interesting if we could extract Python tracebacks from our
mod_wsgi logs. For TG2, we've got WebError middleware, which can email
us tracebacks, but our TG1 apps have plenty of bugs that go unnoticed
Excerpts from Jayson Rowe's message of Wed Jun 15 13:10:19 -0400 2011:
Greetings!
I saw in the Fedora Weekly News today that there were issues with finding
folks to help maintain the Fedora Blogs. I'm a System and Network
Administrator for a software company by trade, and I would be more than
Hey all,
I'd like to push out a new bodhi release this week.
Policy Changes
- Support the new pre-beta policy
- critpath updates only requires 1 proventester karma
- non-critpath updates can be pushed to stable after 3 days in testing
Changes for AutoQA
- Adds
On Wed, Feb 23, 2011 at 05:55:48PM -0500, Ricky Zhou wrote:
Sounds like there's an rollback plan if things break (and I assume this
will be testing in staging first), +1
Of course :) I'll push it into staging tomorrow.
Thanks,
luke
___
I've been trying to get this new bodhi release out the door for a while
now. It fixes a lot of important bugs and adds a bunch of new features.
I've added many new unit tests for a lot of these fixes/features, i've
been poking it in staging for a while, and it does not contain any db
schema
On 08/03/2010 11:18 PM, Mike McGrath wrote:
On Tue, 3 Aug 2010, Luke Macken wrote:
Hey guys,
I want to perform a production bodhi upgrade.
Risks are fairly minimal. I've written unit tests for the new major
features,
and have been bashing on this code in staging all day today. I also
Hey guys,
I want to perform a production bodhi upgrade.
Risks are fairly minimal. I've written unit tests for the new major
features,
and have been bashing on this code in staging all day today. I also tested
`yum downgrade bodhi-server` in staging, which works fine. There are no
database
On Mon, 2010-06-21 at 21:31 -0600, Stephen John Smoogen wrote:
On Mon, Jun 21, 2010 at 12:18 AM, Ricky Elrod codebl...@elrod.me wrote:
Alright, how does this look? +1 worthy? :)
--- a/manifests/services/global.pp
+++ b/manifests/services/global.pp
@@ -171,6 +171,7 @@ class global {
On Wed, 2010-06-16 at 18:39 -0600, Stephen John Smoogen wrote:
Ok I think I have it Fedora Community working again on appXX.stg and
app01 [tested.] It looks like the version that is working on bapp01
requires various versions of applications not available in EPEL
anymore so I had to grab a
The future of Genshi is currently in question...
http://groups.google.com/group/turbogears-trunk/t/ec921035779324e9
We currently rely on the Genshi templating engine for:
* all static fedoraproject.org sites are compiled down to HTML from Genshi
* Elections
* FAS
* PackageDB
Forwarding mail from upstream TG developer, Florent Aide.
Luke,
I have read this:
http://lists.fedoraproject.org/pipermail/infrastructure/2010-April/008721.html
and that:
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/ec921035779324e9
And I won't reply on your ML
On Thu, Mar 25, 2010 at 01:43:46PM -0400, Luke Macken wrote:
The recent pkgdb update broke fedoracommunity. I have since applied a a
couple of simple, low-risk fixes to get things working again. I wish to
push the version in staging out into production.
https
On Thu, Mar 25, 2010 at 01:02:14PM -0500, Dennis Gilmore wrote:
On Thursday 25 March 2010 12:43:46 pm Luke Macken wrote:
The recent pkgdb update broke fedoracommunity. I have since applied a a
couple of simple, low-risk fixes to get things working again. I wish to
push the version
On Wed, Mar 03, 2010 at 03:15:34PM -0800, Jesse Keating wrote:
On Wed, 2010-03-03 at 17:55 -0500, Luke Macken wrote:
Hi all,
I'd like to push out a new bodhi release everywhere as soon as possible.
This release contains a bunch of critpath/no frozen rawhide fixes,
enhancements (like
On Tue, Feb 16, 2010 at 01:03:28PM -0500, Luke Macken wrote:
Hey guys,
I'd like to upgrade Fedora Community to the version that has been in
staging for the past couple of weeks. The only changes are the
addition of a new 'Statistics' section, containing wiki stats from Ian
Weller, Torrent
60 matches
Mail list logo
