On 03/23/2018 08:56 AM, Ricky Elrod wrote:
> Our cert for whatcanidoforfedora.org expired.
>
> I've renewed the cert and deployed it. I had to run the proxy playbook
> with -t whatcanidoforfedora.org, which caused an httpd reload on
> proxies to see the new cert.
>
> Retroactive +1's please.
+1
On Fri, Mar 23, 2018 at 11:56:44AM -0400, Ricky Elrod wrote:
> Our cert for whatcanidoforfedora.org expired.
>
> I've renewed the cert and deployed it. I had to run the proxy playbook
> with -t whatcanidoforfedora.org, which caused an httpd reload on
> proxies to see the new cert.
>
> Retroactive
Our cert for whatcanidoforfedora.org expired.
I've renewed the cert and deployed it. I had to run the proxy playbook
with -t whatcanidoforfedora.org, which caused an httpd reload on
proxies to see the new cert.
Retroactive +1's please.
___
infrastructur
+1, thanks for this!
-re
On Mon, Mar 12, 2018 at 8:57 PM, Patrick Uiterwijk
wrote:
> Hi all,
>
> Due to the recently unembargoed openshift CVEs part of
> RHSA-2018:0475[1], one of which was marked Important, I have decided
> to update our production and staging os(.stg).fedoraproject.org
> clust
On 03/12/2018 05:57 PM, Patrick Uiterwijk wrote:
> Hi all,
>
> Due to the recently unembargoed openshift CVEs part of
> RHSA-2018:0475[1], one of which was marked Important, I have decided
> to update our production and staging os(.stg).fedoraproject.org
> clusters.
> This has caused exactly zero
Hi all,
Due to the recently unembargoed openshift CVEs part of
RHSA-2018:0475[1], one of which was marked Important, I have decided
to update our production and staging os(.stg).fedoraproject.org
clusters.
This has caused exactly zero seconds downtime to both the control
plane and any applications
> 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
>
+1 T
On Thu, Mar 08, 2018 at 09:06:07AM +0100, Clement Verna wrote:
> 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 :)
>
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_cli
aproject.org.
>
> I totally forgot about the freeze and updated the box and hence
> creating this retroactive FBR. Sorry about it and hope this will help
> in keeping track of what we did on the box.
+1
Dennis
signature.asc
Description: This is a digit
creating this
retroactive FBR. Sorry about it and hope this will help in keeping track of
what we did on the box.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le
On Fri, Sep 22, 2017 at 05:20:57PM -0500, Dennis Gilmore wrote:
> El vie, 22-09-2017 a las 17:38 -0400, Paul W. Frields escribió:
> > I want to apologize profusely -- I pushed a tiny change to the email
> > aliases and completely failed to consider they are covered by FBR
> > requirement.
> >
> >
El vie, 22-09-2017 a las 17:38 -0400, Paul W. Frields escribió:
> I want to apologize profusely -- I pushed a tiny change to the email
> aliases and completely failed to consider they are covered by FBR
> requirement.
>
> https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=
> fe76
On Fri, Sep 22, 2017 at 10:38 PM, Paul W. Frields wrote:
> I want to apologize profusely -- I pushed a tiny change to the email
> aliases and completely failed to consider they are covered by FBR
> requirement.
>
> https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=fe766d267f4e31
On Fri, Sep 22, 2017 at 11:38 PM, Paul W. Frields wrote:
> I want to apologize profusely -- I pushed a tiny change to the email
> aliases and completely failed to consider they are covered by FBR
> requirement.
>
> https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=fe766d267f4e31
I want to apologize profusely -- I pushed a tiny change to the email
aliases and completely failed to consider they are covered by FBR
requirement.
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=fe766d267f4e3149b2931573216de96db8406101
Kushal's no longer at Red Hat effective
+1 as we discussed. We should switch to rpm + patches as soon as we can
however and keep with that. :)
kevin
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe
/pull-request/2385.patch and
> applied it with "patch filter.py /root/2385.patch", and it can be
> reversed with the same command.
>
> I discussed this with Kevin on IRC, but for the record I'd still like
> to request retroactive FBR +1s.
> Anyone willing to give
it can be
reversed with the same command.
I discussed this with Kevin on IRC, but for the record I'd still like
to request retroactive FBR +1s.
Anyone willing to give me those? Thanks!
Patrick
___
infrastructure mailing list -- infrastructure@lists.fe
Hi!
>> While I was debugging settings not saving for Mailman, I found out
> >> that this was caused
> >> by the schema of the "template" table being incorrect.
> >>
> >> It had the following gem:
> >> password | timestamp without time zone
> >>
> >> I've just ran the following query to make it be
+1
On Wed, May 31, 2017 at 3:04 PM, Stephen John Smoogen wrote:
> +1
>
> On 31 May 2017 at 14:54, Patrick Uiterwijk wrote:
>> Hi,
>>
>> While I was debugging settings not saving for Mailman, I found out
>> that this was caused
>> by the schema of the "template" table being incorrect.
>>
>> It ha
+1
On 31 May 2017 at 14:54, Patrick Uiterwijk wrote:
> Hi,
>
> While I was debugging settings not saving for Mailman, I found out
> that this was caused
> by the schema of the "template" table being incorrect.
>
> It had the following gem:
> password | timestamp without time zone
>
> I've just ra
Hi,
While I was debugging settings not saving for Mailman, I found out
that this was caused
by the schema of the "template" table being incorrect.
It had the following gem:
password | timestamp without time zone
I've just ran the following query to make it be identical to what's in the code:
alt
23 matches
Mail list logo
