Hi all,
This email is to inform that there will be some delay in next Atomic Two
Week
Release. This is due to some issues with uploading Atomic AMIs. We are
working
on getting it fixed as soon as possible. Once we have AMIs back, we will do
next
Two week release.
Thanks,
Sinny
Hi everyone,
During our testing of the recent 4.10 kernel that went in to Fedora 25
Atomic Host we found that openshift networking stopped working because
of a regression in the kernel related to openvswitch and MTU settings.
This was fixed in the linux kernel upstream in commit 425df17c [1].
On Thu, Oct 6, 2016, at 02:23 PM, Matthew Miller wrote:
> On Thu, Oct 06, 2016 at 10:25:31AM -0700, Jason Brooks wrote:
> > > Is there a reason we can't pull in the selinux policy version
> > > that I fixed?
> > Is it in bodhi yet? I'd think it'd have to make it all the way through
> > to show
On Thu, Oct 06, 2016 at 10:25:31AM -0700, Jason Brooks wrote:
> > Is there a reason we can't pull in the selinux policy version
> > that I fixed?
> Is it in bodhi yet? I'd think it'd have to make it all the way through
> to show up in a release. It's going to take a lot of karma, too.
I think we
On Thu, Oct 6, 2016 at 10:19 AM, Colin Walters wrote:
>
>
> On Thu, Oct 6, 2016, at 09:21 AM, Adam Miller wrote:
>> Hello all,
>> I just wanted to post a quick update that there has not been a
>> compose that passed all AutoCloud testing criteria for release in the
>> past
On Thu, Oct 6, 2016, at 09:21 AM, Adam Miller wrote:
> Hello all,
> I just wanted to post a quick update that there has not been a
> compose that passed all AutoCloud testing criteria for release in the
> past two weeks. It appears that the Vagrant libvirt images are
> failing.
>
> We will
On Thu, Oct 6, 2016 at 6:21 AM, Adam Miller
wrote:
> Hello all,
> I just wanted to post a quick update that there has not been a
> compose that passed all AutoCloud testing criteria for release in the
> past two weeks. It appears that the Vagrant libvirt images
Hello all,
I just wanted to post a quick update that there has not been a
compose that passed all AutoCloud testing criteria for release in the
past two weeks. It appears that the Vagrant libvirt images are
failing.
We will try again for a release next Two Week window.
Thank you,
-AdamM
On 06/22/2016 08:23 PM, Dusty Mabe wrote:
>
>
> On 06/22/2016 06:46 PM, Josh Berkus wrote:
>>
Incidentally, is there an ISO I can pull anywhere? For my testing?
>>>
>>> Yes, sorry. I meant to include this in the original email.
>>>
>>> The new item is part of the new compose process which
>> Incidentally, is there an ISO I can pull anywhere? For my testing?
>
> Yes, sorry. I meant to include this in the original email.
>
> The new item is part of the new compose process which will reside here:
>
> https://kojipkgs.fedoraproject.org/compose/twoweek/
Hmm. I was hoping to be
On Tue, Jun 21, 2016 at 1:04 PM, Josh Berkus <jber...@redhat.com> wrote:
> On 06/21/2016 09:21 AM, Adam Miller wrote:
>> We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just
>> as the Fedora 24 GA Release was slipped and target next Tuesday
>> (201
On Tue, Jun 21, 2016 at 11:28 AM, Jason Brooks <jbro...@redhat.com> wrote:
> On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller
> <maxamill...@fedoraproject.org> wrote:
>> Hello all,
>> The original schedule for today's Fedora Two-Week Atomic Release
>> was goi
On Tue, Jun 21, 2016 at 11:21:42AM -0500, Adam Miller wrote:
> We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just
Or
> We can skip this Two-Week Atomic Release all together and target the
> next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
> We
On 06/21/2016 09:21 AM, Adam Miller wrote:
> We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just
> as the Fedora 24 GA Release was slipped and target next Tuesday
> (2016-06-21). This would "reset the clock" on the Two Week Releases
> and we will then h
On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Hello all,
> The original schedule for today's Fedora Two-Week Atomic Release
> was going to include a cut-over of our back end Release Infrastructure
> and AutoCloud automated QA environ
15 matches
Mail list logo