On 06/13/12 11:05, Alan Steinberg wrote:
Pete's comments seem to relate back to my original question: What is AI
doing to allow the install to succeed while the Test install fails?


The pkg uninstall that's causing the exception is not part of any of the test AI installation scenarios.

Dave

-- Alan

On 06/13/12 02:34 AM, Peter Dennis wrote:


On 06/12/12 22:24, Dave Miner wrote:
On 06/12/12 17:06, Alan Steinberg wrote:


On 06/12/12 11:58 AM, Dave Miner wrote:
On 06/12/12 14:28, Alan Steinberg wrote:
We just hit a bug where an obsolete package is still listed in the
system group packages. This causes the text install to fail, but
the AI
install apparently just skips it and doesn't report any issues. Is
the
method by which the text install uses the group packages different
than
how AI uses them? Does AI do a check for a package's state?

-- Alan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Interactive installs are always copying the contents of the booted
image; AI installs are installing packages directly. This means that
interactive installs have to uninstall media-specific content so that
the installed system doesn't try to act like an install image. That
should just be removing the packages system/install/media/internal and
system/install/text-install in this case.

Dave

I understand that the text install from media will install the packages
found in the ISO image, and a text install from the network would
install from the repository. Both of these fail due to the obsolete
package. The AI install succeeds, though. This is why I am thinking
that
the text install and the AI create the list of installation packages
differently. AI must be detecting an obsolete package and removes it
from the list, while the text installer doesn't do this check, and
therefore fails to install the obsolete package. I'm looking for
validation on this thought, and whether one of these installation
methods should change to either fail at creation or fail at
installation.


No, a text install from network does not use a package repository at
all. It works the same as a text install from media, it just has a
different package set because the solaris-auto-install group is used,
rather than solaris-large-server.

I don't understand the root cause of the problem that's been observed
yet, honestly, but the package operation should be the same as what
happens on text installs from media.


There is a group package dependency here on the package in question:

set name=pkg.fmri
value=pkg://solaris/group/system/[email protected],5.11-0.175.1.0.0.18.0:20120607T032520Z

....
depend fmri=system/floating-point-scrubber type=group variant.arch=sparc
....


and within the package's manifest:

set name=pkg.fmri
value=pkg://solaris/system/[email protected],5.11-0.175.1.0.0.18.0:20120607T030108Z

set name=variant.debug.osnet value=true value=false
set name=variant.opensolaris.zone value=global value=nonglobal
set name=pkg.obsolete value=true
set name=variant.arch value=sparc
set name=org.opensolaris.consolidation value=osnet

and from pkg(5) we have:

If the value is group, the dependency is
required unless the package is on the image
avoid list. Note that obsolete packages
silently satisfy the group dependency. See the
avoid subcommand in pkg(1).

and so this is package should satisfy the obsolete requirement
but for some reason the older packages have been picked up
but they violate the constraints put in place by the associated
osnet-incorporation which has a:

depend
fmri=pkg:/system/[email protected],5.11-0.175.1.0.0.18.0
type=incorporate variant.arch=sparc

So is there something up with the group package resolutions
or something up with the actual manifest for the floating-point-scrubber
package ?

pete

Dave
-- Alan

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to