Closed Bug 1029334 Opened 11 years ago Closed 11 years ago

Unable to freshly puppetize a Ubuntu64 hardware host

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

Product:
Infrastructure & Operations
Component:
RelOps: Puppet
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Callek, Unassigned)

References

Details

So, in the puppetizing of talos-linux64-ix-003 today we got a failed to puppetize issue, pasted below. :rail, :dustin can one of you perhaps look into this? Mon Jun 23 21:44:41 -0700 2014 Puppet (err): Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install nvidia-310' returned 100: Reading package lists... Building dependency tree... Reading state information... Package nvidia-310 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-310' has no installation candidate Wrapped exception: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install nvidia-310' returned 100: Reading package lists... Building dependency tree... Reading state information... Package nvidia-310 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-310' has no installation candidate Mon Jun 23 21:44:41 -0700 2014 /Stage[main]/Packages::Nvidia_drivers/Package[nvidia-310]/ensure (err): change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install nvidia-310' returned 100: Reading package lists... Building dependency tree... Reading state information... Package nvidia-310 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-310' has no installation candidate Mon Jun 23 21:44:45 -0700 2014 Puppet (err): Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ubuntu-desktop' returned 100: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-desktop : Depends: xorg but it is not going to be installed E: Unable to correct problems, you have held broken packages. Wrapped exception: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ubuntu-desktop' returned 100: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-desktop : Depends: xorg but it is not going to be installed E: Unable to correct problems, you have held broken packages. Mon Jun 23 21:44:45 -0700 2014 /Stage[main]/Packages::Linux_desktop/Package[ubuntu-desktop]/ensure (err): change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ubuntu-desktop' returned 100: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-desktop : Depends: xorg but it is not going to be installed E: Unable to correct problems, you have held broken packages.
$ apt-cache policy nvidia-310 nvidia-310: Installed: (none) Candidate: (none) Version table: The closest version per "apt-ca search nvidia" is nvidia-331: $ apt-cache policy nvidia-331 nvidia-331: Installed: (none) Candidate: 331.79-0ubuntu0.0.1~xedgers12.04.1 Version table: 331.79-0ubuntu0.0.1~xedgers12.04.1 0 500 http://puppetagain-apt.pvt.build.mozilla.org/repos/apt/xorg-edgers/ precise/main amd64 Packages Sounds like the xorg-edgers repo has bumped the version...
The packages are still there, but apparently the --nodelete option to debmirror doesn't do what it says.
Probably the packages are not in the index files (Packages), this is why apt doesn't "see" them...
Exactly. I thought debmirror took care of this. I think this can be fixed by the apt-ftparchive command, but it shouldn't be required. I assume this is only blocking reimages, and thus not of crisis proportions for a while?
So the lesson to learn is that debmirror doesn't rebuild index files. The best fix would have been to only sync trusty last week, and left precise alone. The second best would have been to regenerate the indexes using apt-ftparchive (which basically just enumerates pool/ and builds Packages.gz). But, rail had a snapshot of the /data volume from April, so the best best fix was to just grab dists/precise from that snapshot and restore it. I just did that, and once it's distributed to the masters I'll re-check the apt-cache policy.
# apt-cache policy nvidia-310 nvidia-310: Installed: 310.32-0ubuntu1~xedgers~precise1 Candidate: 310.32-0ubuntu1~xedgers~precise1 Version table: *** 310.32-0ubuntu1~xedgers~precise1 0 100 /var/lib/dpkg/status
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
yay!
I *did* have to reimage the host this bug hit on in order to get past the puppet errors, was unsure if there was an easy way to recover from it, but with reimage the host is back able to puppetize, so this is verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.