I'm not sure why this is happening. The best way I can think of to attack this problem would be to find a package that was installed in the second image-update that wasn't in the first, then go back to the original be and install (with the -v option) that package plus entire and the other consolidations all with the explicit version listed that you expected the image-update to take you to. Presumably, that will fail and we might be able to figure out what went wrong from the output it shows.

Brock

On 07/30/10 02:25 PM, Glenn Lagasse wrote:
Hi,

I'm seeing a problem when I try to image-update (ONU) a SPARC machine
which is running build 144 to more recent ON bits that I've built.  This
seems to be particular to this one machine.  I don't have a problem
updating X86 machines or another SPARC machine.  My nightly builds
cleanly, and onu doesn't return any errors, but it only installs 4
packages:

pkg -R /tmp/onu.vPaywd image-update
DOWNLOAD                                  PKGS       FILES    XFER (MB)
Completed                                  4/4       63/63      0.4/0.4

PHASE                                        ACTIONS
Removal Phase                                    2/2
Install Phase                                    3/3
Update Phase                                   83/83
beadm-ON has been updated successfully

(I can supply the full output from onu as requested).

At this point, the new BE (beadm-ON) doesn't appear to have any updated
packages from my ON repository.  I can reboot into the new BE and then
this is where it gets weird.  If I stand up my ON repo (onu -r -d<path
to repo>) and then do an image-update (just pkg image-update) a new BE
is created and a lot more packages are installed:

r...@wetblanket>  pkg image-update
~/repo/onnv-clone
DOWNLOAD                                  PKGS       FILES    XFER (MB)
Completed                              205/205   2750/2750    97.0/97.0

PHASE                                        ACTIONS
Removal Phase                                792/792
Install Phase                                850/850
Update Phase                               8715/8715

A clone of beadm-ON exists and has been updated and activated.
On the next boot the Boot Environment beadm-ON-1 will be mounted on '/'.
Reboot when ready to switch to this updated BE.

And sure enough if I look in the new BE, packages/bits that I expect to
be updated actually are.

Can anyone explain this?  Help me track down why it's behaving like
this?  I have a wad that I'm ready to push, but while I can't think of
what any of my changes would have to do with this I'm leary to push
until I understand what's happening and why.

Thanks,

Glenn
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev

_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev

Reply via email to