Ticket #163 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

debathena-auto-update should know about apt-release clusterinfo

Reported by: broder Owned by: geofft
Priority: blocker Milestone:
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

Soon, hopefully, machines in various Moira clusters around campus will have "production", "proposed", and/or "development" values for the "apt-release" key in clusterinfo.

debathena-auto-update should know about that key, and adjust /etc/apt/sources.list.d/debathena.list accordingly when it runs.

This allows us to configure cluster machines (and other workstations) to take updates from -proposed and -development without having to ever physically manipulate the machines.

Change History

comment:1 Changed 12 years ago by broder

  • Priority changed from major to critical

comment:2 Changed 12 years ago by geofft

  • Status changed from new to accepted
  • Owner set to geofft

Fixed in r23720, and uploaded to -proposed. There's a bit of a bootstrapping problem here but I'll test it anyway. :)

comment:3 Changed 12 years ago by geofft

  • Status changed from accepted to development

More likely actually fixed in r23786 and uploaded to -development, now with 90% fewer Debathena machines going crazy in their update procedure.

comment:4 Changed 12 years ago by geofft

  • Status changed from development to proposed

Tweaked a bit more in r23814 and moved to -proposed.

comment:5 Changed 12 years ago by geofft

  • Status changed from proposed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.