Re: Why does this luupgrade command fail, but this one works?
- From: RJ <roger0080@xxxxxxxxxxxx>
- Date: Mon, 21 Apr 2008 23:20:19 -0500
RJ wrote:
RJ wrote:I am upgrading an x86 s10u4 to s10u5 via live upgrade.
I have removed the s10u4 SUNWluu SUNWlur SUNWlucfg and added the same packages from the new s10u5 dvd.
I have also added patch 137322-01 for p7zip.
When I run the luupgrade command it fails with an error that it can't append my profile.
I had this same problem with s10u3 to s10u4 but can't for the life of me recall how I resolved the problem.
In both cases I ended up looking inside the luupgrade script for the problem specifics.
But, in this case, I copy the luugrade script to a local directory, and bracket the part in the script causing the error message to be displayed using "set -x/set -x" in the script. Doing this causes it to work! Say what???
Anyone ???
Crazy.
See below:
root@xxxxxxxxxxxxxxxx# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
slice0 yes yes yes no -
slice6 yes no no yes -
root@xxxxxxxxxxxxxxxx# cat profile
install_type upgrade
### THIS STOCK /usr/sbin/luupgrade COMMAND FAILS ###
root@xxxxxxxxxxxxxxxx# luupgrade -D -u -n slice6 -s /cdrom/cdrom0 -j profile
Install media is CD/DVD. </cdrom/cdrom0>.
Waiting for CD/DVD media </cdrom/cdrom0> ...
Copying failsafe multiboot from media.
Uncompressing miniroot
Creating miniroot device
miniroot filesystem is <ufs>
Mounting miniroot at </cdrom/cdrom0/Solaris_10/Tools/Boot>
Validating the contents of the media </cdrom/cdrom0>.
The media is a standard Solaris media.
The media contains an operating system upgrade image.
The media contains <Solaris> version <10>.
Constructing upgrade profile to use.
ERROR: Cannot append upgrade profile <-j profile> to </tmp/.luupgrade.profile.upgrade.6540>.
### USE A LOCAL TWEAKED VERSION OF luupgrade WITH THE set -x/set +x in it:
root@xxxxxxxxxxxxxxxx# which luupgrade
/usr/sbin/luupgrade
root@xxxxxxxxxxxxxxxx# cp /usr/sbin/luupgrade .
root@xxxxxxxxxxxxxxxx# vi luppgrade
<edit local copy of lupgrade to show shell commands being executed via "set -x">
### HERE IS THE diff's BETWEEN THE TWO:
root@xxxxxxxxxxxxxxxx# diff /usr/sbin/luupgrade luupgrade
4420a4421
> set -x
4422a4424
> set +x
### NOW IT WORKS!
root@xxxxxxxxxxxxxxxx# ./luupgrade -D -u -n slice6 -s /cdrom/cdrom0 -j profile
Install media is CD/DVD. </cdrom/cdrom0>.
Waiting for CD/DVD media </cdrom/cdrom0> ...
Copying failsafe multiboot from media.
Uncompressing miniroot
Creating miniroot device
miniroot filesystem is <ufs>
Mounting miniroot at </cdrom/cdrom0/Solaris_10/Tools/Boot>
Validating the contents of the media </cdrom/cdrom0>.
The media is a standard Solaris media.
The media contains an operating system upgrade image.
The media contains <Solaris> version <10>.
Constructing upgrade profile to use.
+ + /bin/egrep -v ^[ ]*install_type[ ]*upgrade[ ]*$
+ /usr/lib/lu/lucomm_del profile
+ 1>> /tmp/.luupgrade.profile.upgrade.7072
ERRMSG=
Locating the operating system upgrade program.
Checking for existence of previously scheduled Live Upgrade requests.
Creating upgrade profile for BE <slice6>.
Checking for x86 boot partition on ABE.
Determining packages to install or upgrade for BE <slice6>.
Simulating the operating system upgrade of the BE <slice6>.
The operating system upgrade simulation is complete.
Simulating update of package information on boot environment <slice6>.
INFORMATION: The file </var/sadm/system/logs/upgrade_log> on boot
environment <slice6> contains a log of the upgrade operation.
INFORMATION: Review the files listed above. Remember that all of the files
are located on boot environment <slice6>. Before you activate boot
environment <slice6>, determine if any additional system maintenance is
required or if additional media of the software distribution must be
installed.
The Solaris upgrade of the boot environment <slice6> is complete.
root@xxxxxxxxxxxxxxxx#
Second one works because I have the ending "set +x" right before the return code test.
Does anyone know what the cause of the message "ERROR: Cannot append upgrade profile -j profile> to </tmp/.luupgrade.profile.upgrade.6540>." is?
Never mind.
It is pointless to use a profile with just the line "install_type upgrade". I was in the wrong mindset. Duh, that is why it is called live upgrade.
The luupgrade script strips off the line "install_type upgrade" and then appends on all of your other profile options. Since I had no profile options in my profile, the egrep command was not matching anything, and thus it thinks there is an error.
Either add an option in your profile or just skip using the -j profile option.
.
- References:
- Prev by Date: Re: Why does this luupgrade command fail, but this one works?
- Next by Date: Re: How to kill a zone's console login prompt over a tip connection?
- Previous by thread: Re: Why does this luupgrade command fail, but this one works?
- Next by thread: How to kill a zone's console login prompt over a tip connection?
- Index(es):
Relevant Pages
|
