Why do we have an older version number for today's atomic compose? compose?

2016-09-05 Thread Kushal Das
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: 5832e43bcf2054a46169442557d4348d38e280161955c4bcd83b19db6649a5df OSName: fedora-atomic GPGSignature: (unsign

[Fedocal] Reminder meeting : Fedora Cloud Workgroup

2016-09-05 Thread dusty
Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-09-07 from 17:00:00 to 18:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-05 Thread Kushal Das
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: > 5832e43bcf2054a46169442557d4348d38e280161955c4bcd83b19db6649a5df >

Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-05 Thread Dusty Mabe
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: >> 5832e43bcf2054a

Fedora 25 atomic images are stuck while booting

2016-09-05 Thread Kushal Das
Hi, We can not ssh into the latest Fedora 25 based atomic images. While booting one image in Openstack I got [1] as console output. [1] https://kushal.fedorapeople.org/f25_notbooting1.png Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org