New upgrade behavior in case of pre-upgrade unpublished changes

[Itai_Minuhin]

Hi everyone, 

I wanted to bring to your attention a behavioral change in the Management server upgrade .

This behavioral change is relevant only for upgrades from R80.20 and above (for all relevant upgrade paths, lookup for "Upgrade paths" in sk135172)

So far the Management server upgrade has been blocked by a pre-upgrade verification in cases where there are unpublished changes in the management server (open sessions).

From now on,  upgrades will not be blocked in case of open sessions.  Meaning that the system will let you upgrade even when there are unpublished changes. 

Important to note that the unpublished changes will not be upgraded, so it is recommended to publish important changes before the upgrade. 

This change is documented in sk163814. Soon it will be documented in the installation and upgrade guide as well.

A proper notification has been added to the pre-upgrade verification output.

Thank you, 

Itai

[Raj_Khatri]

Hi Itai,

Thank you for this post, however, I have a question regarding verification.  We are planning an upgrade from R80.20 to R80.40.  Our environment consists of the following and receiving verification failed only on the MLM.  Is that normal behavior now introduced in R80.20?  In the past all 3 have verified successfully when downloaded via CPUSE WebUI (Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz)

MDS - Smart1

MLM - HP OpenServer

SME - HP OpenServer

Once the MDS is upgraded to R80.40 and up and running, will the MLM verification pass at that point?  Just looking to eliminate any possible upgrade issues.

Thanks