Puppet Apt module has breaking change in 2.0.0

[jcarroll2007]

I believe that a new version of puppet has caused an error while provisioning.

==> default:    (at /usr/lib/ruby/vendor_ruby/puppet/parser/templatewrapper.rb:7
7:in `method_missing')
==> default: Error: Invalid parameter key_source on Apt::Source[datastax] at /va
grant/modules/oaeservice/manifests/cassandra/dsc.pp:12 on node dev
==> default: Error: Invalid parameter key_source on Apt::Source[datastax] at /va
grant/modules/oaeservice/manifests/cassandra/dsc.pp:12 on node dev

I commented out the lines that these parameters are set on, but this caused more errors. Any suggestions on how to work around this?

[davidoae]

These are required to setup apt to download and install cassandra related packages.
What version of puppet are you using? We use 3.2.2-1puppetlabs1.

[jcarroll2007]

Maybe I'm confused, but don't you use whatever the latest version of puppet? In your provisioning script, you install the latest version if 3+ is not already installed. I tried to target a specific version of puppet, but was unable to get that to work either.

[mrvisser]

It's likely it's the version of the apt puppet module that's problematic as opposed to puppet itself.

The breaking change you see was published early April and it's likely we just haven't provisioned a machine from scratch and used a permissioned apt repo in that long. FWIW, the latest version we have installed of the apt module in QA is 1.7.0.

@jcarroll2007 the vagrant provisioning probably needs a lot more TLC than it gets, as all active OAE contributors currently install the components individually. If you're running OSX then homebrew seems to have packages for all the dependencies and it might be a bit easier.

[jcarroll2007]

@mrvisser I figured as much. Unfortunately, I am confined to hosting on windows. :( Thanks for the info. I have temporarily stepped away from attempting to get the VM up and running. If I return, I will try to get it working.

Thanks!

[mrvisser]

@jcarroll2007 that is unfortunate! I hope you don't mind, I renamed the ticket to describe the eventual issue.

[mrvisser]

Assigned to @davidoae for fix

[davidoae]

The apt module has changed various bits.
These changes do not seem to be forwards or backwards compatible so we cannot just update the puppet manifests until we decide to update puppet (or specifically the apt module) and we cannot update puppet until the manifests are updated.
Many of our apt related manifests will need changing, it's not just key_source that'll be an issue.
I'll create a branch with the required changes that @jcarroll2007 should be able to use, tomorrow hopefully.

[davidoae]

Apologies for the delay. Although I have nearly completed the changes I then got distracted to other more pressing issues. Even if @jcarroll2007 no longer needs this urgently we'll need it as soon as we update puppet in production so I'll be back on this soon.