Hi Wencheng,

I suggest you log this with Micro Focus support team.


You said you received the error with Sentinel version 8.4 Appliance. What does that mean, upgrade to 8.4, or upgrade from 8.4 to 8.5?

You said online upgrade, so I guess 8.4 to 8.5 then?


Today one of our partners had the same, also online upgrade, but that was Sentinel 8.2.0.1.5156 to 8.5 upgrade, while OS was SLES 12 SP3. So OS Suse upgrade, 12 SP3 to SP5.
I suggested to them to do it in stages, so use the offline patch iso's instead. You have used them before?


With Sentinel 8.4 appliance, was the OS on SLES 12 SP5 already? Or that was not upgraded, was it SLES 12 SP3 or SP4? It explains the conflict error. It's important you not only run, zypper -v patch, to upgrade sentinel, but zypper up, as well, for upgrading OS.

-----------------------------------------
Important note - there is a discrepancy between the readme you get from the the download site, so that accompanies the offline patch iso, and the official documentation online (www.microfocus.com/.../).

Check this, see readme_iso.rar attached, and compare it with online docs:
www.netiq.com/.../t4b78khmt11o.html

Above link mentions, so 8.4 upgrade, this command "zypper up". The attached readme that comes with the patch iso, for 8.4, there is no mention of this command. Yes zypper patch (zypper -v patch), not zypper up.

8.3 seems ok - www.netiq.com/.../t4b78khmt11o.html

8.3 SP1 is wrong, so you have to run zypper up as well - www.netiq.com/.../t4b78khmt11o.html

8.4 is wrong, so you have to run zypper up as well - www.netiq.com/.../t4b78khmt11o.html

So readme that comes with offline patch iso for 8.3 SP1, and 8.4 should include zypper up command as well. If that zypper up, isn't run OS will not be upgraded! Verify the same for 8.5 if interested in that upgrade path as well.

a. zypper -v patch

b. zypper up

Enter Y to proceed.

c. (Conditional) Before the upgrade, if event visualization is enabled, after upgrading to Sentinel 8.4.0.0, Elasticsearch stops as it is enabled with X-Pack security plug-in, to start Elasticsearch follow the procedure in Settings in Elasticsearch for Secure Cluster Communication.

d. rcsentinel start

The last step is very important as well, rcsentinel start, as that will upgrade the database! This needs to be done before reboot, otherwise the upgrade is incomplete, as DB is not updated, and this cannot be done after reboot!


So ensure you follow the upgrade path to the letter, if not done correctly, some components might not get updated correctly, for example database. So make sure you have vmware snapshot, or backup.
-----------------------------------------


Is this virtualized? Is it possible to go back to the original vmware snapshot?


If above doesn't help log a case, and technical support will deal with it. Also we require a FULL set of sentinel logs. This will allow us to verify the upgrade process, and health of the system.

Hope this helps...


Thanks,


Henk

readme_iso.rar

Hi Wencheng,

I suggest you log this with Micro Focus support team.


You said you received the error with Sentinel version 8.4 Appliance. What does that mean, upgrade to 8.4, or upgrade from 8.4 to 8.5?

You said online upgrade, so I guess 8.4 to 8.5 then?


Today one of our partners had the same, also online upgrade, but that was Sentinel 8.2.0.1.5156 to 8.5 upgrade, while OS was SLES 12 SP3. So OS Suse upgrade, 12 SP3 to SP5.
I suggested to them to do it in stages, so use the offline patch iso's instead. You have used them before?


With Sentinel 8.4 appliance, was the OS on SLES 12 SP5 already? Or that was not upgraded, was it SLES 12 SP3 or SP4? It explains the conflict error. It's important you not only run, zypper -v patch, to upgrade sentinel, but zypper up, as well, for upgrading OS.

-----------------------------------------
Important note - there is a discrepancy between the readme you get from the the download site, so that accompanies the offline patch iso, and the official documentation online (www.microfocus.com/.../).

Check this, see readme_iso.rar attached, and compare it with online docs:
www.netiq.com/.../t4b78khmt11o.html

Above link mentions, so 8.4 upgrade, this command "zypper up". The attached readme that comes with the patch iso, for 8.4, there is no mention of this command. Yes zypper patch (zypper -v patch), not zypper up.

8.3 seems ok - www.netiq.com/.../t4b78khmt11o.html

8.3 SP1 is wrong, so you have to run zypper up as well - www.netiq.com/.../t4b78khmt11o.html

8.4 is wrong, so you have to run zypper up as well - www.netiq.com/.../t4b78khmt11o.html

So readme that comes with offline patch iso for 8.3 SP1, and 8.4 should include zypper up command as well. If that zypper up, isn't run OS will not be upgraded! Verify the same for 8.5 if interested in that upgrade path as well.

a. zypper -v patch

b. zypper up

Enter Y to proceed.

c. (Conditional) Before the upgrade, if event visualization is enabled, after upgrading to Sentinel 8.4.0.0, Elasticsearch stops as it is enabled with X-Pack security plug-in, to start Elasticsearch follow the procedure in Settings in Elasticsearch for Secure Cluster Communication.

d. rcsentinel start

The last step is very important as well, rcsentinel start, as that will upgrade the database! This needs to be done before reboot, otherwise the upgrade is incomplete, as DB is not updated, and this cannot be done after reboot!


So ensure you follow the upgrade path to the letter, if not done correctly, some components might not get updated correctly, for example database. So make sure you have vmware snapshot, or backup.
-----------------------------------------


Is this virtualized? Is it possible to go back to the original vmware snapshot?


If above doesn't help log a case, and technical support will deal with it. Also we require a FULL set of sentinel logs. This will allow us to verify the upgrade process, and health of the system.

Hope this helps...


Thanks,


Henk

readme_iso.rar

HI

    My sentinel version is 8.4 Appliance which OS is SLES12SP3.

I had tested (1) All Offline upgrade: SLES12SP5 +sentinel 8.5....but the 9443 webconsole disappear and it prompt indexing service seem not starting when manual start sentinel service  ( 2) online upgrade. it occur a VBASE conflict , after patch & upgrade...the 9443 webconsole disappear.

     Wencheng

Yes

     It is VM...I have snapshot befor I did these offline/online update testing.

Wencheng