Please review the changes:
https://pagure.io/fedora-kickstarts/pull-request/119
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
dustymabe added a new comment to an issue you are following:
``
Thanks for the heads up, and sorry for the double comments if it happens again!
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/186
___
dustymabe added a new comment to an issue you are following:
``
Thanks for the heads up, and sorry for the double comments if it happens again!
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/186
___
dustymabe added a new comment to an issue you are following:
``
> vgoyal
> This script will only set up the thin pool when you are using devicemapper
> right? So the script would only make a thin pool LV when running for dm and
> only make a regular LV when running for overlay. So one type of
dustymabe added a new comment to an issue you are following:
``
> vgoyal
> This script will only set up the thin pool when you are using devicemapper
> right? So the script would only make a thin pool LV when running for dm and
> only make a regular LV when running for overlay. So one type of
Adding fedora cloud list.
On 08/22/2016 10:13 AM, Colin Walters wrote:
> Hi, I'd like to propose a fairly fundamental rework of Atomic Host. TL;DR:
>
> - Move towards "system containers" (or layered packages) for flannel/etcd
> - Move towards containers (system, or Docker) for
On 08/18/2016 01:47 PM, Daniel J Walsh wrote:
>
>
> On 08/18/2016 12:00 PM, Dusty Mabe wrote:
>> We need to add mdadm to Fedora Atomic Host so that we can support software
>> raid disk setups.
>>
>> https://pagure.io/fedora-atomic/pull-request/8
>>
We are going to attempt to release the 20170228 images
that contain the fix for CVE-2017-6074. We'll try to
release today (2/28) unless we get any negative feedback.
Here is the new candidate:
The atomic images are here:
On 02/27/2017 09:41 PM, Adam Williamson wrote:
> On Mon, 2017-02-27 at 17:25 +, Fedora compose checker wrote:
>> Missing expected images:
>>
>> Atomic qcow2 x86_64
>
> There seems to be some sort of problem in pungi-make-ostree:
>
On 02/28/2017 08:56 AM, Colin Walters wrote:
> On Tue, Feb 28, 2017, at 01:37 AM, Dusty Mabe wrote:
>
>> The atomic images are here:
> ^ Host =)
>
>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170228.0/compose/C
On 03/01/2017 12:08 PM, Sayan Chowdhury wrote:
> On Tue, Feb 28, 2017 at 9:43 PM, Sayan Chowdhury
> wrote:
>> On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen
>> wrote:
>>> We are still working on this.
>>>
>>> On 27 February 2017 at
On 02/28/2017 08:11 PM, Josh Berkus wrote:
> On 02/28/2017 05:05 PM, Dusty Mabe wrote:
>>
>>
>> On 02/28/2017 07:33 PM, Josh Berkus wrote:
>>> Folks,
>>>
>>> Apparently Ansible-2.2.1 breaks OpenShift-Ansible. The only other
>>>
On 02/28/2017 07:33 PM, Josh Berkus wrote:
> Folks,
>
> Apparently Ansible-2.2.1 breaks OpenShift-Ansible. The only other
> version available, 2.1.2 is too old for Openshift-Ansible. And attempts
> to downgrade via pip result in dependency hell and fails.
Haven't tried with 2.2.1 yet. Been
On 03/01/2017 09:25 AM, nore...@fedoraproject.org wrote:
>
> A new Fedora Atomic Host update is available via an OSTree commit:
>
> Commit: ba95a4665776b58d342ad9cc36779f9b8fcf19c6606f8964a8ec1622cadc
> Version: 25.67
>
>
> Existing systems can be upgraded in place via e.g. `atomic host
The status of the issue: `Milestones, components need updating` of project:
`atomic-wg` has been updated to: Closed by dustymabe.
https://pagure.io/atomic-wg/issue/162
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an
dustymabe added a new comment to an issue you are following:
``
Leaving the cloud base image with the cloud sig for now:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/ITOEHIH2LJGUB6ZIOUYGOEX4T66JJKSX/#PEEAQVTK5TNDKFHXBRVMW7ZA5NKKYKT6
``
To reply, visit the
The status of the issue: `Working with the Server WG` of project: `atomic-wg`
has been updated to: Closed by dustymabe.
https://pagure.io/atomic-wg/issue/127
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
dustymabe added a new comment to an issue you are following:
``
closing this Dockerfiles ticket as we are now using the Fedora build system to
build containers and they are going through review.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/121
The status of the issue: `Migrate Dockerfiles to systemd, update for
Fedora:latest, clean up READMEs` of project: `atomic-wg` has been updated to:
Closed by dustymabe.
https://pagure.io/atomic-wg/issue/121
___
cloud mailing list --
dustymabe added a new comment to an issue you are following:
``
@maxamillion can you answer this?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/236
___
cloud mailing list --
The issue: `move ostree ref to be "container-host"` of project: `atomic-wg` has
been assigned to `dustymabe` by dustymabe.
https://pagure.io/atomic-wg/issue/198
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
The issue: `switch to overlay2` of project: `atomic-wg` has been assigned to
`dustymabe` by dustymabe.
https://pagure.io/atomic-wg/issue/186
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
On 08/23/2016 11:30 PM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found
On 09/05/2016 02:06 PM, Kushal Das wrote:
> On 05/09/16, Kushal Das wrote:
>> Hi,
>>
>> After an *atomic host upgrade* in an atomic host.
>>
>> Deployments:
>> ● fedora-atomic:fedora-atomic/24/x86_64/docker-host
>>Version: 24.35 (2016-09-05 01:23:02)
>> Commit:
>>
On 09/06/2016 10:27 AM, Micah Abbott wrote:
>
> It looks like the ostree composes had the version numbering reset on
> July 20.
>
> # ostree pull --commit-metadata-only --depth=-1
> fedora-atomic:fedora-atomic/24/x86_64/docker-host
>
> 68 metadata, 0 content objects fetched; 7 KiB
In the cloud meeting today I brought up overlayfs and F25. After
discussing with the engineers closer to the technology they recommend
waiting to move to overlayfs as the default in F26.
I think this will work well because it will give us some time to allow
people to "try" overlayfs in F25 (we
On 09/10/2016 12:47 PM, Chris Murphy wrote:
> On Fri, Sep 9, 2016 at 9:28 PM, Dusty Mabe <du...@dustymabe.com> wrote:
>>
>>
>> Should I open a bug for this? Can we get someone to look at it/work on it?
>
> Yes, and I think it needs a dmesg in case partprobe was
On 09/11/2016 12:22 AM, Dusty Mabe wrote:
>
>
> On 09/10/2016 12:47 PM, Chris Murphy wrote:
>> On Fri, Sep 9, 2016 at 9:28 PM, Dusty Mabe <du...@dustymabe.com> wrote:
>>>
>>>
>>> Should I open a bug for this? Can we get someone to look at it/wor
On 09/15/2016 04:25 AM, Kushal Das wrote:
> On 14/09/16, Adam Miller wrote:
>> On Wed, Sep 14, 2016 at 2:14 PM, Dusty Mabe <du...@dustymabe.com> wrote:
>>>
>>> In the cloud meeting today I brought up overlayfs and F25. After
>>> discussing w
From
https://kojipkgs.fedoraproject.org//work/tasks/5352/1352/Fedora-Cloud-Base-25-20160909.n.0.x86_64.qcow2
Sep 10 03:13:17 cloudhost.localdomain cloud-init[645]: 2016-09-10 03:13:17,078
- util.py[WARNING]: Failed: growpart /dev/sda 1
Sep 10 03:13:17 cloudhost.localdomain
Hey Jason,
Did you ever make any progress on planning a test day for us for this cycle?
Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
On 09/21/2016 03:38 PM, Vinny Valdez wrote:
>
> On Wed, Sep 21, 2016 at 2:05 PM, Sayan Chowdhury
> > wrote:
>
> * vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
>
We need to add mdadm to Fedora Atomic Host so that we can support software raid
disk setups.
https://pagure.io/fedora-atomic/pull-request/8
___
cloud mailing list
cloud@lists.fedoraproject.org
lease?)
Dusty
[1]
https://download.fedoraproject.org/pub/alt/atomic/stable/Atomic/x86_64/iso/Fedora-Atomic-dvd-x86_64-24-20160820.0.iso
>
>> On 08/23/2016 10:09 PM, Dusty Mabe wrote:
>>> The atomic ISO images are using the wrong tree. The images built on
>>> 8/23 [1
On 08/25/2016 12:05 PM, Dusty Mabe wrote:
>
>
> On 08/25/2016 04:07 AM, Peter Robinson wrote:
>>> Adding rel-eng. They might be able to help us out more on this topic.
>>
>> Could you maybe add a little bit more information? Like what tree is
>>
The atomic ISO images are using the wrong tree. The images built on
8/23 [1] yield the following system after an install:
-bash-4.3# rpm-ostree status
TIMESTAMP (UTC) VERSION ID OSNAMEREFSPEC
* 2016-06-15
Adding atomic-devel
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
> The atomic ISO images are using the wrong tree. The images built on
> 8/23 [1] yield the following system after an install:
>
> -bash-4.3# rpm-ostree status
> TIMESTAMP (UTC) VERSION ID
On 08/25/2016 06:43 PM, Adam Miller wrote:
> Hello all,
> I just wanted to throw out a note to everyone that I've gotten a chance
> to work on this[0] and pending some testing we should be good to go for next
> Two Week Atomic Release ... however, this is going to cause issues where the
>
On 08/24/2016 11:27 AM, Kushal Das wrote:
> Hi all,
>
> During Flock PRD discussion, a proposal was put up about changing the
> name of the WG to Atomic. We have few open questions from last week's
> meeting. I
> will try to put those down here, if anyone wants to add to that list, or
>
On 08/25/2016 02:51 PM, Jason Brooks wrote:
> On Thu, Aug 25, 2016 at 11:43 AM, Dusty Mabe <du...@dustymabe.com> wrote:
>>
>> Others have made some good comments in this thread. I'm really not as
>> concerned with these specific questions.
>>
>> I think
I just added new dates to the page. Can people sign up to host the meetings?
https://fedoraproject.org/wiki/Cloud#Upcoming_Meetings.2C_Agendas.2C_and_Chairs
If you are new, don't worry! We will all help you through it.
Dusty
___
cloud mailing list
summary:
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-24/fedora_cloud_wg.2016-08-24-17.07.html
full log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-24/fedora_cloud_wg.2016-08-24-17.07.log.html
==
#fedora-meeting-1: fedora cloud WG
Adding rel-eng. They might be able to help us out more on this topic.
Dusty
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
> The atomic ISO images are using the wrong tree. The images built on
> 8/23 [1] yield the following system after an install:
>
> -bash-4.3# rpm-ostree status
&
On 09/28/2016 02:56 PM, Jason Brooks wrote:
> That'd be fine, or would Fri be better?
Friday works too.
Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
On 09/28/2016 02:13 PM, Jason Brooks wrote:
> I was supposed to send out an ML msg about that but I haven't done it yet.
> How does Oct 11 sound?
>
> Jason
That week sounds good but I would suggest that Monday or Fridays tend
to be a little lighter on meetings than other days so we might get
On 09/21/2016 12:45 PM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found
On 10/03/2016 02:47 AM, Trishna Guha wrote:
> On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das wrote:
>> Hi all,
>>
>> The current F25 Atomic images are failing to boot[1], I never managed to
>> reach
>> dracut emergency shell in my local box.
>>
>> Can anyone else also please
On 10/03/2016 03:06 PM, Colin Walters wrote:
> On Mon, Oct 3, 2016, at 02:57 PM, Dusty Mabe wrote:
>
>> There is a kernel panic happening early in boot. Here is the serial
>> console log from one of those boots:
>
> https://bugzilla.redhat.com/show_bug.cgi?
On 10/03/2016 02:57 PM, Dusty Mabe wrote:
>
>
> On 10/03/2016 02:47 AM, Trishna Guha wrote:
>> On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das <m...@kushaldas.in> wrote:
>>> Hi all,
>>>
>>> The current F25 Atomic images are failing to boot[1], I
On 09/29/2016 06:03 PM, Adam Miller wrote:
> Hello all,
> I was recently discussing some items around docker layered image
> release process in the future with Randy (bowlofeggs) and Patrick
> (puiterwijk). As a side effect of our discussion there were two
> questions I wanted to ask of the
On 10/03/2016 01:45 PM, Jason Brooks wrote:
> On Thu, Sep 29, 2016 at 10:38 PM, wrote:
>> Hey Jason
>>
>> Did you guys file a ticket for the test day?
>> If not , here's is where you can [
>> https://fedorahosted.org/fedora-qa/report/11 ]
>>
>
> I'm going to file this
https://bodhi.fedoraproject.org/updates/FEDORA-2016-0ed0314ad7
We need karma on this package so we can get new docker-storage-setup to take
care of https://bugzilla.redhat.com/show_bug.cgi?id=1387934.
Dusty
___
cloud mailing list --
On thursday night the image builds didn't run because pagure was intermittently
down.
For the past 2 nights they have failed to build. I'm not sure why exactly but
there is
some libvirt error [1] in the logs.
Dennis has been looking into this for us.
I'm hoping we can an image built to look
On 11/08/2016 03:57 PM, Colin Walters wrote:
>
>
> On Tue, Nov 8, 2016, at 10:49 AM, Josh Berkus wrote:
>> Someone's written a tiny C implementation of gosu:
>>
>> https://github.com/ncopa/su-exec
>
> This is seems close to `runuser` from util-linux,
> which would just need to be taught an
Hey all,
In Fedora Atomic the release process is disjoint from the rest of
Fedora in that our images aren't produced as part of the normal
"production" composes and RCs.
I will make it a point to send out an email like this on the same day
that every RC is created in Fedora so that we can
dustymabe added a new comment to an issue you are following:
``
> The dark text on purple around "atomic cli" is a little tough to read.
Yeah, on this page: https://stg.getfedora.org/en/cloud/ - the Atomic CLI
section does not look good.
``
To reply, visit the link below or just reply to this
I believe we need to communicate a few things for F25:
1 - overlayfs - what it is, how to enable it in the various f25 images we
release
2 - containerized k8s - no longer in atomic host so we have to show people how
to use it
I am already planning to write the first blog post. Any volunteers
dustymabe added a new comment to an issue you are following:
``
> There's a kube 1.4.5 in koji for fc26
> (http://koji.fedoraproject.org/koji/buildinfo?buildID=816481), and I've asked
> Jan about making it available for fedora 25.
Can you keep us in the loop here on the progress of this one?
On 11/10/2016 05:09 AM, Jason Brooks wrote:
> I summed up the state of kube on f25 in this issue:
> https://pagure.io/atomic-wg/issue/176
Wow! That is an excellent, very detailed, issue.
Thanks Jason!
___
cloud mailing list --
On 11/09/2016 05:45 PM, Josh Berkus wrote:
> On 11/09/2016 09:43 AM, Dusty Mabe wrote:
>> I believe we need to communicate a few things for F25:
>>
>> 1 - overlayfs - what it is, how to enable it in the various f25 images we
>> release
>> 2 - containerized k8s
I reviewed the announcement and would like to suggest some changes:
https://gist.github.com/dustymabe/e308d1f549e4df55d3a902d271b4cf48/revisions?short_path=7002345#diff-700234571b092630ce68dcd5a3da6529
Also, the press release seems to still reference 24. Are we updating
that?
On 11/02/2016
On 11/10/2016 12:01 PM, Brian Proffitt wrote:
> Dusty:
>
> Added your changes. in them, you mentioned a "yum/rpm environment". Should
> that be "dnf/rpm"?
>
Yep! Thanks
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an
On 10/21/2016 04:02 PM, Colin Walters wrote:
>
>
> On Fri, Oct 21, 2016, at 03:42 PM, Jason Brooks wrote:
>
>>> Oct 21 18:40:37 localhost.localdomain systemd[1]:
>>> docker-storage-setup.service: Job docker-storage-setup.service/start
>>> deleted to break ordering cycle starting with
On 10/23/2016 06:55 PM, Dusty Mabe wrote:
>
>
> On 10/21/2016 04:02 PM, Colin Walters wrote:
>>
>>
>> On Fri, Oct 21, 2016, at 03:42 PM, Jason Brooks wrote:
>>
>>>> Oct 21 18:40:37 localhost.localdomain systemd[1]:
>>>> docker-stor
dustymabe added a new comment to an issue you are following:
``
Looks like the instance is shutting itself down:
https://paste.fedoraproject.org/460804/14774076
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/175
dustymabe added a new comment to an issue you are following:
``
actually I don't think it shut itself down now. looks like the gssproxy service
fails to come up and has to time out before other things can continue during
boot:
```
-bash-4.3# systemctl status gssproxy.service
●
I haven't had time to really investigate but figured I would pass this along:
qcow:
http://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161021.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-25-20161021.n.0.x86_64.qcow2
test results from last night's test run:
As part of the next release of Fedora 24 atomic host should we also
release the Fedora 24 base image so that the released version doesn't
have the latest huge kernel bug in it by default?
Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
On 10/24/2016 03:22 PM, Dusty Mabe wrote:
>
> As part of the next release of Fedora 24 atomic host should we also
> release the Fedora 24 base image so that the released version doesn't
> have the latest huge kernel bug in it by default?
It looks like the image builds we are doi
Hey WG,
I can't make the meeting today because of a conflict. Some updates:
- We have a working Atomic qcow so we are go for test day:
http://fedoraproject.org/wiki/Test_Day:2016_10_24_Cloud
- The tests for Autocloud for f25 failed last night due to
a typo. We believe that they really
dustymabe added a new comment to an issue you are following:
``
agreed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/177
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an
dustymabe added a new comment to an issue you are following:
``
I gave review and feedback in the original ticket that was opened for this:
https://fedorahosted.org/fedora-websites/ticket/406#comment:1
Please make any further comments/review there.
``
To reply, visit the link below or just
dustymabe added a new comment to an issue you are following:
``
@jberkus - can you explain what situation you were in when you hit this
problem? I'm not seeing it:
```
$ sudo docker run -it --rm fedora-docker-base-25-1.2.x86_64 bash
[root@0dcea1cb767e /]#
[root@0dcea1cb767e /]# cp
dustymabe added a new comment to an issue you are following:
``
This is an actual problem with the way the images are built right now. Can you
workaround this issue by adding a line like this to your Vagrantfile:
config.vm.synced_folder "/tmp", "/vagrant", disabled: 'true'
``
To reply, visit
dustymabe added a new comment to an issue you are following:
``
@walters. what exactly do you want to revert? We added the
[patch](http://pkgs.fedoraproject.org/cgit/rpms/cloud-init.git/commit/?id=b48cb59de23027b5b647baaf7d7dbe8eb52c95ad)
to cloud-init to make it so that networkmanager can read
dustymabe added a new comment to an issue you are following:
``
> One should be able to configure static IPs via nmcli in bootcmd hooks in
> cloud-init, so I'd like to back out the change to enable network.service.
hmm. I don't think we enabled network.service
```
-bash-4.3# systemctl status
dustymabe added a new comment to an issue you are following:
``
I would say update the wiki page, but whatever works.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/154
___
cloud mailing list --
dustymabe added a new comment to an issue you are following:
``
@jberkus - now we can propose new changes to the F25 page. please schedule some
time for interested parties to get together and go over your proposed changes.
``
To reply, visit the link below or just reply to this email
We currently don't have a download page for the Fedora 25 cloud base
image. This is because we did a poor job of communicating with the
websites team (our fault, not theirs) before Fedora 25 release.
There will be a new site for the cloud base image at
https://cloud.fedoraproject.org/
This is
On 11/22/2016 12:17 AM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found
dustymabe added a new comment to an issue you are following:
``
> What's the problem? It seems it cannot write to /
That is right. With Atomic only some directories are writable. The problem is
that the images used to get generated with the default sync to go to
`/home/vagrant/sync` and that
On 11/16/2016 11:49 AM, Dusty Mabe wrote:
>
>
> On 11/14/2016 04:02 PM, Dusty Mabe wrote:
>> Hi releng,
>>
>> It is a week before Fedora 25 will be released and the Atomic images
>> are still using the "nightly" composes. When can we expect the
>
dustymabe added a new comment to an issue you are following:
``
This is going to need to be reworked for F25. After next week let's sit down
and apply your sketch to the new pages.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/154
dustymabe added a new comment to an issue you are following:
``
mattdm and I are meeting with robyduck today to try to get a formal request in
for cloud.fp.o
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/158
dustymabe added a new comment to an issue you are following:
``
@jberkus ^^
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send
dustymabe added a new comment to an issue you are following:
``
as an alternative for now I have been working on getting the openshift-ansible
installer to work against F25 atomic host. I have opened up several issuses:
https://github.com/openshift/openshift-ansible/issues/2808
I think RC1.3 is what we are going with on Tuesday. Please take some time to
test out
the RC1.3 images so we can find/document any issues that we need to. You can
find them on this page:
https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.3_Cloud
Also, the EC2 images are:
dwalsh sent a message to the devel list about this. Follow along/respond here:
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/JBUEITVRLFHHOPQXSSFVYL5WQA3754ZZ/
___
cloud mailing list -- cloud@lists.fedoraproject.org
dustymabe added a new comment to an issue you are following:
``
so this is the same behavior as the F24 docker base image so I vote that we
don't make this change until after F25 release. - Also someone needs to step up
and "own" the issue and be responsible for making the change.
``
To
dustymabe added a new comment to an issue you are following:
``
@dwalsh - can you comment on this?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
___
cloud mailing list --
Looks like we have a candidate for release for F25 Atomic this week.
This is the Fedora-Atomic-25-20161120.0 production compose and all
links to ISOs and cloud images are below. The autocloud tests all
passed https://apps.fedoraproject.org/autocloud/jobs/491. Please
take some time and see if
Hi releng,
It is a week before Fedora 25 will be released and the Atomic images
are still using the "nightly" composes. When can we expect the
production composes that run daily (i.e. RC-20161114.0) to start
producing F25 images rather than F24 images?
We really need this so that we can test
We now have successful image builds! Please try them out!
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161101.n.0/compose/CloudImages/x86_64/images/
On 10/30/2016 09:17 AM, Dusty Mabe wrote:
>
> On thursday night the image builds didn't run because
On 10/30/2016 09:45 AM, Dusty Mabe wrote:
>
>
> On 10/30/2016 09:17 AM, Dusty Mabe wrote:
>>
>> On thursday night the image builds didn't run because pagure was
>> intermittently down.
>> For the past 2 nights they have failed to build. I'm not sure why
On 10/30/2016 09:17 AM, Dusty Mabe wrote:
>
> On thursday night the image builds didn't run because pagure was
> intermittently down.
> For the past 2 nights they have failed to build. I'm not sure why exactly but
> there is
> some libvirt error [1] in the logs.
>
>
On 11/02/2016 02:04 AM, Trishna Guha wrote:
> Hi all,
>
> There is Connection refused issue when I am trying to ssh to the current
> Fedora Atomic 24 Qcow2 image [1].
> Here is the connection refused failure for it on Autocloud [2].
>
> [1]
>
https://kojipkgs.fedoraproject.org//work/tasks/3677/16053677/Fedora-Cloud-Base-25-20161011.n.0.x86_64.qcow2
seen on local kvm as well as on openstack newton:
Cloud-init v. 0.7.7 running 'init' at Tue, 11 Oct 2016 21:45:39 +. Up 7.01 s
ci-info: +++Net device
The Vagrant Atlas page with the new atomic host:
https://atlas.hashicorp.com/fedora/boxes/
https://atlas.hashicorp.com/fedora/boxes/25-atomic-host/versions/20161207
vagrant init fedora/25-atomic-host; vagrant up
or, if you already have the box, to get the new one:
vagrant box update --box
dustymabe added a new comment to an issue you are following:
``
> Well, we shouldn't remove the prior ISO until the new one is populated. We
> had at least 24 hours with no ISO.
We actually don't "remove" the iso, but the link does get updated (which is
effectively removing it from the
dustymabe added a new comment to an issue you are following:
``
thanks @miabbott, I also just tried out the latest ISO and it works for me.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud
301 - 400 of 875 matches
Mail list logo