s2aio doesn't get success on aws

Bug #1686256 reported by Kota Tsuyuzaki on 2017-04-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Since the recent s2aio.sh chanes, it has not been able to setup the storlets environment on Amazon Web Service (AWS) environment.

I proceeded the tasks described at http://storlets.readthedocs.io/en/latest/getting_started.html

and then, get failed as:

TASK [docker_client : install necessary linux-image-extra] *************************************************************
fatal: []: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'linux-image-extra-4.4.0-1013-aws' is available"}
 to retry, use: --limit @/home/ubuntu/storlets/install/storlets/docker_cluster.retry

PLAY RECAP ************************************************************************************************************* : ok=5 changed=4 unreachable=0 failed=1

And also, it seems that the tasks are missing to install docker to the host.

Kota Tsuyuzaki (tsuyuzaki-kota) wrote :

it looks like a change at [1] from "linux-image-extra-{{ uname.stdout_lines[0] }}" to "linux-image-extra-virtual" works.

But I'm not sure it's a general solution because it seems linux-image-extra-virtual is for a virtual machine and s2aio.sh is for any linux environment, isn't it?

1: https://github.com/openstack/storlets/blob/master/install/storlets/roles/docker_client/tasks/main.yml#L39-L44

Kota Tsuyuzaki (tsuyuzaki-kota) wrote :

Er - linux-image-generic-lts-xenial seems prefer? I'll try it later.

Reviewed: https://review.openstack.org/459990
Committed: https://git.openstack.org/cgit/openstack/storlets/commit/?id=d0ceeb55ecf52f073fddbec359919800c2aa96e1
Submitter: Jenkins
Branch: master

commit d0ceeb55ecf52f073fddbec359919800c2aa96e1
Author: Kota Tsuyuzaki <email address hidden>
Date: Wed Apr 26 01:09:18 2017 -0700

    Fix apt fails due to linux image missing on AWS EC2

    `uname -r` doesn't show the kernel number with 'genric' suffix (it will
    be as 'aws' suffix) on AWS EC2 so that we may need a more general way to
    get the correct package name.

    Change-Id: Ieaa6891cb441124f13b5dc822f6511bc3091e188
    Closes-Bug: #1686256

Changed in storlets:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers