Bug #3349
aptitude provider claims to have upgraded package when it has not
| Status: | Investigating | Start date: | 03/06/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | package | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | aptitude | |||
Description
We recently switched to the aptitude provider and upgraded to 0.25.4; we noticed that some machines were continuously stating they were upgrading a package. When we investigated we found that aptitude was failing to find the specified version of the package, but puppet was not detecting this error, and was doing two things:
1) erroneously claiming to have upgraded the package to the specified version 2) sending a notification to subscribed resources
This seems like a pretty nasty issue.
History
#1
Updated by James Turnbull over 3 years ago
- Status changed from Unreviewed to Investigating
- Assignee set to Jesse Wolfe
#2
Updated by Paul Lathrop about 3 years ago
Note: I’m happy to provide a Debian host for testing if needed.
#3
Updated by Joshua Lifton over 1 year ago
- Assignee deleted (
Jesse Wolfe)
This issue was assigned to a former Puppet Labs employee. Adding back to the pool of unreviewed issues.