/flynn

EC2 builds fail with apt package resolution failure #1829

Closed
titanous opened this Issue Sep 5, 2015 · 5 comments

Comments

Assignees

@josephglanville josephglanville

Labels
component/util/release kind/bug
Projects
None yet
Milestone
No milestone
2 participants
@titanous @josephglanville
@titanous
Owner

titanous commented Sep 5, 2015

The EC2 VM builder is failing a lot with this error:

   amazon-ebs: Reading package lists...
   amazon-ebs: + [[ amazon-ebs == �\i   \u�\l�\o\x\-\o� ]]
   amazon-ebs: + apt-get install --install-recommends linux-generic-lts-vivid linux-image-generic-lts-vivid -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold
   amazon-ebs: Reading package lists...
   amazon-ebs: Building dependency tree...
   amazon-ebs: Reading state information...
   amazon-ebs: Some packages could not be installed. This may mean that you have
   amazon-ebs: requested an impossible situation or if you are using the unstable
   amazon-ebs: distribution that some required packages have not yet been created
   amazon-ebs: or been moved out of Incoming.
   amazon-ebs: The following information may help to resolve the situation:
   amazon-ebs:
   amazon-ebs: The following packages have unmet dependencies:
   amazon-ebs: linux-image-generic-lts-vivid : Depends: linux-image-extra-3.19.0-26-generic but it is not going to be installed
   amazon-ebs: Recommends: thermald but it is not installable
   amazon-ebs: E: Unable to correct problems

@titanous titanous added kind/bug component/util/release P1 labels Sep 5, 2015

@titanous titanous changed the title from EC2 builds with apt package resolution failure to EC2 builds fail with apt package resolution failure Sep 24, 2015

@titanous titanous assigned josephglanville Oct 4, 2015

@josephglanville josephglanville referenced this issue Oct 5, 2015

Merged

util/packer: Normalize apt sources across releases #1937

@josephglanville josephglanville closed this in #1937 Oct 6, 2015

@josephglanville
Member

josephglanville commented Oct 7, 2015

Looks like this is not completely solved sadly.

@josephglanville josephglanville reopened this Oct 7, 2015

@titanous
Owner

titanous commented Oct 10, 2015

This error showed up again in today's build log.
@titanous
Owner

titanous commented Oct 18, 2015

This issue occurred in the past two builds.
@josephglanville
Member

josephglanville commented Dec 16, 2015

Is this still happening? I haven't seen the release job fail with this error for some time.
@titanous
Owner

titanous commented Dec 16, 2015

We can close until we see it again.

@titanous titanous closed this Dec 16, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment