The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #15548

(puppetlabs-apt) Handling of apt update refreshonly setting.

Added by Craig Dunn about 3 years ago. Updated about 3 years ago.

Status:RejectedStart date:07/16/2012
Priority:HighDue date:
Assignee:-% Done:


Category:-Spent time:-
Target version:-
Keywords: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


The base class had an interesting way of trying to override the refresh only parameter of the exec for apt update…

if $always_apt_update == true {     
    Exec <| title=='apt_update' |> {
      refreshonly => false,

I’m pretty sure that has never worked – it caused it to fail many tests with;

 1) apt when specifying class parameters
     Failure/Error: it { should include_class("apt::params") }
       Puppet::Parser::Compiler failed with error ArgumentError: wrong number of arguments (1 for 0)

This patch makes all spec tests pass.


#1 Updated by Craig Dunn about 3 years ago

  • Status changed from In Topic Branch Pending Review to Rejected

This seems to be an issue with ruby 1.9.3 support rather than the module itself – it works in 1.8.7 so Im going to close this off and raise a separate ticket against Puppet core after some more testing

Also available in: Atom PDF