Eric, I've not used the puppetlabs-release deb at all. my EC2 hosts have the puppetlabs repo added at bootstrap time, through cloud-init user-data. This is the entire config.
#cloud-config manage_etc_hosts: true hostname: <hostname> fqdn: <hostname>.example.com apt_sources: - source: "deb http://apt.puppetlabs.com $RELEASE main" keyid: 4BD6EC30 filename: puppetlabs.list apt_update: true apt_upgrade: true packages: - puppet puppet: conf: agent: server: "puppet.example.com" certname: "%i.<hostname>.eu-west-1" ...where <hostname> is set to the, well, desired hostname. This is enough to add the repo, install and configure Puppet and connect to our master, which then takes over. Puppet then configures the server, including taking over management of puppet.conf and puppetlabs.list. To resolve this upgrade issue, I've made two changes. I've modified the cloud-init script to correctly bootstrap new nodes: source: "deb http://apt.puppetlabs.com $RELEASE main dependencies" Also, I've fixed existing nodes by pushing a similar change through Puppet before attempting the upgrade to 3.2.1. Regards, Martijn Op donderdag 23 mei 2013 23:25:52 UTC+2 schreef Eric Sorenson het volgende: > > Quick question for those of you affected by this -- what did you to do to > add the puppetlabs apt repo? > > Did you do it through the method described here: > http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu > > .. or some other way? I'm trying to suss out whether the docs / packages > are messing people up. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
