How's life with 3.6.2?
98 views
Skip to first unread message
Christopher Wood
Jun 11, 2014, 4:40:18 PM6/11/14
to puppet...@googlegroups.com
I only notice three issues where "Affects Version: 3.6.2". Have any of you upgraded to 3.6.2 yet? If so, where did you upgrade from and how's life now?
https://tickets.puppetlabs.com/browse/PUP-2752?jql=affectedVersion%20%3D%20%223.6.2%22
(I'm probably doing this on our dev puppetmasters tomorrow, I will file tickets if there are any surprises.)
https://tickets.puppetlabs.com/browse/PUP-2752?jql=affectedVersion%20%3D%20%223.6.2%22
(I'm probably doing this on our dev puppetmasters tomorrow, I will file tickets if there are any surprises.)
Pete Brown
Jun 11, 2014, 8:36:14 PM6/11/14
to puppet-users
I decided to put puppet,hiera and facter versions into my base profile
so upgrades are tested in my dev environment and then pushed out to
production when I am happy.
3.6.2 is also a security release so I (and you very likely) want it
(and the relevant ssl fixes) pushed out asap.
I also just added a versioned ssl class to my profiles to make that even easier.
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140611204001.GA20741%40iniquitous.heresiarch.ca.
> For more options, visit https://groups.google.com/d/optout.
so upgrades are tested in my dev environment and then pushed out to
production when I am happy.
3.6.2 is also a security release so I (and you very likely) want it
(and the relevant ssl fixes) pushed out asap.
I also just added a versioned ssl class to my profiles to make that even easier.
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140611204001.GA20741%40iniquitous.heresiarch.ca.
> For more options, visit https://groups.google.com/d/optout.
Christopher Wood
Jun 12, 2014, 7:48:50 AM6/12/14
to puppet...@googlegroups.com
That's why I'm upgrading (otherwise 3.4.3 works for me), but I will have a hard time justifying any upgrade that leads to breakage. They're in profile::base for me too.
Well, on with my testing!
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAJ8DPF7PLa%2B3RNA8bO-E2aZcmhaMsTLZgZewE08sYAsJ7GQ8Fw%40mail.gmail.com.
Well, on with my testing!
Christopher Wood
Jun 12, 2014, 12:38:32 PM6/12/14
to puppet...@googlegroups.com
Verdict: Went fine with the usual upgrade teething troubles. (Once I figured those out I reverted to my pre-upgrade VM snapshot on the first upgraded host and there was no hassle the second time.) I went from 3.4.3 to 3.6.2.
The procedure was to upgrade the following rpms on each host (daemon restarts were included), reading logs as I went:
for i in mcollective-puppet-agent hiera facter puppet mcollective; do mco package $i update -F hostname=$SERVER; done
Upgrading mcollective this way meant the last mco package never returned since the daemon was restarted, I'm fine with that.
Then this for the puppetmasters to ensure the passenger-based puppetmasters were restarted:
mco service httpd restart -F hostname=$SERVER; done
These three issues, unfixed, would have been blockers for me doing an upgrade:
1) yumrepo mirrorlist vs baseurl (fixed in puppet 3.5.1)
https://tickets.puppetlabs.com/browse/PUP-2155 (dupe)
https://tickets.puppetlabs.com/browse/PUP-2150
I was using mirrorlist, it was past time to use baseurl anyway. I never saw an error since I was on 3.4.3.
Solution: use baseurl.
2) datacat module 0.4.2 incompatible with puppet >= 3.5 (fixed in datacat 0.5.0)
https://github.com/richardc/puppet-datacat/issues/12
I saw this sort of error on the puppetmaster:
Jun 12 09:48:15 puppetmaster1dev puppet-master[4552]: undefined method `module' for "production":String at /etc/puppet/environments/production/modules/datacat/manifests/init.pp:59 on node puppetmaster1dev.company.com
Solution: upgrade the datacat module to 0.5.0
3) mcollective service/package trouble with puppet 3.5 (fixed in mcollective-puppet-agent 1.7.1)
https://tickets.puppetlabs.com/browse/MCOP-23
I saw the following errors when checking package status after the initial aborted upgrade of mcollective only, not any mcollective plugins.
a) First, this after a plain upgrade (but without restarting the puppet agent):
$ mco package mcollective status -F hostname=puppetmaster1dev
* [ ==========================================================> ] 1 / 1
puppetmaster1dev.company.com: Could not autoload puppet/type/package: no 'environments' in {:root_environment=>#<Puppet::Node::Environment:0x7fc087f1d070 @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*", @config_version=nil>, :current_environment=>#<Puppet::Node::Environment:0x7fc087f1d070 @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*", @config_version=nil>} at top of [[0, nil, nil]]
Summary of Arch:
No aggregate summary could be computed
Summary of Ensure:
No aggregate summary could be computed
Finished processing 1 / 1 hosts in 46.00 ms
b) Second, after restarting both mcollective and puppet:
$ mco package mcollective status -F hostname=puppetmaster1dev
* [ ==========================================================> ] 1 / 1
puppetmaster1dev.company.com: undefined method `properties' for nil:NilClass
Summary of Arch:
No aggregate summary could be computed
Summary of Ensure:
No aggregate summary could be computed
Finished processing 1 / 1 hosts in 31.84 ms
Solution: upgrade mcollective-puppet-agent before upgrading/restarting mcollective and puppet
Editorially, this was very relaxing and I should have saved it for Friday afternoon.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140612114824.GB25610%40iniquitous.heresiarch.ca.
The procedure was to upgrade the following rpms on each host (daemon restarts were included), reading logs as I went:
for i in mcollective-puppet-agent hiera facter puppet mcollective; do mco package $i update -F hostname=$SERVER; done
Upgrading mcollective this way meant the last mco package never returned since the daemon was restarted, I'm fine with that.
Then this for the puppetmasters to ensure the passenger-based puppetmasters were restarted:
mco service httpd restart -F hostname=$SERVER; done
These three issues, unfixed, would have been blockers for me doing an upgrade:
1) yumrepo mirrorlist vs baseurl (fixed in puppet 3.5.1)
https://tickets.puppetlabs.com/browse/PUP-2155 (dupe)
https://tickets.puppetlabs.com/browse/PUP-2150
I was using mirrorlist, it was past time to use baseurl anyway. I never saw an error since I was on 3.4.3.
Solution: use baseurl.
2) datacat module 0.4.2 incompatible with puppet >= 3.5 (fixed in datacat 0.5.0)
https://github.com/richardc/puppet-datacat/issues/12
I saw this sort of error on the puppetmaster:
Jun 12 09:48:15 puppetmaster1dev puppet-master[4552]: undefined method `module' for "production":String at /etc/puppet/environments/production/modules/datacat/manifests/init.pp:59 on node puppetmaster1dev.company.com
Solution: upgrade the datacat module to 0.5.0
3) mcollective service/package trouble with puppet 3.5 (fixed in mcollective-puppet-agent 1.7.1)
https://tickets.puppetlabs.com/browse/MCOP-23
I saw the following errors when checking package status after the initial aborted upgrade of mcollective only, not any mcollective plugins.
a) First, this after a plain upgrade (but without restarting the puppet agent):
$ mco package mcollective status -F hostname=puppetmaster1dev
* [ ==========================================================> ] 1 / 1
puppetmaster1dev.company.com: Could not autoload puppet/type/package: no 'environments' in {:root_environment=>#<Puppet::Node::Environment:0x7fc087f1d070 @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*", @config_version=nil>, :current_environment=>#<Puppet::Node::Environment:0x7fc087f1d070 @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*", @config_version=nil>} at top of [[0, nil, nil]]
Summary of Arch:
No aggregate summary could be computed
Summary of Ensure:
No aggregate summary could be computed
Finished processing 1 / 1 hosts in 46.00 ms
b) Second, after restarting both mcollective and puppet:
$ mco package mcollective status -F hostname=puppetmaster1dev
* [ ==========================================================> ] 1 / 1
puppetmaster1dev.company.com: undefined method `properties' for nil:NilClass
Summary of Arch:
No aggregate summary could be computed
Summary of Ensure:
No aggregate summary could be computed
Finished processing 1 / 1 hosts in 31.84 ms
Solution: upgrade mcollective-puppet-agent before upgrading/restarting mcollective and puppet
Editorially, this was very relaxing and I should have saved it for Friday afternoon.
José Luis Ledesma
Jun 12, 2014, 3:51:03 PM6/12/14
to puppet...@googlegroups.com
Very nice report, we use mcollective so it will be very useful!
Have you found any performance issue? I'm worried about that because our current puppet master is currently a bit overloaded.
Thanks,
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140612163813.GA26648%40iniquitous.heresiarch.ca.
Christopher Wood
Jun 12, 2014, 4:20:46 PM6/12/14
to puppet...@googlegroups.com
No performance issues, but I'm running one CA and one non-CA puppetmaster behind a load balancer. My reflex action in case of load is to throw more servers in and then think about what's wrong.
I did see one of these for each new agent checkin, but things worked fine:
Jun 12 11:45:07 puppetmaster1dev puppet-master[10201]: Could not retrieve facts for puppetmaster2dev.company.com: Failed to find facts from PuppetDB at puppetdb1dev.company.com:8081: source did not contain any PSON!
On Thu, Jun 12, 2014 at 09:50:54PM +0200, José Luis Ledesma wrote:
> Very nice report, we use mcollective so it will be very useful!
>
> Have you found any performance issue? I'm worried about that because our
> current puppet master is currently a bit overloaded.
>
> Thanks,
>
> El 12/06/2014 18:38, "Christopher Wood" <[1]christop...@pobox.com>
> [3]https://tickets.puppetlabs.com/browse/PUP-2150
> > > > For more options, visit [13]https://groups.google.com/d/optout.
> > > For more options, visit [16]https://groups.google.com/d/optout.
> > For more options, visit [19]https://groups.google.com/d/optout.
> For more options, visit [22]https://groups.google.com/d/optout.
> For more options, visit [25]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:christop...@pobox.com
> 2. https://tickets.puppetlabs.com/browse/PUP-2155
> 3. https://tickets.puppetlabs.com/browse/PUP-2150
> 4. https://github.com/richardc/puppet-datacat/issues/12
> 5. http://puppetmaster1dev.company.com/
> 6. https://tickets.puppetlabs.com/browse/MCOP-23
> 7. http://puppetmaster1dev.company.com/
> 8. http://puppetmaster1dev.company.com/
> 9. mailto:christop...@pobox.com
> 10. https://tickets.puppetlabs.com/browse/PUP-2752?jql=affectedVersion%20%3D%20%223.6.2%22
> 11. mailto:puppet-users%2Bunsu...@googlegroups.com
> 12. https://groups.google.com/d/msgid/puppet-users/20140611204001.GA20741%40iniquitous.heresiarch.ca
> 13. https://groups.google.com/d/optout
> 14. mailto:puppet-users%2Bunsu...@googlegroups.com
> 15. https://groups.google.com/d/msgid/puppet-users/CAJ8DPF7PLa%2B3RNA8bO-E2aZcmhaMsTLZgZewE08sYAsJ7GQ8Fw%40mail.gmail.com
> 16. https://groups.google.com/d/optout
> 17. mailto:puppet-users%2Bunsu...@googlegroups.com
> 18. https://groups.google.com/d/msgid/puppet-users/20140612114824.GB25610%40iniquitous.heresiarch.ca
> 19. https://groups.google.com/d/optout
> 20. mailto:puppet-users%2Bunsu...@googlegroups.com
> 21. https://groups.google.com/d/msgid/puppet-users/20140612163813.GA26648%40iniquitous.heresiarch.ca
> 22. https://groups.google.com/d/optout
> 23. mailto:puppet-users...@googlegroups.com
> 24. https://groups.google.com/d/msgid/puppet-users/CAF_B3df4aUxOhNQbEonKm%2BdHmh%2BnmE1wPeHagy1-ve%2B3tgbG-w%40mail.gmail.com?utm_medium=email&utm_source=footer
> 25. https://groups.google.com/d/optout
I did see one of these for each new agent checkin, but things worked fine:
Jun 12 11:45:07 puppetmaster1dev puppet-master[10201]: Could not retrieve facts for puppetmaster2dev.company.com: Failed to find facts from PuppetDB at puppetdb1dev.company.com:8081: source did not contain any PSON!
On Thu, Jun 12, 2014 at 09:50:54PM +0200, José Luis Ledesma wrote:
> Very nice report, we use mcollective so it will be very useful!
>
> Have you found any performance issue? I'm worried about that because our
> current puppet master is currently a bit overloaded.
>
> Thanks,
>
> escribió:
>
> Verdict: Went fine with the usual upgrade teething troubles. (Once I
> figured those out I reverted to my pre-upgrade VM snapshot on the first
> upgraded host and there was no hassle the second time.) I went from
> 3.4.3 to 3.6.2.
>
> The procedure was to upgrade the following rpms on each host (daemon
> restarts were included), reading logs as I went:
>
> for i in mcollective-puppet-agent hiera facter puppet mcollective; do
> mco package $i update -F hostname=$SERVER; done
>
> Upgrading mcollective this way meant the last mco package never returned
> since the daemon was restarted, I'm fine with that.
>
> Then this for the puppetmasters to ensure the passenger-based
> puppetmasters were restarted:
>
> mco service httpd restart -F hostname=$SERVER; done
>
> These three issues, unfixed, would have been blockers for me doing an
> upgrade:
>
> 1) yumrepo mirrorlist vs baseurl (fixed in puppet 3.5.1)
>
> [2]https://tickets.puppetlabs.com/browse/PUP-2155 (dupe)
>
> Verdict: Went fine with the usual upgrade teething troubles. (Once I
> figured those out I reverted to my pre-upgrade VM snapshot on the first
> upgraded host and there was no hassle the second time.) I went from
> 3.4.3 to 3.6.2.
>
> The procedure was to upgrade the following rpms on each host (daemon
> restarts were included), reading logs as I went:
>
> for i in mcollective-puppet-agent hiera facter puppet mcollective; do
> mco package $i update -F hostname=$SERVER; done
>
> Upgrading mcollective this way meant the last mco package never returned
> since the daemon was restarted, I'm fine with that.
>
> Then this for the puppetmasters to ensure the passenger-based
> puppetmasters were restarted:
>
> mco service httpd restart -F hostname=$SERVER; done
>
> These three issues, unfixed, would have been blockers for me doing an
> upgrade:
>
> 1) yumrepo mirrorlist vs baseurl (fixed in puppet 3.5.1)
>
> [3]https://tickets.puppetlabs.com/browse/PUP-2150
>
> I was using mirrorlist, it was past time to use baseurl anyway. I never
> saw an error since I was on 3.4.3.
>
> Solution: use baseurl.
>
> 2) datacat module 0.4.2 incompatible with puppet >= 3.5 (fixed in
> datacat 0.5.0)
>
> [4]https://github.com/richardc/puppet-datacat/issues/12
> I was using mirrorlist, it was past time to use baseurl anyway. I never
> saw an error since I was on 3.4.3.
>
> Solution: use baseurl.
>
> 2) datacat module 0.4.2 incompatible with puppet >= 3.5 (fixed in
> datacat 0.5.0)
>
>
> I saw this sort of error on the puppetmaster:
>
> Jun 12 09:48:15 puppetmaster1dev puppet-master[4552]: undefined method
> `module' for "production":String at
> /etc/puppet/environments/production/modules/datacat/manifests/init.pp:59
> on node [5]puppetmaster1dev.company.com
> I saw this sort of error on the puppetmaster:
>
> Jun 12 09:48:15 puppetmaster1dev puppet-master[4552]: undefined method
> `module' for "production":String at
> /etc/puppet/environments/production/modules/datacat/manifests/init.pp:59
>
> Solution: upgrade the datacat module to 0.5.0
>
> 3) mcollective service/package trouble with puppet 3.5 (fixed in
> mcollective-puppet-agent 1.7.1)
>
> [6]https://tickets.puppetlabs.com/browse/MCOP-23
> Solution: upgrade the datacat module to 0.5.0
>
> 3) mcollective service/package trouble with puppet 3.5 (fixed in
> mcollective-puppet-agent 1.7.1)
>
>
> I saw the following errors when checking package status after the
> initial aborted upgrade of mcollective only, not any mcollective
> plugins.
>
> a) First, this after a plain upgrade (but without restarting the puppet
> agent):
>
> $ mco package mcollective status -F hostname=puppetmaster1dev
>
> * [ ==========================================================> ] 1 / 1
>
> [7]puppetmaster1dev.company.com: Could not autoload
> I saw the following errors when checking package status after the
> initial aborted upgrade of mcollective only, not any mcollective
> plugins.
>
> a) First, this after a plain upgrade (but without restarting the puppet
> agent):
>
> $ mco package mcollective status -F hostname=puppetmaster1dev
>
> * [ ==========================================================> ] 1 / 1
>
> puppet/type/package: no 'environments' in
> {:root_environment=>#<Puppet::Node::Environment:0x7fc087f1d070
> @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*",
> @config_version=nil>,
> :current_environment=>#<Puppet::Node::Environment:0x7fc087f1d070
> @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*",
> @config_version=nil>} at top of [[0, nil, nil]]
>
> Summary of Arch:
>
> No aggregate summary could be computed
>
> Summary of Ensure:
>
> No aggregate summary could be computed
>
> Finished processing 1 / 1 hosts in 46.00 ms
>
> b) Second, after restarting both mcollective and puppet:
>
> $ mco package mcollective status -F hostname=puppetmaster1dev
>
> * [ ==========================================================> ] 1 / 1
>
> [8]puppetmaster1dev.company.com: undefined method `properties' for
> {:root_environment=>#<Puppet::Node::Environment:0x7fc087f1d070
> @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*",
> @config_version=nil>,
> :current_environment=>#<Puppet::Node::Environment:0x7fc087f1d070
> @manifest="/tmp", @modulepath=[], @watching=true, @name=:"*root*",
> @config_version=nil>} at top of [[0, nil, nil]]
>
> Summary of Arch:
>
> No aggregate summary could be computed
>
> Summary of Ensure:
>
> No aggregate summary could be computed
>
> Finished processing 1 / 1 hosts in 46.00 ms
>
> b) Second, after restarting both mcollective and puppet:
>
> $ mco package mcollective status -F hostname=puppetmaster1dev
>
> * [ ==========================================================> ] 1 / 1
>
> <[9]christop...@pobox.com> wrote:
> > > > I only notice three issues where "Affects Version: 3.6.2". Have
> any of you upgraded to 3.6.2 yet? If so, where did you upgrade from and
> how's life now?
> > > >
> > > >
> [10]https://tickets.puppetlabs.com/browse/PUP-2752?jql=affectedVersion%20%3D%20%223.6.2%22
> > > > I only notice three issues where "Affects Version: 3.6.2". Have
> any of you upgraded to 3.6.2 yet? If so, where did you upgrade from and
> how's life now?
> > > >
> > > >
> > > >
> > > > (I'm probably doing this on our dev puppetmasters tomorrow, I will
> file tickets if there are any surprises.)
> > > >
> > > > --
> > > > 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 [11]puppet-users...@googlegroups.com.
> > > > (I'm probably doing this on our dev puppetmasters tomorrow, I will
> file tickets if there are any surprises.)
> > > >
> > > > --
> > > > 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,
> > > > To view this discussion on the web visit
> [12]https://groups.google.com/d/msgid/puppet-users/20140611204001.GA20741%40iniquitous.heresiarch.ca.
> > > > For more options, visit [13]https://groups.google.com/d/optout.
> > >
> > > --
> > > 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 [14]puppet-users...@googlegroups.com.
> > > --
> > > 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,
> > > To view this discussion on the web visit
> [15]https://groups.google.com/d/msgid/puppet-users/CAJ8DPF7PLa%2B3RNA8bO-E2aZcmhaMsTLZgZewE08sYAsJ7GQ8Fw%40mail.gmail.com.
> > > For more options, visit [16]https://groups.google.com/d/optout.
> >
> > --
> > 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 [17]puppet-users...@googlegroups.com.
> > --
> > 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
> > To view this discussion on the web visit
> [18]https://groups.google.com/d/msgid/puppet-users/20140612114824.GB25610%40iniquitous.heresiarch.ca.
> > For more options, visit [19]https://groups.google.com/d/optout.
>
> --
> 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 [20]puppet-users...@googlegroups.com.
> --
> 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
> To view this discussion on the web visit
> [21]https://groups.google.com/d/msgid/puppet-users/20140612163813.GA26648%40iniquitous.heresiarch.ca.
> For more options, visit [22]https://groups.google.com/d/optout.
>
> --
> 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 [23]puppet-users...@googlegroups.com.
> --
> 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
> To view this discussion on the web visit
> [24]https://groups.google.com/d/msgid/puppet-users/CAF_B3df4aUxOhNQbEonKm%2BdHmh%2BnmE1wPeHagy1-ve%2B3tgbG-w%40mail.gmail.com.
> For more options, visit [25]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:christop...@pobox.com
> 2. https://tickets.puppetlabs.com/browse/PUP-2155
> 3. https://tickets.puppetlabs.com/browse/PUP-2150
> 4. https://github.com/richardc/puppet-datacat/issues/12
> 5. http://puppetmaster1dev.company.com/
> 6. https://tickets.puppetlabs.com/browse/MCOP-23
> 7. http://puppetmaster1dev.company.com/
> 8. http://puppetmaster1dev.company.com/
> 9. mailto:christop...@pobox.com
> 10. https://tickets.puppetlabs.com/browse/PUP-2752?jql=affectedVersion%20%3D%20%223.6.2%22
> 11. mailto:puppet-users%2Bunsu...@googlegroups.com
> 12. https://groups.google.com/d/msgid/puppet-users/20140611204001.GA20741%40iniquitous.heresiarch.ca
> 13. https://groups.google.com/d/optout
> 14. mailto:puppet-users%2Bunsu...@googlegroups.com
> 15. https://groups.google.com/d/msgid/puppet-users/CAJ8DPF7PLa%2B3RNA8bO-E2aZcmhaMsTLZgZewE08sYAsJ7GQ8Fw%40mail.gmail.com
> 16. https://groups.google.com/d/optout
> 17. mailto:puppet-users%2Bunsu...@googlegroups.com
> 18. https://groups.google.com/d/msgid/puppet-users/20140612114824.GB25610%40iniquitous.heresiarch.ca
> 19. https://groups.google.com/d/optout
> 20. mailto:puppet-users%2Bunsu...@googlegroups.com
> 21. https://groups.google.com/d/msgid/puppet-users/20140612163813.GA26648%40iniquitous.heresiarch.ca
> 22. https://groups.google.com/d/optout
> 23. mailto:puppet-users...@googlegroups.com
> 24. https://groups.google.com/d/msgid/puppet-users/CAF_B3df4aUxOhNQbEonKm%2BdHmh%2BnmE1wPeHagy1-ve%2B3tgbG-w%40mail.gmail.com?utm_medium=email&utm_source=footer
> 25. https://groups.google.com/d/optout
Pete Brown
Jun 13, 2014, 1:37:33 AM6/13/14
to puppet-users
Nice report.
Thanks.
I have a dev environment i build with vagrant every day. I even
managed to bootstrap a puppetmaster in there for testing exported
resources.
Highly recommend using Vagrant because it forces you to fix those
dependency errors you would normally not see on live servers that have
been running for a while.
All my code gets the bugs tested out of it on base vms before it gets
pushed into production.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140612163813.GA26648%40iniquitous.heresiarch.ca.
Thanks.
I have a dev environment i build with vagrant every day. I even
managed to bootstrap a puppetmaster in there for testing exported
resources.
Highly recommend using Vagrant because it forces you to fix those
dependency errors you would normally not see on live servers that have
been running for a while.
All my code gets the bugs tested out of it on base vms before it gets
pushed into production.
Christopher Wood
Jun 13, 2014, 4:58:00 AM6/13/14
to puppet...@googlegroups.com
This was in the dev environment (not vagrant, just a separate set of VMs with their own set of puppetmasters). If things are fine for a few days I'll roll up through staging and production.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAJ8DPF4VGTqUpde4w7Bjf_U-Lb%2B%3DZM_hPwn3KBnx2WVrq-%3DiYA%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages