From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Michael Santana <msantana@redhat.com>, dev <dev@dpdk.org>
Subject: Re: [NOTICE] 0-day Robot offline for upgrades
Date: Wed, 14 Sep 2022 10:42:37 -0400 [thread overview]
Message-ID: <f7tpmfykof6.fsf@redhat.com> (raw)
In-Reply-To: <CAJFAV8w6A9grgwzBfx2yPFFyQGG7_bDr-AhR_26MaZ7-a4sBAA@mail.gmail.com> (David Marchand's message of "Wed, 14 Sep 2022 10:05:42 +0200")
David Marchand <david.marchand@redhat.com> writes:
> Hey Aaron, Michael,
>
> On Fri, Sep 9, 2022 at 5:34 PM Aaron Conole <aconole@redhat.com> wrote:
>>
>> Greetings,
>>
>> This is to let you know that we are executing upgrades today for the open
>> 0-day robot that we run for OVS and DPDK projects. We don't expect that
>> the robot will be offline for a very long time, but just note that there
>> will be some down time as we bring the systems back online.
>>
>> Upgrade has already started, so don't be surprised if there are not jobs
>> reported today. We have backups ready to restore the systems in case of
>> fatal error. We plan to bring jobs online one by one to make sure that
>> we don't miss anything.
>>
>
> It looks like the maintenance is finished.
Yes, I think some final verification is still being done on the system
for some internal jobs, but I believe the 0-day robot jobs are back online.
> Can you confirm that there is no further action on this topic and we
> can expect normal operations?
I think this is true - Thanks!
> As usual, thanks!
prev parent reply other threads:[~2022-09-14 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:34 [NOTICE] 0-day Robot offline for upgrades Aaron Conole
2022-09-14 8:05 ` David Marchand
2022-09-14 14:42 ` Aaron Conole [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7tpmfykof6.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=msantana@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.