Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

2016-08-10 Thread Fedora Cloud Trac Tickets
#153: design, deploy and document Fedora OpenShift Playground (FOSP) -+--- Reporter: goern| Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords:

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

2016-08-10 Thread Fedora Cloud Trac Tickets
#153: design, deploy and document Fedora OpenShift Playground (FOSP) -+--- Reporter: goern| Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords:

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

2016-08-10 Thread Fedora Cloud Trac Tickets
#153: design, deploy and document Fedora OpenShift Playground (FOSP) -+--- Reporter: goern| Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords:

[cloud] #168: Put OpenShift Origin in Container with Fedora Base

2016-08-10 Thread Fedora Cloud Trac Tickets
#168: Put OpenShift Origin in Container with Fedora Base +- Reporter: scollier| Owner: Type: task| Status: new Priority: normal | Milestone: Future Component:

Fedora Cloud SIG Minutes - 8/10/2016

2016-08-10 Thread Scott Collier
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-10/fedora_cloud_wg.2016-08-10-17.00.html #fedora-meeting-1: fedora_cloud_wg Meeting started by scollier at 17:00:56 UTC (full logs). Meeting summary Roll Call (scollier, 17:01:02) Ticket

Re: [cloud] #151: Need owner to define basic container smoke testing requirements

2016-08-10 Thread Fedora Cloud Trac Tickets
#151: Need owner to define basic container smoke testing requirements -+-- Reporter: acarter | Owner: maxamillion Type: task | Status: closed Priority: normal | Milestone: Future Component: --- | Resolution: fixed

[cloud] #167: Decide a process about failed tests for Autocloud

2016-08-10 Thread Fedora Cloud Trac Tickets
#167: Decide a process about failed tests for Autocloud +- Reporter: kushal | Owner: Type: task| Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting

Re: [cloud] #160: Ship fedora-motd in F24 atomic image

2016-08-10 Thread Fedora Cloud Trac Tickets
#160: Ship fedora-motd in F24 atomic image --+--- Reporter: rtnpro| Owner: kushal Type: task | Status: assigned Priority: normal| Milestone: Future Component: Cloud Base Image |

Re: [cloud] #155: Decide on post-GA update cadence for various deliverables

2016-08-10 Thread Fedora Cloud Trac Tickets
#155: Decide on post-GA update cadence for various deliverables -+-- Reporter: maxamillion | Owner: jasonbrooks Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- |

Re: Fedora Atomic Host Two Week Release Announcement

2016-08-10 Thread Vasiliy Tolstov
2016-08-10 16:52 GMT+03:00 Dennis Gilmore : > change alt to download so https://download.fedoraproject.org/pub/alt/atomic/ > it will redirect you to a globally close mirror Thanks! -- Vasiliy Tolstov, e-mail: v.tols...@yoctocloud.net

Re: Fedora Atomic Host Two Week Release Announcement

2016-08-10 Thread Matt Micene
If I'm reading the autocloud results correctly, that failed on the VirtualBox provider but not the libvirt provider: https://apps.fedoraproject.org/autocloud/jobs/355/output#299 Is there a difference between the two box providers that isn't being taken into account for the existence of the user

Re: Fedora Atomic Host Two Week Release Announcement

2016-08-10 Thread Dennis Gilmore
On Wednesday, August 10, 2016 2:54:44 PM CDT Vasiliy Tolstov wrote: > Does https://alt.fedoraproject.org/pub/alt/atomic/ have mirror that > more close to Russia? change alt to download so https://download.fedoraproject.org/pub/alt/atomic/ it will redirect you to a globally close mirror Dennis >

Re: Fedora Atomic Host Two Week Release Announcement

2016-08-10 Thread Trishna Guha
On Wed, Aug 10, 2016 at 9:27 AM, Adam Miller wrote: > > Appears to be a bug, I'll get it fixed. > After reading the job details, this is exact error we can see [1]. For Vagrant Atomic image user journal is not getting logged to disk ever. That's why the error has