| Puppet Upgrade 9.0 to 9.0.1 [message #126972] |
Thu, 07 January 2016 20:03  |
nate.keegan
Messages: 46
Registered: June 2015
|
|
|
|
I followed the update procedure but I goofed up and did the initial cd /var/packages/pool/non-free && update-archive for the 9.0.1 deb file without having the site.pp file configured for auto-updates on the Pupper server.
In my logs on the downstream server (backend for example) I'm seeing the attached which I'm not 100 percent certain how to address or whether this is due to my screwing up the sequence on the Puppet server or not.
In a nutshell this is what I'm seeing in the logs:
Jan 7 16:48:11 kerio-backend1 puppet-agent[5605]: (/Stage[main]/Kerio_cloud::Backend/Debconf_package[kerio-con nect]/Package[kerio-connect]/ensure) change from 9.0.0.291-1 to 9.0.1.394-1 failed:
Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install kerio-connect' returned 100: Reading package lists...
#012Building dependency tree...
#012Reading state information...
#012The following packages will be upgraded:
#012 kerio-connect#0121 upgraded, 0 newly installed, 0 to remove and 28 not upgraded.
#012Need to get 312 MB of archives.
#012After this operation, 105 kB of additional disk space will be used.
#012WARNING: The following packages cannot be authenticated!
#012 kerio-connect
#012E: There are problems and -y was used without --force-yes
#012 at /etc/puppet/modules/debconf_package/manifests/init.pp:64
For some reason my logs are in UTC time rather than local time but that isn't a big deal.
My question then is whether this is caused by my sequencing mistake (and if so how to fix it) or something else related to a Puppet config or the .deb file itself.
This is in our lab environment so is not impacting anything for production although I want to start our migration process from Exchange to Kerio using 9.0.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Puppet Upgrade 9.0 to 9.0.1 [message #127196 is a reply to message #127188] |
Fri, 15 January 2016 15:13  |
nate.keegan
Messages: 46
Registered: June 2015
|
|
|
|
All back-end updated following the procedure listed:
- Deb x86 package on Puppet in /var/packages/pool/non-free
- Edited site.pp on Puppet to allow auto-update
- Ran update-archive on Puppet, no issues
- Ran apt-get update and apt-get install kerio-connect on each back-end
I will update our internal documentation set on the procedure.
I appreciate the help on this as this type of a scenario is very useful since one doesn't typically have to upgrade a mail system with a high rate of frequency.
Compared to say an Exchange cumulative update procedure this is a breeze so no complaints on my end of things.
|
|
|
|
|
|
|
|
|
|
|
|
Members
Search
Help
Register
Login
Home
