On 09/ 8/11 10:57 AM, Tyson Ainsworth - Oracle wrote:
Hi Jack,
Thanks for the quick response. I am trying to create an AI client
image of b173. I have set the default publisher to
http://netinstall-s11.us.oracle.com/solaris
I was wondering if perhaps the manifest files had changed so I used my
manifest file with the 173 AI image downloaded from nana and it work
great there.
Sounds like a mismatch between your publisher contents and B173.
If I try using the default manifest file in
<image_path>/auto_install/manifest ,without any modifications, with my
DC created image I get the "AI manifest failed validation" error.
This leads me to think that there is something wrong / different about
my DC AI client image. What do you think?
I think that what you tried should have worked, because a default
manifest should work with the image it comes from. The bits in your
image sound inconsistent with each other.
I don't know what changes there are between netinstall-s11 and the
pristine packages at ipkg. I would start with
ipkg.us.oracle.com/solaris11/dev. Also, I was reminded that for 173,
you *do* need to build 173 AI client images on a 173 system.
I'm not sure what your end goal is; perhaps you want to customize your
image. If this is so, I suggest getting a reference 173 image working
first, then you can start diverging by tweaking/customizing your image.
Ping me further if you want to know more on how to do this.
Thanks,
Jack
Thanks,
Tyson
On 09/08/11 10:22, Jack Schwartz wrote:
Hi Tyson.
Sounds like you built an AI client image with bits that are
incompatible with your manifest. Check the publisher you specified
under the "transfer-ips-install" <software> tag in the DC manifest
you used to build your AI client image. Is it current? The default,
http://pkg.oracle.com/solaris/release is not current. The most
current is http://ipkg.us.oracle.com/solaris11/dev.
(Side note: You'll probably want to set all publisher settings to the
same value.)
Another possibility is that you built your image with current bits
but you based your manifest on an old manifest template. Lately
manifest definitions have been changing frequently. The manifest you
create should be based on the image you will use them with. Do the
following to check this out:
On the system where you created your service, check out the
default.xml and ai_manifest.xml files of your service and compare
them with your failing manifest. Find these files by doing
installadm list and looking under
<image_path>/auto_install/manifest. In the same directory you will
also find the DTD specifications which define the format of the
manifest.
On a related but tangential note, it is best to build a version X
image on a version X system. So if you are building a B173 AI client
image, do it on a B173 system. Version mismatches *could* work but
are not guaranteed.
I hope that helps,
Jack
On 09/ 8/11 07:31 AM, Tyson Ainsworth wrote:
Hi,
I am having a problem with a DC AI image that I have created. I
have successfully created an AI ISO image using distro constructor.
I can then successfully create an install service using installadm
create-service. I have a problem adding a manifest to this
service. I get "AI manifest failed validation: No declaration for
element target ...." Several elements are listed. If I create an
install service with the AI ISO image made available for download.
I can add the same manifest file without any problems. I must be
missing something. Does anyone have any ideas on what I am missing
or doing wrong?
Thanks,
Tyson
_______________________________________________
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
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
