Ticket #483 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

auto-update should deal with conffile conflicts on cluster

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

Description (last modified by jdreed) (diff)

Right now, if anything triggers a dpkg conffile conflict, auto-update will hang indefinitely. Not the best failure mode.

On cluster machines, since we are the sysadmin, we should be passing -o Dpkg::Options::=--force-confnew to aptitude.

Change History

comment:1 Changed 12 years ago by jdreed

  • Milestone set to Spring 2010

comment:2 follow-up: ↓ 3 Changed 11 years ago by jdreed

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

Now that mail to root occasionally goes somewhere useful, I say we implement this as described above (--force-confnew on cluster, --force-confold on workstation and whine at the user).

comment:3 in reply to: ↑ 2 Changed 11 years ago by andersk

Replying to jdreed:

as described above (--force-confnew on cluster, --force-confold on workstation and whine at the user).

That is not as described above. --force-confold is the Athena 9 behavior. The desired behavior as described is to make the update fail, which is different.

comment:4 Changed 11 years ago by jdreed

  • Description modified (diff)
  • Summary changed from auto-update should deal with conffile conflicts to auto-update should deal with conffile conflicts on cluster

comment:5 Changed 11 years ago by jdreed

  • Status changed from accepted to proposed

comment:6 Changed 11 years ago by broder

  • Status changed from proposed to closed
  • Resolution set to fixed

Moved to production.

Note: See TracTickets for help on using tickets.