Testing of http://dl.fedoraproject.org/pub/alt/stage/21-20150309/Cloud-Images/x86_64/Images/

[Kushal Das]

Hi,

I tested the images locally following the cloud tests. They passed
successfully. But I failed to make them to boot on fed-cloud02.

Before uploading the images I converted them by the following command.

$ qemu-img amend -f qcow2 -o compat=0.10 Fedora-Cloud-Base-21-20150309.x86_64.qcow2

In case anyone want to test my convert images, they can be found at [1]
and [2].

[1] http://192.161.48.34/Fedora-Cloud-Base-21-20150309.x86_64.qcow2
[2] http://192.161.48.34/Fedora-Cloud-Atomic-21-20150309.x86_64.qcow2

Kushal

[Joe Brockmeier]

On 03/19/2015 06:22 AM, Kushal Das wrote:
> I tested the images locally following the cloud tests. They passed
> successfully. But I failed to make them to boot on fed-cloud02.

This is converting b/c images are actually qcow3 and OpenStack doesn't
love qcow3? (or v3 qcow2, if you prefer)

Best,

jzb

[Juerg Haefliger]

On Thu, Mar 19, 2015 at 1:56 PM, Joe Brockmeier  wrote:
> On 03/19/2015 06:22 AM, Kushal Das wrote:
> > I tested the images locally following the cloud tests. They passed
> > successfully. But I failed to make them to boot on fed-cloud02.
>
> This is converting b/c images are actually qcow3 and OpenStack doesn't
> love qcow3? (or v3 qcow2, if you prefer)

Depends on the version of the underlying qemu, OpenStack shouldn't
care. FWIW HP Public Cloud can't handle v3 yet.

...Juerg
> Best,
> jzb
>
> Joe Brockmeier | Project Atomic Doer of Things
> [e-mail] | http://community.redhat.com/
> Twitter: @jzb  | http://dissociatedpress.net/
>
> cloud mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Kushal Das]

On 19/03/15, Kushal Das wrote:
> Hi,
>
> I tested the images locally following the cloud tests. They passed
> successfully. But I failed to make them to boot on fed-cloud02.

As a side note, in the atomic image I am getting one service failed to
load in the first boot, can not see the error after a reboot.

UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
  ● var-lib-nfs-rpc_pipefs.mount loaded failed failed RPC Pipe File
  System

LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of
  SUB.
  SUB    = The low-level unit activation state, values depend on unit
  type.

Kushal