Hi Mike, On 21.05.2012 13:26, Mike Burgener wrote:
Has nobody any idea on this?
Maybe you could post a full debug log from one of the machines where it obviously does not "update" properly and a full listing of the XML defining the package.
Very likely WPKG does not execute the upgrade commands as it does not detect an upgrade - ie. this means the package was not installed in older revision on the nodes which do not "update" properly. If the package is "new" to a host, then WPKG executes the "install" commands, not "upgrade".
So please check the local wpkg.xml on the nodes which do not work properly. Maybe these machines got an earlier version of the package deployed. If the revision attribute has not been incremented since then WPKG will not perform an upgrade. So assuming you probably incremented the revision attribute before, then these hosts might have performed the upgrade already and now if you change the package on server side without incrementing the revision then WPKG will not re-execute the upgrade commands.
br, Rainer ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
