Hi Frank,
On 09/ 8/10 09:40 AM, Frank Allan wrote:
Jan
the system is on an internal customer network and I cannot get the
files off without an extended security process.
The install log shows a lot of detail about the disk identification
and selection and ends up selecting the requested disk (c3t2d0) and
using the entire disk.
the only things in the log after that are the same three AI lines as
before - no extra info.
sc_manifest.xml is empty
That is the problem - we need to find out, why you ended up with empty file.
I am thinking my client manifests are bad/incorrect.
I tried deleting the manifest I created for the client and just using
the defaults.
Even though default.xml in the /aiserver/<svcname> has been modified
to use my local repository instead of pkg.opensolaris.org/release, the
ai_combined_manifest.xml file does not pick up the modifications.
Could you please elaborate more on how you configured install service
and what version of installadm(1m) tools you use on AI server ?
I am asking, since you mention you edited default.xml in
/aiserver/<svcname> directory which does not sound familiar to me,
instead it should be something like
/var/ai/<port_number>/AI_data/default.xml
I had tried creating a manifest file for the client, and this is
obviously what has caused the timezone error.
I did a boot net:dhcp using the default manifest, then edited the
ai_combined_manifest.xml to point to my local repository before I
enabled auto-installer service and the system is booting using the
default.
Note that the default manifest that was loaded onto the booting system
still referenced pkg.opensolaris.org rather than my internal repo. Do
I have to restart pkg/server after modifying default.xml?
Nope, you do not need to restart neither pkg/server (which serves IPS
repository) neither install/server (which serves AI imagest and manifests).
I am still unsure how i go about getting the modified default manifest
to be picked up automatically.
default.xml is located in /var/ai/<port_number>/AI_data/default.xml, where
<port_number> for appropriate install services could be obtained by running
# installadm list -n <install_service>
I also want to use static networking, but I am obviously missing
something, as my attempts to include the static networking template
failed with a "StartTag invalid element name message".
In this case, I might recommend not to edit default.xml directly,
but instead let installadm(1m) syntactically validate it - you could do
something like:
# cp /var/ai/<port_number>/AI_data/default.xml /tmp/
# vi /tmp/default.xml <--- edit what you need, do not change manifest name
# installadm add -m /tmp/default.xml -n <install_service>
Are there any sample client manifests which include the static
networking option?
If you have on your AI server installadm(1m) tools based at least on
build 146,
then sample sc manifest with static network configuration is available at
/usr/share/auto_install/sc_profiles/static_network.xml
Alternatively, it could be downloaded from
http://hub.opensolaris.org/bin/download/Project+caiman/System+Configuration+Project/staticnetwork.xml
You can either keep it as separate file and reference it in AI manifest
or directly embed it in AI manifest.
Previously (b137) I had an ai manifest, an sc manifest and a criteria
manifest which referenced the previous two, but my reading of the new
setup seemed to imply that the sc manifest could be included in the ai
manifest, however, I can't seem to get this to work with b147.
AI manifest as well as the way how criteria could be specified underwent
significant
changes in 147 - see following flag day for more details:
http://hub.opensolaris.org/bin/view/Project+caiman/Pre-Flag+Day+for+bug+16423
That said, SC manifest still could be either included as external file
or directly
embedded into AI manifest.
I am unsure whether I am just confused or whether there has been a
change in the way things work.
Bunch of things have changed in recent couple of builds :-)
Jan
Cheers
Frank
On 09/ 8/10 04:16 PM, Jan Damborsky wrote:
Hi Frank,
On 09/ 8/10 04:10 AM, Frank Allan wrote:
This looks like bug 4629 which was supposed to have been fixed in
March 2009.
Has it resurfaced, or is this something else?
It seems that the issue you are encountering is not related to 4629,
as it is not
seen on all machines (I have successfully installed sun4u machines
with 147).
In order to be able to evaluate what's going on, could you please
rerun the
installer in debug mode ? It is enabled by passing 'install_debug'
from OBP prompt:
{0} ok boot net:dhcp - install install_debug
After the installation fails, could you please log to the machine
(jack/jack)
and attach following files ?
/tmp/ai_combined_manifest.xml
/tmp/sc_manifest.xml
/tmp/install_log
Thank you,
Jan
Cheers
Frank
On 09/ 8/10 10:29 AM, Frank Allan wrote:
I am attempting to use AI with b147 to load a SPARC system (Ultra
45, 6Gb, XVR-300, 4*250Gb disk).
The system is on an internal network with a local repository.
The default manifests have been configured to access the internal
repository.
wanboot works, the system loads the client-specific manifest, finds
the target disk, reports enough physical memory for installation,
then I get:
<AI Sep 8 00:42:07> Parsing system configuration manifest
<AI Sep 8 00:42:07> Detected the latest format of System
Configuration manifest.
<AI Sep 8 00:42:07> Setting of OM_ATTR_TIMEZONE_INFO failed
Automated Installation failed
in the property_group "other_sc_params" I have:
<propval name="timezone" type="astring" value="GMT"/>
any ideas on why I am getting this error, and any way to resolve it?
Cheers
Frank
_______________________________________________
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
