I have tried several time to update to latest version 7.300 from 7.202 .After 100 % it shows Up2date package Initialization Failed.
ASG Installed on VMware Server.
There is a certain complexity to handling errors inside the up2date installation. The old behavior was to just not raise the system version in case an error occurred, because usually a) the goal is that no error should occur, so this would ensure that we could check it out whenever something failed and b) it's hard to automatically figure out what exactly caused the error and react accordingly. The problem in this special case is that the check which you are actually overriding with "--rpmargs --force" effectively prohibits the user to try installation again (once the package installation failed, every following installation will fail, too). We certainly underestimated the amount of cases where the first installation try would fail; very prominent amongst them are script timeouts because of high load environments, seemingly random failure of init scripts to bring services up/down, or the manual installation of RPMs causing problems.
Now, of course, we did address that problem, but as stated above it is the complexity of automatically handling errors when a plethora of error cases is possible, and the danger that failure to correctly handle it can render systems unusable, which keeps us from releasing it. The code change which is planned for this issue will make a re-installation of the package possible in cases where RPMs of the same package have already been installed (either in the last run, or a support package, or whatever reason). It will also reduce the cases where the system version is not increased due to an error during installation, but that comes with a price. Certain errors during the installation phase will now require a system reboot to ensure a sane environment. Because this can also happen for up2date packages which regularly would not require a reboot, we are reluctant to release it. Of course we could do it like a certain OS and just state in every up2date that it "may require a system restart" ... but I am pretty sure you wouldn't like that. So we're taking our time searching for improvements and working on the surroundings of the up2date process to reduce the probability of cases where a reboot would be required.
So, in my opinion, you're currently being faced with the lesser of two evils. We are aware of the situation, and are working on a solution, but as the up2date is one of the most vital parts of our system we want a stable solution which improves the situation for everyone, in every case.
