Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

linux-image-extra not available on AWS server #38

Closed
joshbrw opened this issue Nov 13, 2017 · 6 comments
Closed

linux-image-extra not available on AWS server #38

joshbrw opened this issue Nov 13, 2017 · 6 comments

Comments

@joshbrw
Copy link

joshbrw commented Nov 13, 2017

Error:

Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install linux-image-extra-4.4.0-1039-aws' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package linux-image-extra-4.4.0-1039-aws
E: Couldn't find any package by glob 'linux-image-extra-4.4.0-1039-aws'
E: Couldn't find any package by regex 'linux-image-extra-4.4.0-1039-aws'
Error: /Stage[main]/Docker::Install/Package[linux-image-extra-4.4.0-1039-aws]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install linux-image-extra-4.4.0-1039-aws' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package linux-image-extra-4.4.0-1039-aws
E: Couldn't find any package by glob 'linux-image-extra-4.4.0-1039-aws'
E: Couldn't find any package by regex 'linux-image-extra-4.4.0-1039-aws'

I've temporarily patched this by setting $manage_kernel => false, but seems to be an issue.
@davejrt davejrt added the bug label Nov 14, 2017
@davejrt
Copy link
Contributor

davejrt commented Dec 15, 2017

Apologies for the delay in getting back to you. We'll look into fixing the logic for this in an upcoming release.

@davideagle
Copy link

Any news on this bug, or a workaround other than $manage_kernel => false ?

@LongLiveCHIEF
Copy link
Contributor

LongLiveCHIEF commented Jan 6, 2018 •
edited
Loading

@davejrt @scotty-c do we even need the manage_kernel switch anymore? I believe at this point it's only needed for a combination of docker and operating system that I think this module would no longer even support.

@davejrt
Copy link
Contributor

davejrt commented Jan 6, 2018

There is a ticket in our backlog to remove anything that is no longer relevant to the operating system we no longer support after the fork. Someone will be looking into this sprint. Thanks for your patience, we've been a bit light on with engineers over the christmas/new year break.

@LongLiveCHIEF LongLiveCHIEF mentioned this issue Jan 6, 2018
Closed
@LongLiveCHIEF
Copy link
Contributor

LongLiveCHIEF commented Jan 6, 2018 •
edited
Loading

There is a ticket in our backlog to remove anything that is no longer relevant to the operating system we no longer support after the fork.

Assuming the supported operating systems shown in metadata.json is correct, then my PR #102 will take care of that.

nuclearsandwich added a commit to ros-infrastructure/buildfarm_deployment_config that referenced this issue Jan 12, 2018
@nuclearsandwich
Docker module does not need to install additional kernel packages.
8e94845 
Since the deployment of the new AWS-optimised kernel for Ubuntu in April
2017, buildfarm deployments on AWS will fail unless the operator first
reverts to the default virtual kernel.

The "manage_kernel" parameter is meant to install supplementary kernel
packages required by older combinations of docker and Ubuntu.
https://github.com/garethr/garethr-docker/blob/ccade80caf3be669241e733d6489828789cba5c1/manifests/install.pp#L65-L67

According to the official puppet-docker module, which was copied from
garethr/docker without commit history, this flag is no longer needed any
of their supported platforms [1] and is due to be removed.

Since Ubuntu Xenial is one of the platforms that this is no longer
needed on. Removing it to allow the use of the AWS-optimized kernel does
no harm.

[1]: puppetlabs/puppetlabs-docker#38
@nuclearsandwich nuclearsandwich mentioned this issue Jan 12, 2018
Merged
@davejrt
Copy link
Contributor

davejrt commented Jan 15, 2018

Fixed in PR #116

@davejrt davejrt closed this as completed Jan 15, 2018
nuclearsandwich added a commit to ros-infrastructure/buildfarm_deployment_config that referenced this issue Jan 18, 2018
@nuclearsandwich
Docker module does not need to install additional kernel packages. (#26)
8608312 
Since the deployment of the new AWS-optimised kernel for Ubuntu in April
2017, buildfarm deployments on AWS will fail unless the operator first
reverts to the default virtual kernel.

The "manage_kernel" parameter is meant to install supplementary kernel
packages required by older combinations of docker and Ubuntu.
https://github.com/garethr/garethr-docker/blob/ccade80caf3be669241e733d6489828789cba5c1/manifests/install.pp#L65-L67

According to the official puppet-docker module, which was copied from
garethr/docker without commit history, this flag is no longer needed any
of their supported platforms [1] and is due to be removed.

Since Ubuntu Xenial is one of the platforms that this is no longer
needed on. Removing it to allow the use of the AWS-optimized kernel does
no harm.

[1]: puppetlabs/puppetlabs-docker#38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@joshbrw @davejrt @davideagle @LongLiveCHIEF