Project

General

Profile

Actions

Bug #22299

closed

compute node nvidia dependency conflict

Added by Peter Amstutz about 1 month ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Story points:
-

Description

packer-build-compute-image: #275

13:00:18     amazon-ebs: The following packages have unmet dependencies:
13:00:18     amazon-ebs:  nvidia-container-toolkit : Depends: libnvidia-container-tools (>= 1.17.0-1) but 1.16.2-1 is to be installed

Also it reports "success" incorrectly on jenkins.

Actions #1

Updated by Peter Amstutz about 1 month ago

  • Target version changed from Development 2024-11-06 sprint to Development 2024-11-20
Actions #2

Updated by Peter Amstutz about 1 month ago

  • Description updated (diff)
Actions #3

Updated by Peter Amstutz about 1 month ago

  • Description updated (diff)
Actions #4

Updated by Brett Smith about 1 month ago

  • Assigned To set to Brett Smith
Actions #5

Updated by Brett Smith about 1 month ago

Peter Amstutz wrote:

Also it reports "success" incorrectly on jenkins.

As best I can tell the compute node build job just always does that, I have always seen it report success through a variety of errors. Probably better to file a separate bug for it because I assume we're gonna fix the nvidia pin issue before we fix that.

Actions #6

Updated by Peter Amstutz about 1 month ago

  • Assigned To changed from Brett Smith to Peter Amstutz
  • Status changed from New to Resolved

So, this just needed a pin on nvidia-container-toolkit to match libnvidia-container.

Getting build.sh to error out correctly is just a matter of adding set -e -o pipefail.

Actions #7

Updated by Peter Amstutz about 1 month ago

  • Target version changed from Development 2024-11-20 to Development 2024-11-06 sprint
Actions

Also available in: Atom PDF