{"id":380,"date":"2010-06-07T02:12:50","date_gmt":"2010-06-07T07:12:50","guid":{"rendered":"http:\/\/yourlinuxguy.com\/?p=380"},"modified":"2010-06-07T20:16:18","modified_gmt":"2010-06-08T01:16:18","slug":"how-can-i-remotely-upgrade-from-oes2-sp1-to-oes2-sp2","status":"publish","type":"post","link":"https:\/\/yourLinuxGuy.com\/?p=380","title":{"rendered":"How can I remotely upgrade from OES2-SP1 to OES2-SP2?"},"content":{"rendered":"<p>This is just a simplified adaptation of a community post by author <a title=\"http:\/\/www.novell.com\/communities\/user\/6477\" href=\"http:\/\/www.novell.com\/communities\/user\/6477\" target=\"_blank\">sakila<\/a> here:<br \/>\n<a title=\"http:\/\/www.novell.com\/communities\/node\/9298\/patching-and-upgrading-oes2-sp1-oes2-sp2\" href=\"http:\/\/www.novell.com\/communities\/node\/9298\/patching-and-upgrading-oes2-sp1-oes2-sp2\" target=\"_blank\">http:\/\/www.novell.com\/communities\/node\/9298\/patching-and-upgrading-oes2-sp1-oes2-sp2<\/a><br \/>\n&#8230;all due credit (and thanks) to the author for putting that together!!\u00a0  Please read that doc first to get a feel for what I&#8217;m after here, and take in all the warnings and caveats.\u00a0  Maybe even post a comment, and thank the author&#8230;  \ud83d\ude09<\/p>\n<p>I don&#8217;t know about you, but the last thing I want to have to do during a server OS upgrade is drive all around the state to go hit &#8220;enter&#8221; on a console or something.\u00a0 If I can&#8217;t do it remotely, I don&#8217;t want to do it!\u00a0 So my intention here is just to document a possible remote upgrade method, clean up some typos, and so forth.\u00a0 Please note that I have followed this procedure a good handful of times, and have had great success with it so far.\u00a0 If you follow this procedure, make sure to drop a comment and let me know how it went.<\/p>\n<p>And for heaven&#8217;s sake, if you don&#8217;t know what you&#8217;re doing, don&#8217;t do this!\u00a0  Read it all through first, maybe test on a demo machine, etc&#8230;\u00a0 Also, I hope it goes without saying that you&#8217;ll probably want to make use of the &#8220;<code>screen<\/code>&#8221; utility to do all this work&#8230;\u00a0 More on <code>screen<\/code> another time&#8230;<\/p>\n<p>Anyway, back to the task at hand&#8230;<\/p>\n<p>First, patch your OES2-SP<strong>1<\/strong> system completely up-to-date with this:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>rug up -t patch -g security -g recommended OES2-SP1-Updates SLES10-SP2-Updates<\/code><\/span><\/pre>\n<p>&#8230;but watch out for being prompted for the <a title=\"http:\/\/yourlinuxguy.com\/?p=314\" href=\"http:\/\/yourlinuxguy.com\/?p=314\" target=\"_blank\">move-to-sles10-sp3 issue<\/a> !!\u00a0 Reboot as needed.<\/p>\n<p>Now a quick aside or two, right in the midst of things&#8230; If you have a crazy, complicated admin password, change it temporarily for this process.\u00a0 Set it to &#8220;changeme&#8221;, or &#8220;temp123&#8221;, or anything without special characters.\u00a0 You&#8217;ll thank me for it later, and it will work better when you create the &#8220;answer&#8221; file.\u00a0 Also, please remember that if you have an SMT server, make sure to prepare the new channels you&#8217;ll need.\u00a0 Oh, and if you have custom installation sources (like and ftp server or webserver with ISOs mounted on it or something), they&#8217;ll be useless in a few minutes anyway, so you may want to delete them now&#8230;<\/p>\n<p>Then, assuming all patches are up to date, your server codes are valid, etc., etc., the first step of the process is to get the &#8220;update&#8221; patch in place:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>rug in -t patch move-to-oes2-sp2<\/code><\/span><\/pre>\n<p>&#8230;you should not need to reboot here.<\/p>\n<p>Now the box is mid-way between versions.\u00a0 We can see that it needs its versioning and control packages (those that define what version it is to be) with this command:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>rug lu -t patch<\/code><\/span><\/pre>\n<p>So now we need to continue to turn it into an extremely un-patched OES2sp<strong>2<\/strong> server, with this command:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>rug up -t patch -g recommended<\/code><\/span><\/pre>\n<p>&#8230;and DO NOT REBOOT when prompted!\u00a0  Because if you reboot now, you will need to physically be at the console screen to enter the eDirectory tree Admin password when prompted.\u00a0  We don&#8217;t want that (unless you have HP Lights-out boards or something).\u00a0 So, in order to create an answer file to automatically stuff the the Admin password in (remember, you changed it to something simple, right?), do the following:\u00a0 In a shell session, as root,<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>cd \/root<\/code><\/span><\/pre>\n<p>&#8230;to ensure the answer file is away from other users, since it will be created in your working directory.\u00a0  Now create the answer file like this:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>yast create-answer-file [adminpassword]<\/code><\/span><\/pre>\n<p>&#8230;of course, replacing &#8220;<code>[adminpassword]<\/code>&#8221; with your eDirectory Admin password.\u00a0 Unfortunately, you must enter the password on the command line, then it re-displays it to you, so:<\/p>\n<ol>\n<li> make sure there are no eyes on the monitor other than yours while doing this, and<\/li>\n<li>I strongly recommend that when you finish this session, you log back in and vi \/root\/.bash_history and remove the line with the admin password (so other users don&#8217;t see it later!)<\/li>\n<\/ol>\n<p>Now, copy it to where it needs to be:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>cp answer \/opt\/novell\/oes-install\/<\/code><\/span><\/pre>\n<p>Now reboot:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>init 6<\/code><\/span><\/pre>\n<p>When the server is back up and running, it will complete the update of all the OES-related services; this takes some time.\u00a0 Once that&#8217;s done, you need to do a final round of patching with our brand-new updated channels:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>rug up -t patch -g security -g recommended OES2-SP2-Updates SLES10-SP3-Updates<\/code><\/span><\/pre>\n<p>&#8230;and reboot if needed.\u00a0  Oh, and some cleanup&#8230;\u00a0 Delete the temp answer file:<\/p>\n<pre><span style=\"font-size: xx-small;\"><code>rm \/opt\/novell\/oes-install\/answer<\/code><\/span><\/pre>\n<p>&#8230;And don&#8217;t forget to remove the answer file password line from your <code>\/root\/.bash_history<\/code>&#8230;\u00a0 And change your Admin password again&#8230;<\/p>\n<p>And as a final step, clean up your installation sources (<code>yast inst_source<\/code>) if you had custom ones.  And you&#8217;ll also need to re-add your &#8220;Add-On&#8221; source for the OES software;\u00a0 it&#8217;s a requirement.\u00a0 So one way to do it would be to run &#8220;<code>yast add-on<\/code>&#8221; , and walk through the steps of adding the URL to the source, ensuring all the patterns are listed (they should all be set to &#8220;Reconfigure is Disabled&#8221;).<\/p>\n<p>And that&#8217;s it!\u00a0  If all went well, you should now have a fully upgraded server.\u00a0 Enjoy!<\/p>\n<p>8)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is just a simplified adaptation of a community post by author sakila here: http:\/\/www.novell.com\/communities\/node\/9298\/patching-and-upgrading-oes2-sp1-oes2-sp2 &#8230;all due credit (and thanks) to the author for putting that together!!\u00a0 Please read that doc first to get a feel for what I&#8217;m after&#8230;<br \/><a class=\"read-more-button\" href=\"https:\/\/yourLinuxGuy.com\/?p=380\">Read more<\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[12,83,82,72],"tags":[],"class_list":["post-380","post","type-post","status-publish","format-standard","hentry","category-advanced","category-oes2sp1","category-oes2sp2","category-rug"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pnjn1-68","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/380","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=380"}],"version-history":[{"count":42,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/380\/revisions"}],"predecessor-version":[{"id":522,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/380\/revisions\/522"}],"wp:attachment":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}