Captain
Captain
897 views

oes18sp2 and patches

Jump to solution

Hi All,

Not sure if anyone could help, Upgrade our servers from oes18-sp1 to oes18-sp2 all worked fine. Then I patched the servers using SMT and have found that during patches install crash occurs on all servers. Seems that there is an issue with grub2-i386, dracut and tomcat-servlet-4_0-api patches. Never seen this before.

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Captain
Captain

Thanks for your time in responding.  Found the issue, during patching cpu was coring. resolved the core issue and patches install successfully.

View solution in original post

0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Please log an SR and let us know the number.

Thanks

Tarik

0 Likes
Vice Admiral
Vice Admiral

I've had a similar problem today on OES 18sp2.  Server working fine, than ran yast online_update, installed latest patches, rebooted, and now NDSD won't start.

I've raised an SR (SR#101308191561 ), but not heard anything yet.

0 Likes
Captain
Captain

Just wondering if there was a solution to this.  Upgraded servers to OES2018 SP2 all working fine then when patching an error:

Subprocess failed. Error: RPM failed: error: package grub2-i386-pc-2.02-12.21.1.x86_64 is not installed

patching fails.

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

How did you perform the upgrade from SP1 to SP2? Media? Wagon?

Did you include current code from the SP2 update channels during the upgrade?

Had the SP1 offset been patched to the top before starting the upgrade?

Is EFI in use?

 

If you like it: like it.
0 Likes
Captain
Captain

SP1 was patched with latest updates prior upgrading to SP2. Upgraded to SP2 using media and did not include the update channel during the upgrade. Upgrade went well, all services up and running after upgrade.

Then using our SMT channel for patching. No dependency errors are detected then half way though patching quits unexpected. Run the patch again and the error is detected.

EFI is not used.

The following packages are also detected as excluded packages;

tomcat-servlet-4_0-api-9.0.36-3.45.1
apache2-prefork-2.4.23-29.63.1
dracut-044.2-17.12.1

 

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

I try to avoid this way of upgrading if ever possible as it generally involves downgrading code. And the more time passes by after the media release the greater the gap will be. Nevertheless i've just duped the way you went and had no issues. So let's concentrate on

grub2-i386-pc-2.02-12.21.1.x86_64

which is the version you SHOULD have after a media-based upgrade to SP2 without the SP2 update channels (this build resides in both the ISO file and the pool repo). The error you're facing implies that you have something older after the media upgrade and before patching via SMT. Which build do you have right after the media upgrade?

 

If you like it: like it.
0 Likes
Captain
Captain

Thanks for your time in responding.  Found the issue, during patching cpu was coring. resolved the core issue and patches install successfully.

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.