I just tried creating the flar again, using the steps you provided below.  I
left the machine in multiuser mode, and stored the flar in /var/tmp.  When I do
a flar info on this new flar, I still receive the incorrect architecture
information:

root@cmsappt1# flar info ./test.flar
archive_id=2fd87f49d75c7b3dc0a01b46849ff604
files_archived_method=cpio
creation_date=20091113163907
creation_master=cmsappt1
content_name=test.flar
creation_node=cmsappt1
creation_hardware_class=sun4v
creation_platform=SUNW,SPARC-Enterprise-T1000
creation_processor=sparc
creation_release=5.10
creation_os_name=SunOS
creation_os_version=Generic_141444-09
rootpool=rpool
bootfs=rpool/ROOT/sol10u7_stage_2
snapname=zflash.091113.11.11
files_compressed_method=compress
content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
type=FULL


--- In JETJumpStart@yahoogroups.com, Bruce Porter <bdporter@...> wrote:
>
> chanrahan68 wrote:
> >
> >
>
> I've just done an x86 zfs flash install. will do a sun4v soon, however
> my steps differ slightly
>
>
>
> > To create the flar, I did the following:
> >
> > 1. Booted my model machine which is a T1000 with two drives, from c0t0d0s0.
> >
> > 2. Placed the model machine in single user mode
>
> I did not (and have *never*) taken a system to single user before
> running flar.
>
> > 3. Mounted c0t1d0s0 to /mnt. This gives me a place to store the flar
> > 4. Used the command "flarcreate -n s101009sun4v-zfs.flar -c -S
> > /mnt/s101009sun4v-zfs.flar
>
>
> I also always write the flar to /var/tmp (as that is ignored by flar anyway)
>
>
> >
> > I then copied this flar to my jumpstart server and tried to use it to
> > perform an install. Here is the screen output from that attempted install:
> >
>
> How do you copy ? I use scp
>
>
> > Setting up Java. Please wait...
> > Serial console, reverting to text install
> > Beginning system identification...
> > Searching for configuration file(s)...
> > Using sysid configuration file
> > 10.5.204.32:/opt/SUNWjet/Clients/cmsappt1/sysidcfg
> > Search complete.
> > Discovering additional network configuration...
> > Completing system identification...
> > Starting remote procedure call (RPC) services: done.
> > System identification complete.
> > Starting Solaris installation program...
> > Searching for JumpStart directory...
> > Using rules.ok from 10.5.204.32:/opt/SUNWjet.
> > Checking rules.ok file...
> > Using begin script: Utils/begin
> > Using derived profile: Utils/begin
> > Using finish script: Utils/finish
> > Executing JumpStart preinstall phase...
> > Executing begin script "Utils/begin"...
> > Installation of cmsappt1 at 09:20 on 13-Nov-2009
> > Loading JumpStart Server variables
> > Loading Client configuration file
> > BASE_CONFIG: Running base_config begin script....
> > CUSTOM: Running custom begin script....
> > FLASH: Running flash begin script....
> > Begin script Utils/begin execution completed.
> > Searching for SolStart directory...
> > Checking rules.ok file...
> > Using begin script: install_begin
> > Using finish script: patch_finish
> > Executing SolStart preinstall phase...
> > Executing begin script "install_begin"...
> > Begin script install_begin execution completed.
> > WARNING: Flash install: Pool name <rpool> specified in profile will be
> > ignored
> >
> > Processing default locales
> > - Specifying default locale (en_US.UTF-8)
> >
> > Processing profile
> > - Saving Boot Environment Configuration
> > - Opening Flash archive
> > - Validating Flash archive
> >
> > ERROR: Archive does not support this architecture (sun4v)
>
> This is not a JET issue, it is a flar issue
>
> >
> > ERROR: Flash installation failed
> > Solaris installation program exited.
> >
> > --- In JETJumpStart@yahoogroups.com
> > <mailto:JETJumpStart%40yahoogroups.com>, Bruce <bdporter@> wrote:
> >  >
> >  > Michael Ramchand wrote:
> >  > >
> >  > >
> >  > > Could you explain where this error occurs?
> >  > >
> >  > >
> >  > > I've created zfs root flars of S10 U8 and deployed them with no issues.
> >  > >
> >  > > At what stage do you see the error?
> >  > >
> >  > > What is the O/S version of the flar?
> >  >
> >  > And command used to create the flar
> >  >
> >  > >
> >  > > Mike
> >  > > On 12 Nov 2009, at 22:06, chanrahan68 wrote:
> >  > >
> >  > >>
> >  > >>
> >  > >> Greetings,
> >  > >>
> >  > >> I'm attempting to perform a Jumpstart install (using JET 4.7) using a
> >  > >> flar created of a T1000 running Solaris 10 U8 which boots via ZFS.
> >  > >>
> >  > >> The jumpstart install fails because the content_architectures
> > field of
> >  > >> the flar image does not contain "sun4v" even though the flar was
> >  > >> created on a T1000, which is a sun4v platform.
> >  > >>
> >  > >> The server that I am trying to jump is also a T1000, so this should
> >  > >> all work just fine.
> >  > >>
> >  > >> Here is the output of flar info for my flar:
> >  > >>
> >  > >> flar info s101009sun4v-zfs.flar
> >  > >> archive_id=f7777c2130634bc713573345f710c799
> >  > >> files_archived_method=cpio
> >  > >> creation_date=20091112212629
> >  > >> creation_master=cmsappt1
> >  > >> content_name=s101009sun4v-zfs.flar
> >  > >> creation_node=cmsappt1
> >  > >> creation_hardware_class=sun4v
> >  > >> creation_platform=SUNW,SPARC-Enterprise-T1000
> >  > >> creation_processor=sparc
> >  > >> creation_release=5.10
> >  > >> creation_os_name=SunOS
> >  > >> creation_os_version=Generic_141444-09
> >  > >> rootpool=rpool
> >  > >> bootfs=rpool/ROOT/sol10u7_stage_2
> >  > >> snapname=zflash.091112.16.11
> >  > >> files_compressed_method=compress
> >  > >> content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
> >  > >> type=FULL
> >  > >>
> >  > >> Is there something special that I have to do when creating a flar
> > of a
> >  > >> ZFS bootable server in order to make this work?
> >  > >>
> >  > >> Thanks in advance..
> >  > >>
> >  > >
> >  > > ---
> >  > > Mike Ramchand
> >  > > Principal Field Technologist
> >  > > Enterprise Technical Specialist
> >  > > Sun Microsystems (UK)
> >  > > Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
> >  > >
> >  > >
> >  > >
> >  >
> >  >
> >  > --
> >  >
> >  > Bruce D Porter
> >  > Technical Consultant
> >  > YTC Systems LTD
> >  >
> >  > "The internet is a huge and diverse community and not every one is
> >  > friendly"
> >  > http://www.ytc1.co.uk <http://www.ytc1.co.uk>
> >  >
> >
> >
>
>
> --
>
> Bruce D Porter
> Technical Consultant
> YTC Systems LTD
>
> "The internet is a huge and diverse community and not every one is
> friendly"
> http://www.ytc1.co.uk
>

* Marty Lee <marty@...> wrote:
> Solaris JumpStart has 'issues' with FQHNs; as JET lives on top of JumpStart,
> even if you get past the issues you've already seen, there are others you are
> likely to encounter.
>
> As such, we (Mike and I) chose to only use unqualified host names in JET in
> order to keep things working across the board.
>
> If you really need a FQHN then use a custom script or your own module to
> set the FQHN during the build. At that point, if anything then breaks, you
> have a good idea that it was your own module/script that caused it......

Good to know, thanks for the background information!

Sebastian

Solaris JumpStart has 'issues' with FQHNs; as JET lives on top of JumpStart,
even if you get past the issues you've already seen, there are others you are
likely to encounter.

As such, we (Mike and I) chose to only use unqualified host names in JET in
order to keep things working across the board.

If you really need a FQHN then use a custom script or your own module to
set the FQHN during the build. At that point, if anything then breaks, you
have a good idea that it was your own module/script that caused it......

(can you tell we've been here before ? Your mileage may vary, stocks can go
up as well as down, etc etc...)

cheers

m

On 13 Nov 2009, at 16:15, Sebastian Kayser wrote:

> Hi,
>
> we are using JET 4.7 and have been working with unqualified hostnames as
> template filenames so far. Lately that caused us some headaches as JET
> inserts the unqualified hostname into /etc/hosts and some of our NFS
> share permissions are based on our DNS domain.
>
> Thus i have switched to a fully qualified template name (for testing
> purposes), but JET seems to look for the profile in an unqualified path.
> Should i just revert to unqualified template names and adjust /etc/hosts
> (or the script which changes the hosts file) or is this a defect in JET
> that could be fixed?
>
> ,----
> | ...
> | Searching for configuration file(s)...
> | Using sysid configuration file
> | 10.5.0.4:/opt/SUNWjet/Clients/ray3.roc.consol.de/sysidcfg
> | Search complete.
> | Discovering additional network configuration...
> | Completing system identification...
> | Starting remote procedure call (RPC) services: done.
> | NIS domain name is roc.consol.de
> | System identification complete.
> | Starting Solaris installation program...
> | Searching for JumpStart directory...
> | Using rules.ok from 10.5.0.4:/opt/SUNWjet.
> | Checking rules.ok file...
> | Using begin script: Utils/begin
> | Using derived profile: Utils/begin
> | Using finish script: Utils/finish
> | Executing JumpStart preinstall phase...
> | Executing begin script "Utils/begin"...
> | cat: cannot open /tmp/install_config/Clients/ray3/profile
> | Installation of ray3 at 16:59 on 13-Nov-2009
> | Loading JumpStart Server variables
> | Unable to locate host specific variables
> | Exiting ...
> | Begin script Utils/begin failed with return value "1".
> | Aborting install.
> | # ls -d /tmp/install_config/Clients/ray3*
> | /tmp/install_config/Clients/ray3.roc.consol.de
> `----
>
> Sebastian
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

-----
Marty Lee                         e: marty@...
Technical Director                v: +44 845 869 2661
Maui Systems Ltd                  f: +44 871 433 8922
Scotland, UK                      w: http://www.maui-systems.co.uk

Sebastian Kayser wrote:
> Hi,
>
> we are using JET 4.7 and have been working with unqualified hostnames as
> template filenames so far. Lately that caused us some headaches as JET
> inserts the unqualified hostname into /etc/hosts and some of our NFS
> share permissions are based on our DNS domain.
>
> Thus i have switched to a fully qualified template name (for testing
> purposes), but JET seems to look for the profile in an unqualified path.
> Should i just revert to unqualified template names and adjust /etc/hosts
> (or the script which changes the hosts file) or is this a defect in JET
> that could be fixed?

JET does not sit happily with FQHN templates, there should be some
history of discussions on the alias. (the name serveice may not be
running/accessible during build)

Set the fully qualified name in the host file, post build using the
custom module

>
> ,----
> | ...
> | Searching for configuration file(s)...
> | Using sysid configuration file
> | 10.5.0.4:/opt/SUNWjet/Clients/ray3.roc.consol.de/sysidcfg
> | Search complete.
> | Discovering additional network configuration...
> | Completing system identification...
> | Starting remote procedure call (RPC) services: done.
> | NIS domain name is roc.consol.de
> | System identification complete.
> | Starting Solaris installation program...
> | Searching for JumpStart directory...
> | Using rules.ok from 10.5.0.4:/opt/SUNWjet.
> | Checking rules.ok file...
> | Using begin script: Utils/begin
> | Using derived profile: Utils/begin
> | Using finish script: Utils/finish
> | Executing JumpStart preinstall phase...
> | Executing begin script "Utils/begin"...
> | cat: cannot open /tmp/install_config/Clients/ray3/profile
> | Installation of ray3 at 16:59 on 13-Nov-2009
> | Loading JumpStart Server variables
> | Unable to locate host specific variables
> | Exiting ...
> | Begin script Utils/begin failed with return value "1".
> | Aborting install.
> | # ls -d /tmp/install_config/Clients/ray3*
> | /tmp/install_config/Clients/ray3.roc.consol.de
> `----
>
> Sebastian
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


--

Bruce D Porter
Technical Consultant
YTC Systems LTD

"The internet is a huge and diverse community and not every one is
friendly"
http://www.ytc1.co.uk

Hi,

we are using JET 4.7 and have been working with unqualified hostnames as
template filenames so far. Lately that caused us some headaches as JET
inserts the unqualified hostname into /etc/hosts and some of our NFS
share permissions are based on our DNS domain.

Thus i have switched to a fully qualified template name (for testing
purposes), but JET seems to look for the profile in an unqualified path.
Should i just revert to unqualified template names and adjust /etc/hosts
(or the script which changes the hosts file) or is this a defect in JET
that could be fixed?

,----
| ...
| Searching for configuration file(s)...
| Using sysid configuration file
| 10.5.0.4:/opt/SUNWjet/Clients/ray3.roc.consol.de/sysidcfg
| Search complete.
| Discovering additional network configuration...
| Completing system identification...
| Starting remote procedure call (RPC) services: done.
| NIS domain name is roc.consol.de
| System identification complete.
| Starting Solaris installation program...
| Searching for JumpStart directory...
| Using rules.ok from 10.5.0.4:/opt/SUNWjet.
| Checking rules.ok file...
| Using begin script: Utils/begin
| Using derived profile: Utils/begin
| Using finish script: Utils/finish
| Executing JumpStart preinstall phase...
| Executing begin script "Utils/begin"...
| cat: cannot open /tmp/install_config/Clients/ray3/profile
| Installation of ray3 at 16:59 on 13-Nov-2009
| Loading JumpStart Server variables
| Unable to locate host specific variables
| Exiting ...
| Begin script Utils/begin failed with return value "1".
| Aborting install.
| # ls -d /tmp/install_config/Clients/ray3*
| /tmp/install_config/Clients/ray3.roc.consol.de
`----

Sebastian

chanrahan68 wrote:
>
>

I've just done an x86 zfs flash install. will do a sun4v soon, however
my steps differ slightly



> To create the flar, I did the following:
>
> 1. Booted my model machine which is a T1000 with two drives, from c0t0d0s0.
>
> 2. Placed the model machine in single user mode

I did not (and have *never*) taken a system to single user before
running flar.

> 3. Mounted c0t1d0s0 to /mnt. This gives me a place to store the flar
> 4. Used the command "flarcreate -n s101009sun4v-zfs.flar -c -S
> /mnt/s101009sun4v-zfs.flar


I also always write the flar to /var/tmp (as that is ignored by flar anyway)


>
> I then copied this flar to my jumpstart server and tried to use it to
> perform an install. Here is the screen output from that attempted install:
>

How do you copy ? I use scp


> Setting up Java. Please wait...
> Serial console, reverting to text install
> Beginning system identification...
> Searching for configuration file(s)...
> Using sysid configuration file
> 10.5.204.32:/opt/SUNWjet/Clients/cmsappt1/sysidcfg
> Search complete.
> Discovering additional network configuration...
> Completing system identification...
> Starting remote procedure call (RPC) services: done.
> System identification complete.
> Starting Solaris installation program...
> Searching for JumpStart directory...
> Using rules.ok from 10.5.204.32:/opt/SUNWjet.
> Checking rules.ok file...
> Using begin script: Utils/begin
> Using derived profile: Utils/begin
> Using finish script: Utils/finish
> Executing JumpStart preinstall phase...
> Executing begin script "Utils/begin"...
> Installation of cmsappt1 at 09:20 on 13-Nov-2009
> Loading JumpStart Server variables
> Loading Client configuration file
> BASE_CONFIG: Running base_config begin script....
> CUSTOM: Running custom begin script....
> FLASH: Running flash begin script....
> Begin script Utils/begin execution completed.
> Searching for SolStart directory...
> Checking rules.ok file...
> Using begin script: install_begin
> Using finish script: patch_finish
> Executing SolStart preinstall phase...
> Executing begin script "install_begin"...
> Begin script install_begin execution completed.
> WARNING: Flash install: Pool name <rpool> specified in profile will be
> ignored
>
> Processing default locales
> - Specifying default locale (en_US.UTF-8)
>
> Processing profile
> - Saving Boot Environment Configuration
> - Opening Flash archive
> - Validating Flash archive
>
> ERROR: Archive does not support this architecture (sun4v)

This is not a JET issue, it is a flar issue

>
> ERROR: Flash installation failed
> Solaris installation program exited.
>
> --- In JETJumpStart@yahoogroups.com
> <mailto:JETJumpStart%40yahoogroups.com>, Bruce <bdporter@...> wrote:
>  >
>  > Michael Ramchand wrote:
>  > >
>  > >
>  > > Could you explain where this error occurs?
>  > >
>  > >
>  > > I've created zfs root flars of S10 U8 and deployed them with no issues.
>  > >
>  > > At what stage do you see the error?
>  > >
>  > > What is the O/S version of the flar?
>  >
>  > And command used to create the flar
>  >
>  > >
>  > > Mike
>  > > On 12 Nov 2009, at 22:06, chanrahan68 wrote:
>  > >
>  > >>
>  > >>
>  > >> Greetings,
>  > >>
>  > >> I'm attempting to perform a Jumpstart install (using JET 4.7) using a
>  > >> flar created of a T1000 running Solaris 10 U8 which boots via ZFS.
>  > >>
>  > >> The jumpstart install fails because the content_architectures
> field of
>  > >> the flar image does not contain "sun4v" even though the flar was
>  > >> created on a T1000, which is a sun4v platform.
>  > >>
>  > >> The server that I am trying to jump is also a T1000, so this should
>  > >> all work just fine.
>  > >>
>  > >> Here is the output of flar info for my flar:
>  > >>
>  > >> flar info s101009sun4v-zfs.flar
>  > >> archive_id=f7777c2130634bc713573345f710c799
>  > >> files_archived_method=cpio
>  > >> creation_date=20091112212629
>  > >> creation_master=cmsappt1
>  > >> content_name=s101009sun4v-zfs.flar
>  > >> creation_node=cmsappt1
>  > >> creation_hardware_class=sun4v
>  > >> creation_platform=SUNW,SPARC-Enterprise-T1000
>  > >> creation_processor=sparc
>  > >> creation_release=5.10
>  > >> creation_os_name=SunOS
>  > >> creation_os_version=Generic_141444-09
>  > >> rootpool=rpool
>  > >> bootfs=rpool/ROOT/sol10u7_stage_2
>  > >> snapname=zflash.091112.16.11
>  > >> files_compressed_method=compress
>  > >> content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
>  > >> type=FULL
>  > >>
>  > >> Is there something special that I have to do when creating a flar
> of a
>  > >> ZFS bootable server in order to make this work?
>  > >>
>  > >> Thanks in advance..
>  > >>
>  > >
>  > > ---
>  > > Mike Ramchand
>  > > Principal Field Technologist
>  > > Enterprise Technical Specialist
>  > > Sun Microsystems (UK)
>  > > Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
>  > >
>  > >
>  > >
>  >
>  >
>  > --
>  >
>  > Bruce D Porter
>  > Technical Consultant
>  > YTC Systems LTD
>  >
>  > "The internet is a huge and diverse community and not every one is
>  > friendly"
>  > http://www.ytc1.co.uk <http://www.ytc1.co.uk>
>  >
>
>


--

Bruce D Porter
Technical Consultant
YTC Systems LTD

"The internet is a huge and diverse community and not every one is
friendly"
http://www.ytc1.co.uk

To create the flar, I did the following:

1.  Booted my model machine which is a T1000 with two drives, from c0t0d0s0.

2.  Placed the model machine in single user mode
3.  Mounted c0t1d0s0 to /mnt.  This gives me a place to store the flar
4.  Used the command "flarcreate -n s101009sun4v-zfs.flar -c -S
/mnt/s101009sun4v-zfs.flar

I then copied this flar to my jumpstart server and tried to use it to perform an
install.  Here is the screen output from that attempted install:

Setting up Java. Please wait...
Serial console, reverting to text install
Beginning system identification...
Searching for configuration file(s)...
Using sysid configuration file
10.5.204.32:/opt/SUNWjet/Clients/cmsappt1/sysidcfg
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services: done.
System identification complete.
Starting Solaris installation program...
Searching for JumpStart directory...
Using rules.ok from 10.5.204.32:/opt/SUNWjet.
Checking rules.ok file...
Using begin script: Utils/begin
Using derived profile: Utils/begin
Using finish script: Utils/finish
Executing JumpStart preinstall phase...
Executing begin script "Utils/begin"...
Installation of cmsappt1 at 09:20 on 13-Nov-2009
Loading JumpStart Server variables
Loading Client configuration file
BASE_CONFIG: Running base_config begin script....
CUSTOM: Running custom begin script....
FLASH: Running flash begin script....
Begin script Utils/begin execution completed.
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.
WARNING: Flash install: Pool name <rpool> specified in profile will be ignored

Processing default locales
         - Specifying default locale (en_US.UTF-8)

Processing profile
         - Saving Boot Environment Configuration
         - Opening Flash archive
         - Validating Flash archive

ERROR: Archive does not support this architecture (sun4v)

ERROR: Flash installation failed
Solaris installation program exited.


--- In JETJumpStart@yahoogroups.com, Bruce <bdporter@...> wrote:
>
> Michael Ramchand wrote:
> >
> >
> > Could you explain where this error occurs?
> >
> >
> > I've created zfs root flars of S10 U8 and deployed them with no issues.
> >
> > At what stage do you see the error?
> >
> > What is the O/S version of the flar?
>
> And command used to create the flar
>
> >
> > Mike
> > On 12 Nov 2009, at 22:06, chanrahan68 wrote:
> >
> >>
> >>
> >> Greetings,
> >>
> >> I'm attempting to perform a Jumpstart install (using JET 4.7) using a
> >> flar created of a T1000 running Solaris 10 U8 which boots via ZFS.
> >>
> >> The jumpstart install fails because the content_architectures field of
> >> the flar image does not contain "sun4v" even though the flar was
> >> created on a T1000, which is a sun4v platform.
> >>
> >> The server that I am trying to jump is also a T1000, so this should
> >> all work just fine.
> >>
> >> Here is the output of flar info for my flar:
> >>
> >> flar info s101009sun4v-zfs.flar
> >> archive_id=f7777c2130634bc713573345f710c799
> >> files_archived_method=cpio
> >> creation_date=20091112212629
> >> creation_master=cmsappt1
> >> content_name=s101009sun4v-zfs.flar
> >> creation_node=cmsappt1
> >> creation_hardware_class=sun4v
> >> creation_platform=SUNW,SPARC-Enterprise-T1000
> >> creation_processor=sparc
> >> creation_release=5.10
> >> creation_os_name=SunOS
> >> creation_os_version=Generic_141444-09
> >> rootpool=rpool
> >> bootfs=rpool/ROOT/sol10u7_stage_2
> >> snapname=zflash.091112.16.11
> >> files_compressed_method=compress
> >> content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
> >> type=FULL
> >>
> >> Is there something special that I have to do when creating a flar of a
> >> ZFS bootable server in order to make this work?
> >>
> >> Thanks in advance..
> >>
> >
> > ---
> > Mike Ramchand
> > Principal Field Technologist
> > Enterprise Technical Specialist
> > Sun Microsystems (UK)
> > Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
> >
> >
> >
>
>
> --
>
> Bruce D Porter
> Technical Consultant
> YTC Systems LTD
>
> "The internet is a huge and diverse community and not every one is
> friendly"
> http://www.ytc1.co.uk
>

Hello,

The OS version of the flar is Solaris 10 U8.

Here is the screen output from my attempted jumpstart:

Setting up Java. Please wait...
Serial console, reverting to text install
Beginning system identification...
Searching for configuration file(s)...
Using sysid configuration file
10.5.204.32:/opt/SUNWjet/Clients/cmsappt1/sysidcfg
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services: done.
System identification complete.
Starting Solaris installation program...
Searching for JumpStart directory...
Using rules.ok from 10.5.204.32:/opt/SUNWjet.
Checking rules.ok file...
Using begin script: Utils/begin
Using derived profile: Utils/begin
Using finish script: Utils/finish
Executing JumpStart preinstall phase...
Executing begin script "Utils/begin"...
Installation of cmsappt1 at 09:20 on 13-Nov-2009
Loading JumpStart Server variables
Loading Client configuration file
BASE_CONFIG: Running base_config begin script....
CUSTOM: Running custom begin script....
FLASH: Running flash begin script....
Begin script Utils/begin execution completed.
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.
WARNING: Flash install: Pool name <rpool> specified in profile will be ignored

Processing default locales
         - Specifying default locale (en_US.UTF-8)

Processing profile
         - Saving Boot Environment Configuration
         - Opening Flash archive
         - Validating Flash archive

ERROR: Archive does not support this architecture (sun4v)

ERROR: Flash installation failed
Solaris installation program exited.


--- In JETJumpStart@yahoogroups.com, Michael Ramchand <mike.ramchand@...> wrote:
>
> Could you explain where this error occurs?
>
> I've created zfs root flars of S10 U8 and deployed them with no issues.
>
> At what stage do you see the error?
>
> What is the O/S version of the flar?
>
> Mike
> On 12 Nov 2009, at 22:06, chanrahan68 wrote:
>
> > Greetings,
> >
> > I'm attempting to perform a Jumpstart install (using JET 4.7) using
> > a flar created of a T1000 running Solaris 10 U8 which boots via ZFS.
> >
> > The jumpstart install fails because the content_architectures field
> > of the flar image does not contain "sun4v" even though the flar was
> > created on a T1000, which is a sun4v platform.
> >
> > The server that I am trying to jump is also a T1000, so this should
> > all work just fine.
> >
> > Here is the output of flar info for my flar:
> >
> > flar info s101009sun4v-zfs.flar
> > archive_id=f7777c2130634bc713573345f710c799
> > files_archived_method=cpio
> > creation_date=20091112212629
> > creation_master=cmsappt1
> > content_name=s101009sun4v-zfs.flar
> > creation_node=cmsappt1
> > creation_hardware_class=sun4v
> > creation_platform=SUNW,SPARC-Enterprise-T1000
> > creation_processor=sparc
> > creation_release=5.10
> > creation_os_name=SunOS
> > creation_os_version=Generic_141444-09
> > rootpool=rpool
> > bootfs=rpool/ROOT/sol10u7_stage_2
> > snapname=zflash.091112.16.11
> > files_compressed_method=compress
> > content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
> > type=FULL
> >
> > Is there something special that I have to do when creating a flar of
> > a ZFS bootable server in order to make this work?
> >
> > Thanks in advance..
> >
> >
>
> ---
> Mike Ramchand
> Principal Field Technologist
> Enterprise Technical Specialist
> Sun Microsystems (UK)
> Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
>

Michael Ramchand wrote:
>
>
> Could you explain where this error occurs?
>
>
> I've created zfs root flars of S10 U8 and deployed them with no issues.
>
> At what stage do you see the error?
>
> What is the O/S version of the flar?

And command used to create the flar

>
> Mike
> On 12 Nov 2009, at 22:06, chanrahan68 wrote:
>
>>
>>
>> Greetings,
>>
>> I'm attempting to perform a Jumpstart install (using JET 4.7) using a
>> flar created of a T1000 running Solaris 10 U8 which boots via ZFS.
>>
>> The jumpstart install fails because the content_architectures field of
>> the flar image does not contain "sun4v" even though the flar was
>> created on a T1000, which is a sun4v platform.
>>
>> The server that I am trying to jump is also a T1000, so this should
>> all work just fine.
>>
>> Here is the output of flar info for my flar:
>>
>> flar info s101009sun4v-zfs.flar
>> archive_id=f7777c2130634bc713573345f710c799
>> files_archived_method=cpio
>> creation_date=20091112212629
>> creation_master=cmsappt1
>> content_name=s101009sun4v-zfs.flar
>> creation_node=cmsappt1
>> creation_hardware_class=sun4v
>> creation_platform=SUNW,SPARC-Enterprise-T1000
>> creation_processor=sparc
>> creation_release=5.10
>> creation_os_name=SunOS
>> creation_os_version=Generic_141444-09
>> rootpool=rpool
>> bootfs=rpool/ROOT/sol10u7_stage_2
>> snapname=zflash.091112.16.11
>> files_compressed_method=compress
>> content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
>> type=FULL
>>
>> Is there something special that I have to do when creating a flar of a
>> ZFS bootable server in order to make this work?
>>
>> Thanks in advance..
>>
>
> ---
> Mike Ramchand
> Principal Field Technologist
> Enterprise Technical Specialist
> Sun Microsystems (UK)
> Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
>
>
>


--

Bruce D Porter
Technical Consultant
YTC Systems LTD

"The internet is a huge and diverse community and not every one is
friendly"
http://www.ytc1.co.uk

Greetings,

I'm attempting to perform a Jumpstart install (using JET 4.7) using a flar
created of a T1000 running Solaris 10 U8 which boots via ZFS.

The jumpstart install fails because the content_architectures field of the flar
image does not contain "sun4v" even though the flar was created on a T1000,
which is a sun4v platform.

The server that I am trying to jump is also a T1000, so this should all work
just fine.

Here is the output of flar info for my flar:

flar info s101009sun4v-zfs.flar
archive_id=f7777c2130634bc713573345f710c799
files_archived_method=cpio
creation_date=20091112212629
creation_master=cmsappt1
content_name=s101009sun4v-zfs.flar
creation_node=cmsappt1
creation_hardware_class=sun4v
creation_platform=SUNW,SPARC-Enterprise-T1000
creation_processor=sparc
creation_release=5.10
creation_os_name=SunOS
creation_os_version=Generic_141444-09
rootpool=rpool
bootfs=rpool/ROOT/sol10u7_stage_2
snapname=zflash.091112.16.11
files_compressed_method=compress
content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
type=FULL

Is there something special that I have to do when creating a flar of a ZFS
bootable server in order to make this work?

Thanks in advance..

On Thu, Nov 12, 2009 at 02:10:23PM +0000, Michael Ramchand wrote:
> (But I agree, it needs to be done properly, and the way I would do it is to
> mimic the standard solaris base_config_shutup_sendmail variable, and remove
> the appending to the /etc/hosts fiel code altogether from the install
> script.)

I think the zones/jetzone script ought to be calling JS_add_host,
and if that needs a modification to support the "IP + multiple hostnames"
then it should get it.

James.

Im sorry Marty, email can so kill the emotion of meaning that its very easy to
misinterpret the meaning of the author.

However the email was more about the code and what it was or was not doing
rather than the hard work that you guys have put into it.

Likewise ive just struggled through three days of trying to get this working and
have shared what i have found.

it works right now for me , and sure a more elegant solution can be developed
from that.

regards peter

--- In JETJumpStart@yahoogroups.com, Marty Lee <marty@...> wrote:
>
>
> Using resolv.conf to find the domain name is unreliable - I've seen a number
of
> production servers where their true FQDN is not just a case of appending the
> hostname with the 'domain' line in /etc/resolv.conf : even less where I can
say
> the 'search' line could be used - that truly does look like a disaster waiting
to
> happen.
>
> I would prefer to use a distinct variable within JET to identify the FQDN and
> get the installer to define it directly. It could then be used to populate a
> resolv.conf file if no other details were given, but not necessarily the other
> way around.
>
> As kerberos isn't widely used in the customers I've ever used JET with (like 0
> out of all the years I've been involved), I can understand why this has never
> really been a problem before.
>
> As a side note - you might want to consider some of the phrases you use when
> posting comments here; JET was put out to the community to help people and
> this alias is normally supportive of that effort. Comments such as '...no
attempt
> was ever made....' is verging on the disrespectful and likely to make people
> less willing to come forward and help.... Just my opinion.
>
> m
>
>
> On 12 Nov 2009, at 13:12, ossiltd wrote:
>
> > looking at the code now it appears that no attempt was ever made to obtain
the FQDM instead just setting it to hostname. three times through the zone
install process.
> >
> > so using some of your own code from JS_remove_host
> >
> > ive done the following to the install script and this works.
> >
> > and if you have a resolv.conf it attempts to get the domain or first search
item and set the FQDN with it in the hosts file as is required for things like
kerberos to function correctly.
> >
> > im not suggesting its 100% bug free for every installation but it works
here. It will need testing evaluating to ensure it does not have any unintended
side effects.
> >
> > regards peter
> >
> > productdir="`cd ${0%/*}/..; pwd`"
> > if [ -f ${ROOTDIR}/etc/resolv.conf ]
> > then
> > DOMAIN=`grep domain ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
> > if [ "${DOMAIN}X" = "X" ]
> > then
> > #domain not set use serach instead
> > DOMAIN=`grep search ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
> > fi
> > fi
> > FQDN=`grep ${HOST}.${DOMAIN} ${ROOTDIR}/etc/inet/hosts`
> > #prevent re-entrant"
> > if [ "${FQDN}XXX" = "XXX" ]
> > then
> > cputype="`uname -p`"
> > cat ${ROOTDIR}/etc/inet/hosts|nawk '$1 ~ "^#" { print $0; };
> > $1 !~ "^#" { hostline=""; for(i=2; i<=NF;i++) {
> > if($i != "'"${HOST}"'" && $i != "'"${HOST}"'." && $i != "loghost") {
hostline=hostline" "$i};
> > };
> > if(hostline != "") { print $1"\t"hostline; }
> > }' > /tmp/newhosts.$$
> > mv /tmp/newhosts.$$ ${ROOTDIR}/etc/inet/hosts
> >
> > echo "Add hosts entry for FQDN and UQHN"
> > echo "${base_config_sysidcfg_ip_address}" "${HOST}.${DOMAIN}" "${HOST}"
loghost \
> > >> ${ROOTDIR}/etc/inet/hosts
> > fi
> >
> > if [ -x "${productdir}/solaris/install" ]; then
> > ( cd ${productdir} ; ./solaris/install)
> > else
> > echo "Unable to locate solaris install script"
> > fi
> >
> > /opt/SUNWjet/Products/base_config/solariszone/install
> >
> >
>
> -----
> Marty Lee                         e: marty@...
> Technical Director                v: +44 845 869 2661
> Maui Systems Ltd                  f: +44 871 433 8922
> Scotland, UK                      w: http://www.maui-systems.co.uk
>

>
> Using resolv.conf to find the domain name is unreliable - I've seen a
> number of
> production servers where their true FQDN is not just a case of appending
> the
> hostname with the 'domain' line in /etc/resolv.conf : even less where I
> can say
> the 'search' line could be used - that truly does look like a disaster
> waiting to
> happen.
>
> I would prefer to use a distinct variable within JET to identify the FQDN
> and
> get the installer to define it directly. It could then be used to populate
> a
> resolv.conf file if no other details were given, but not necessarily the
> other
> way around.

+1

>
> As kerberos isn't widely used in the customers I've ever used JET with
> (like 0
> out of all the years I've been involved), I can understand why this has
> never
> really been a problem before.
>
> As a side note - you might want to consider some of the phrases you use
> when
> posting comments here; JET was put out to the community to help people and
> this alias is normally supportive of that effort. Comments such as '...no
> attempt
> was ever made....' is verging on the disrespectful and likely to make
> people
> less willing to come forward and help.... Just my opinion.

+1 :-)

>
> m
>
>
> On 12 Nov 2009, at 13:12, ossiltd wrote:
>
>> looking at the code now it appears that no attempt was ever made to
>> obtain the FQDM instead just setting it to hostname. three times through
>> the zone install process.
>>
>> so using some of your own code from JS_remove_host
>>
>> ive done the following to the install script and this works.
>>
>> and if you have a resolv.conf it attempts to get the domain or first
>> search item and set the FQDN with it in the hosts file as is required
>> for things like kerberos to function correctly.
>>
>> im not suggesting its 100% bug free for every installation but it works
>> here. It will need testing evaluating to ensure it does not have any
>> unintended side effects.
>>
>> regards peter
>>
>> productdir="`cd ${0%/*}/..; pwd`"
>> if [ -f ${ROOTDIR}/etc/resolv.conf ]
>> then
>> DOMAIN=`grep domain ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
>> if [ "${DOMAIN}X" = "X" ]
>> then
>> #domain not set use serach instead
>> DOMAIN=`grep search ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
>> fi
>> fi
>> FQDN=`grep ${HOST}.${DOMAIN} ${ROOTDIR}/etc/inet/hosts`
>> #prevent re-entrant"
>> if [ "${FQDN}XXX" = "XXX" ]
>> then
>> cputype="`uname -p`"
>> cat ${ROOTDIR}/etc/inet/hosts|nawk '$1 ~ "^#" { print $0; };
>> $1 !~ "^#" { hostline=""; for(i=2; i<=NF;i++) {
>> if($i != "'"${HOST}"'" && $i != "'"${HOST}"'." && $i != "loghost") {
>> hostline=hostline" "$i};
>> };
>> if(hostline != "") { print $1"\t"hostline; }
>> }' > /tmp/newhosts.$$
>> mv /tmp/newhosts.$$ ${ROOTDIR}/etc/inet/hosts
>>
>> echo "Add hosts entry for FQDN and UQHN"
>> echo "${base_config_sysidcfg_ip_address}" "${HOST}.${DOMAIN}" "${HOST}"
>> loghost \
>> >> ${ROOTDIR}/etc/inet/hosts
>> fi
>>
>> if [ -x "${productdir}/solaris/install" ]; then
>> ( cd ${productdir} ; ./solaris/install)
>> else
>> echo "Unable to locate solaris install script"
>> fi
>>
>> /opt/SUNWjet/Products/base_config/solariszone/install
>>
>>
>
> -----
> Marty Lee                         e: marty@...
> Technical Director                v: +44 845 869 2661
> Maui Systems Ltd                  f: +44 871 433 8922
> Scotland, UK                      w: http://www.maui-systems.co.uk
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>


--
Bruce Porter

Using resolv.conf to find the domain name is unreliable - I've seen a number of
production servers where their true FQDN is not just a case of appending the
hostname with the 'domain' line in /etc/resolv.conf : even less where I can say
the 'search' line could be used - that truly does look like a disaster waiting
to
happen.

I would prefer to use a distinct variable within JET to identify the FQDN and
get the installer to define it directly. It could then be used to populate a
resolv.conf file if no other details were given, but not necessarily the other
way around.

As kerberos isn't widely used in the customers I've ever used JET with (like 0
out of all the years I've been involved), I can understand why this has never
really been a problem before.

As a side note - you might want to consider some of the phrases you use when
posting comments here; JET was put out to the community to help people and
this alias is normally supportive of that effort. Comments such as '...no
attempt
was ever made....' is verging on the disrespectful and likely to make people
less willing to come forward and help.... Just my opinion.

m


On 12 Nov 2009, at 13:12, ossiltd wrote:

> looking at the code now it appears that no attempt was ever made to obtain the
FQDM instead just setting it to hostname. three times through the zone install
process.
>
> so using some of your own code from JS_remove_host
>
> ive done the following to the install script and this works.
>
> and if you have a resolv.conf it attempts to get the domain or first search
item and set the FQDN with it in the hosts file as is required for things like
kerberos to function correctly.
>
> im not suggesting its 100% bug free for every installation but it works here.
It will need testing evaluating to ensure it does not have any unintended side
effects.
>
> regards peter
>
> productdir="`cd ${0%/*}/..; pwd`"
> if [ -f ${ROOTDIR}/etc/resolv.conf ]
> then
> DOMAIN=`grep domain ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
> if [ "${DOMAIN}X" = "X" ]
> then
> #domain not set use serach instead
> DOMAIN=`grep search ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
> fi
> fi
> FQDN=`grep ${HOST}.${DOMAIN} ${ROOTDIR}/etc/inet/hosts`
> #prevent re-entrant"
> if [ "${FQDN}XXX" = "XXX" ]
> then
> cputype="`uname -p`"
> cat ${ROOTDIR}/etc/inet/hosts|nawk '$1 ~ "^#" { print $0; };
> $1 !~ "^#" { hostline=""; for(i=2; i<=NF;i++) {
> if($i != "'"${HOST}"'" && $i != "'"${HOST}"'." && $i != "loghost") {
hostline=hostline" "$i};
> };
> if(hostline != "") { print $1"\t"hostline; }
> }' > /tmp/newhosts.$$
> mv /tmp/newhosts.$$ ${ROOTDIR}/etc/inet/hosts
>
> echo "Add hosts entry for FQDN and UQHN"
> echo "${base_config_sysidcfg_ip_address}" "${HOST}.${DOMAIN}" "${HOST}"
loghost \
> >> ${ROOTDIR}/etc/inet/hosts
> fi
>
> if [ -x "${productdir}/solaris/install" ]; then
> ( cd ${productdir} ; ./solaris/install)
> else
> echo "Unable to locate solaris install script"
> fi
>
> /opt/SUNWjet/Products/base_config/solariszone/install
>
>

-----
Marty Lee                         e: marty@...
Technical Director                v: +44 845 869 2661
Maui Systems Ltd                  f: +44 871 433 8922
Scotland, UK                      w: http://www.maui-systems.co.uk

looking at the code now it appears that no attempt was ever made to obtain the
FQDM instead just setting it to hostname. three times through the zone install
process.

so using some of your own code from JS_remove_host

ive done the following to the install script and this works.

and if you have a resolv.conf it attempts to get the domain or first search item
and set the FQDN with it in the hosts file as is required for things like
kerberos to function correctly.

im not suggesting its 100% bug free for every installation but it works here. It
will need testing evaluating to ensure it does not have any unintended side
effects.

regards peter


productdir="`cd ${0%/*}/..; pwd`"
if [ -f ${ROOTDIR}/etc/resolv.conf ]
then
DOMAIN=`grep domain ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
         if [ "${DOMAIN}X" = "X" ]
         then
         #domain not set use serach instead
         DOMAIN=`grep search ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
         fi
fi
FQDN=`grep ${HOST}.${DOMAIN} ${ROOTDIR}/etc/inet/hosts`
#prevent re-entrant"
if [ "${FQDN}XXX" = "XXX" ]
then
cputype="`uname -p`"
cat ${ROOTDIR}/etc/inet/hosts|nawk '$1 ~ "^#" { print $0; };
$1 !~ "^#" { hostline=""; for(i=2; i<=NF;i++) {
if($i != "'"${HOST}"'" && $i != "'"${HOST}"'." && $i != "loghost") {
hostline=hostline" "$i};
         };
  if(hostline != "") { print $1"\t"hostline; }
}' > /tmp/newhosts.$$
mv /tmp/newhosts.$$ ${ROOTDIR}/etc/inet/hosts

echo "Add hosts entry for FQDN and UQHN"
echo "${base_config_sysidcfg_ip_address}" "${HOST}.${DOMAIN}" "${HOST}" loghost
\
         >> ${ROOTDIR}/etc/inet/hosts
fi

if [ -x "${productdir}/solaris/install" ]; then
         ( cd ${productdir} ; ./solaris/install)
else
         echo "Unable to locate solaris install script"
fi



/opt/SUNWjet/Products/base_config/solariszone/install

looking at the code now it appears that no attempt was ever made to obtain the
FQDM instead just setting it to hostname. three times through the zone install
process.

so using some of your own code from JS_remove_host

ive done the following to the install script and this works.

and if you have a resolv.conf it attempts to get the domain or first search item
and set the FQDN with it in the hosts file as is required for things like
kerberos to function correctly.

im not suggesting its 100% bug free for every installation but it works here. It
will need testing evaluating to ensure it does not have any unintended side
effects.

regards peter


productdir="`cd ${0%/*}/..; pwd`"
if [ -f ${ROOTDIR}/etc/resolv.conf ]
then
DOMAIN=`grep domain ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
         if [ "${DOMAIN}X" = "X" ]
         then
         #domain not set use serach instead
         DOMAIN=`grep search ${ROOTDIR}/etc/resolv.conf|nawk '{print $2}'`
         fi
fi
FQDN=`grep ${HOST}.${DOMAIN} ${ROOTDIR}/etc/inet/hosts`
#prevent re-entrant"
if [ "${FQDN}XXX" = "XXX" ]
then
cputype="`uname -p`"
cat ${ROOTDIR}/etc/inet/hosts|nawk '$1 ~ "^#" { print $0; };
$1 !~ "^#" { hostline=""; for(i=2; i<=NF;i++) {
if($i != "'"${HOST}"'" && $i != "'"${HOST}"'." && $i != "loghost") {
hostline=hostline" "$i};
         };
  if(hostline != "") { print $1"\t"hostline; }
}' > /tmp/newhosts.$$
mv /tmp/newhosts.$$ ${ROOTDIR}/etc/inet/hosts

echo "Add hosts entry for FQDN and UQHN"
echo "${base_config_sysidcfg_ip_address}" "${HOST}.${DOMAIN}" "${HOST}" loghost
\
         >> ${ROOTDIR}/etc/inet/hosts
fi

if [ -x "${productdir}/solaris/install" ]; then
         ( cd ${productdir} ; ./solaris/install)
else
         echo "Unable to locate solaris install script"
fi



/opt/SUNWjet/Products/base_config/solariszone/install

well one of the reasons for this is that it breaks scripts in post install that
use getent, and they all need to be fixed as they dont expect to get several
lines from the reply.

however needlessly echoing lines into hosts is not good code.

something like, cat hosts|grep -v $hostname >> tempfile,

followed by the adding of hostname and FQDN, would be the right way of updating
a file.

also i noticed that despite the fqdn being entered in the nameservice= part of
sysidcfg, you make no attempt to set this in the FQDN, all it gets set to is
hostname.

regards peter




--- In JETJumpStart@yahoogroups.com, Marty Lee <marty@...> wrote:
>
>
> I think Bruce's suggestion of doing both might be the answer; at least getting
> 'check_client' in the zones module to run twice - once for each CPU arch we
> suspect and for it to write out a summary at the end of the output listing
> either a pass/fail for sparc/x86.
>
> check_client in the solariszone area does the loop around the products, so it
> wouldn't be too much to augment it.
>
> If I get a chance, I'll knock together a trial and see how it goes. Won't be
before
> next week before anyone starts to hassle me for a test copy!
>
> cheers
>
> m
>
> On 11 Nov 2009, at 20:28, Michael Ramchand wrote:
>
> > In other words.... what you are seeing has always been there, and it never
really bothered anyone.
> >
> >
> > I'll have a look at tidying it up soon.
> >
> > On the arch thing? Has anyone come up with a good suggestion to solve?
> >
> >
> >
> > On 11 Nov 2009, at 19:59, Bruce wrote:
> >
> >>
> >> ossiltd wrote:
> >> >
> >> >
> >> > ok debugged some of this zones stuff and clearly the install is
> >> > attempting to update the hosts file with a hostname. and a hostname 3
> >> > times throughout this install with no checks to see if it already has an
> >> > entry
> >> >
> >> > excerpts from the output
> >> >
> >> > + echo Populating zone tl0077 sysidcfg
> >> > Populating zone tl0077 sysidcfg
> >> > + cp /tmp/jet.28262/Clients/tl0077/sysidcfg
/zones/tl0077/root/etc/sysidcfg
> >> > + chmod 600 /zones/tl0077/root/etc/sysidcfg
> >> > ####################################################
> >> > + echo Add hosts entry for UQHN
> >> > Add hosts entry for UQHN
> >> > + echo 10.100.240.177 tl0077
> >> > + 1>> /zones/tl0077/root/etc/inet/hosts
> >> > + echo Add hosts entry for FQHN
> >> > Add hosts entry for FQHN
> >> > + echo 10.100.240.177 tl0077.
> >> > + 1>> /zones/tl0077/root/etc/inet/hosts
> >> > ####################################################
> >> > + echo Disable NFSv4 prompt
> >> > Disable NFSv4 prompt
> >> > + ed /zones/tl0077/root/etc/default/nfs
> >> > + cat
> >> > + 0<<
> >> > 1,$s/#NFSMAPID_DOMAIN=.*/NFSMAPID_DOMAIN=dynamic/g
> >> > w
> >> > q
> >> >
> >> > BASE_CONFIG: Installing base_config....
> >> > + + cd ./..
> >> > + pwd
> >> > productdir=/tmp/jet/Products/base_config
> >> > + + uname -p
> >> > cputype=sparc
> >> > ##############################################
> >> > + echo Add hosts entry for UQHN
> >> > Add hosts entry for UQHN
> >> > + echo 10.100.240.177 tl0077
> >> > + 1>> //etc/inet/hosts
> >> > + echo Add hosts entry for FQHN
> >> > Add hosts entry for FQHN
> >> > + echo 10.100.240.177 tl0077.
> >> > + 1>> //etc/inet/hosts
> >> > ################################################
> >> > + [ -x /tmp/jet/Products/base_config/solaris/install ]
> >> > + cd /tmp/jet/Products/base_config
> >> > + ./solaris/install
> >> > + JS_get_module_hint //var/opt/sun/jet/config base_config disable
> >> > bcdisableflag=
> >> > + [ -n ]
> >> > + JS_display Product base_config started
> >> > + [ 1 != 1 ]
> >> > + JS_message INFO Product base_config started
> >> >
> >> > BASE_CONFIG: Product base_config finished
> >> > BASE_CONFIG: Installing base_config....
> >> > + + cd ./..
> >> > + pwd
> >> > productdir=/tmp/jet/Products/base_config
> >> > + + uname -p
> >> > cputype=sparc
> >> > ###############################################
> >> > + echo Add hosts entry for UQHN
> >> > Add hosts entry for UQHN
> >> > + echo 10.100.240.177 tl0077
> >> > + 1>> //etc/inet/hosts
> >> > + echo Add hosts entry for FQHN
> >> > Add hosts entry for FQHN
> >> > + echo 10.100.240.177 tl0077.
> >> > + 1>> //etc/inet/hosts
> >> > ###############################################
> >> > + [ -x /tmp/jet/Products/base_config/solaris/install ]
> >> > + cd /tmp/jet/Products/base_config
> >> > + ./solaris/install
> >> > + JS_get_module_hint //var/opt/sun/jet/config base_config disable
> >> > bcdisableflag=
> >> > + [ -n ]
> >> > + JS_display Product base_config started
> >> > + [ 1 != 1 ]
> >> > + JS_message INFO Product base_config started
> >> >
> >> > any ideas on why this is or is this a know problem with jetzones
> >> >
> >>
> >> We have obviously got used to it, and let it ride. It has done it for a
> >> while.
> >>
> >> Now you have brought my attention to it, I can see (sort of) what is
> >> happening.
> >>
> >> The 1st two are inserted by, base_config/solariszone/install, at least 2
> >> more are from jetzone
> >>
> >> *Then* , we are falling back to run base_config/solaris/install
> >>
> >> We are trying to treat a zone as a solaris instance and have
> >> JET/JumpStart work with it as a product.
> >>
> >> MIke will as usual have some thoughts on this now, and I am sure he
> >> would rather not have anything in JET base_config try and see if the
> >> instance in question is a zone or not.
> >>
> >> So, maybe the easiest option is just to check if the host file entry is
> >> already there or not, that will have to go into base_config and zones.
> >> So essentially the FQHN/UQHN needs to be a Utils/lib script to save
> >> duplication of work.
> >>
> >> --
> >>
> >> Bruce D Porter
> >> Technical Consultant
> >> YTC Systems LTD
> >>
> >> "The internet is a huge and diverse community and not every one is
> >> friendly"
> >> http://www.ytc1.co.uk
> >>
> >
> > ---
> > Mike Ramchand
> > Principal Field Technologist
> > Enterprise Technical Specialist
> > Sun Microsystems (UK)
> > Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
> >
> >
> >
> >
>
> -----
> Marty Lee                         e: marty@...
> Technical Director                v: +44 845 869 2661
> Maui Systems Ltd                  f: +44 871 433 8922
> Scotland, UK                      w: http://www.maui-systems.co.uk
>

I think Bruce's suggestion of doing both might be the answer; at least getting
'check_client' in the zones module to run twice - once for each CPU arch we
suspect and for it to write out a summary at the end of the output listing
either a pass/fail for sparc/x86.

check_client in the solariszone area does the loop around the products, so it
wouldn't be too much to augment it.

If I get a chance, I'll knock together a trial and see how it goes. Won't be
before
next week before anyone starts to hassle me for a test copy!

cheers

m

On 11 Nov 2009, at 20:28, Michael Ramchand wrote:

> In other words.... what you are seeing has always been there, and it never
really bothered anyone.
>
>
> I'll have a look at tidying it up soon.
>
> On the arch thing? Has anyone come up with a good suggestion to solve?
>
>
>
> On 11 Nov 2009, at 19:59, Bruce wrote:
>
>>
>> ossiltd wrote:
>> >
>> >
>> > ok debugged some of this zones stuff and clearly the install is
>> > attempting to update the hosts file with a hostname. and a hostname 3
>> > times throughout this install with no checks to see if it already has an
>> > entry
>> >
>> > excerpts from the output
>> >
>> > + echo Populating zone tl0077 sysidcfg
>> > Populating zone tl0077 sysidcfg
>> > + cp /tmp/jet.28262/Clients/tl0077/sysidcfg /zones/tl0077/root/etc/sysidcfg
>> > + chmod 600 /zones/tl0077/root/etc/sysidcfg
>> > ####################################################
>> > + echo Add hosts entry for UQHN
>> > Add hosts entry for UQHN
>> > + echo 10.100.240.177 tl0077
>> > + 1>> /zones/tl0077/root/etc/inet/hosts
>> > + echo Add hosts entry for FQHN
>> > Add hosts entry for FQHN
>> > + echo 10.100.240.177 tl0077.
>> > + 1>> /zones/tl0077/root/etc/inet/hosts
>> > ####################################################
>> > + echo Disable NFSv4 prompt
>> > Disable NFSv4 prompt
>> > + ed /zones/tl0077/root/etc/default/nfs
>> > + cat
>> > + 0<<
>> > 1,$s/#NFSMAPID_DOMAIN=.*/NFSMAPID_DOMAIN=dynamic/g
>> > w
>> > q
>> >
>> > BASE_CONFIG: Installing base_config....
>> > + + cd ./..
>> > + pwd
>> > productdir=/tmp/jet/Products/base_config
>> > + + uname -p
>> > cputype=sparc
>> > ##############################################
>> > + echo Add hosts entry for UQHN
>> > Add hosts entry for UQHN
>> > + echo 10.100.240.177 tl0077
>> > + 1>> //etc/inet/hosts
>> > + echo Add hosts entry for FQHN
>> > Add hosts entry for FQHN
>> > + echo 10.100.240.177 tl0077.
>> > + 1>> //etc/inet/hosts
>> > ################################################
>> > + [ -x /tmp/jet/Products/base_config/solaris/install ]
>> > + cd /tmp/jet/Products/base_config
>> > + ./solaris/install
>> > + JS_get_module_hint //var/opt/sun/jet/config base_config disable
>> > bcdisableflag=
>> > + [ -n ]
>> > + JS_display Product base_config started
>> > + [ 1 != 1 ]
>> > + JS_message INFO Product base_config started
>> >
>> > BASE_CONFIG: Product base_config finished
>> > BASE_CONFIG: Installing base_config....
>> > + + cd ./..
>> > + pwd
>> > productdir=/tmp/jet/Products/base_config
>> > + + uname -p
>> > cputype=sparc
>> > ###############################################
>> > + echo Add hosts entry for UQHN
>> > Add hosts entry for UQHN
>> > + echo 10.100.240.177 tl0077
>> > + 1>> //etc/inet/hosts
>> > + echo Add hosts entry for FQHN
>> > Add hosts entry for FQHN
>> > + echo 10.100.240.177 tl0077.
>> > + 1>> //etc/inet/hosts
>> > ###############################################
>> > + [ -x /tmp/jet/Products/base_config/solaris/install ]
>> > + cd /tmp/jet/Products/base_config
>> > + ./solaris/install
>> > + JS_get_module_hint //var/opt/sun/jet/config base_config disable
>> > bcdisableflag=
>> > + [ -n ]
>> > + JS_display Product base_config started
>> > + [ 1 != 1 ]
>> > + JS_message INFO Product base_config started
>> >
>> > any ideas on why this is or is this a know problem with jetzones
>> >
>>
>> We have obviously got used to it, and let it ride. It has done it for a
>> while.
>>
>> Now you have brought my attention to it, I can see (sort of) what is
>> happening.
>>
>> The 1st two are inserted by, base_config/solariszone/install, at least 2
>> more are from jetzone
>>
>> *Then* , we are falling back to run base_config/solaris/install
>>
>> We are trying to treat a zone as a solaris instance and have
>> JET/JumpStart work with it as a product.
>>
>> MIke will as usual have some thoughts on this now, and I am sure he
>> would rather not have anything in JET base_config try and see if the
>> instance in question is a zone or not.
>>
>> So, maybe the easiest option is just to check if the host file entry is
>> already there or not, that will have to go into base_config and zones.
>> So essentially the FQHN/UQHN needs to be a Utils/lib script to save
>> duplication of work.
>>
>> --
>>
>> Bruce D Porter
>> Technical Consultant
>> YTC Systems LTD
>>
>> "The internet is a huge and diverse community and not every one is
>> friendly"
>> http://www.ytc1.co.uk
>>
>
> ---
> Mike Ramchand
> Principal Field Technologist
> Enterprise Technical Specialist
> Sun Microsystems (UK)
> Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
>
>
>
>

-----
Marty Lee                         e: marty@...
Technical Director                v: +44 845 869 2661
Maui Systems Ltd                  f: +44 871 433 8922
Scotland, UK                      w: http://www.maui-systems.co.uk

ossiltd wrote:
>
>
> ok debugged some of this zones stuff and clearly the install is
> attempting to update the hosts file with a hostname. and a hostname 3
> times throughout this install with no checks to see if it already has an
> entry
>
> excerpts from the output
>
> + echo Populating zone tl0077 sysidcfg
> Populating zone tl0077 sysidcfg
> + cp /tmp/jet.28262/Clients/tl0077/sysidcfg /zones/tl0077/root/etc/sysidcfg
> + chmod 600 /zones/tl0077/root/etc/sysidcfg
> ####################################################
> + echo Add hosts entry for UQHN
> Add hosts entry for UQHN
> + echo 10.100.240.177 tl0077
> + 1>> /zones/tl0077/root/etc/inet/hosts
> + echo Add hosts entry for FQHN
> Add hosts entry for FQHN
> + echo 10.100.240.177 tl0077.
> + 1>> /zones/tl0077/root/etc/inet/hosts
> ####################################################
> + echo Disable NFSv4 prompt
> Disable NFSv4 prompt
> + ed /zones/tl0077/root/etc/default/nfs
> + cat
> + 0<<
> 1,$s/#NFSMAPID_DOMAIN=.*/NFSMAPID_DOMAIN=dynamic/g
> w
> q
>
> BASE_CONFIG: Installing base_config....
> + + cd ./..
> + pwd
> productdir=/tmp/jet/Products/base_config
> + + uname -p
> cputype=sparc
> ##############################################
> + echo Add hosts entry for UQHN
> Add hosts entry for UQHN
> + echo 10.100.240.177 tl0077
> + 1>> //etc/inet/hosts
> + echo Add hosts entry for FQHN
> Add hosts entry for FQHN
> + echo 10.100.240.177 tl0077.
> + 1>> //etc/inet/hosts
> ################################################
> + [ -x /tmp/jet/Products/base_config/solaris/install ]
> + cd /tmp/jet/Products/base_config
> + ./solaris/install
> + JS_get_module_hint //var/opt/sun/jet/config base_config disable
> bcdisableflag=
> + [ -n ]
> + JS_display Product base_config started
> + [ 1 != 1 ]
> + JS_message INFO Product base_config started
>
> BASE_CONFIG: Product base_config finished
> BASE_CONFIG: Installing base_config....
> + + cd ./..
> + pwd
> productdir=/tmp/jet/Products/base_config
> + + uname -p
> cputype=sparc
> ###############################################
> + echo Add hosts entry for UQHN
> Add hosts entry for UQHN
> + echo 10.100.240.177 tl0077
> + 1>> //etc/inet/hosts
> + echo Add hosts entry for FQHN
> Add hosts entry for FQHN
> + echo 10.100.240.177 tl0077.
> + 1>> //etc/inet/hosts
> ###############################################
> + [ -x /tmp/jet/Products/base_config/solaris/install ]
> + cd /tmp/jet/Products/base_config
> + ./solaris/install
> + JS_get_module_hint //var/opt/sun/jet/config base_config disable
> bcdisableflag=
> + [ -n ]
> + JS_display Product base_config started
> + [ 1 != 1 ]
> + JS_message INFO Product base_config started
>
> any ideas on why this is or is this a know problem with jetzones
>

We have obviously got used to it, and let it ride. It has done it for a
while.

Now you have brought my attention to it, I can see (sort of) what is
happening.

The 1st two are inserted by, base_config/solariszone/install, at least 2
more are from jetzone

*Then* , we are falling back to run base_config/solaris/install

We are trying to treat a zone as a solaris instance and have
JET/JumpStart work with it as a product.

MIke will as usual have some thoughts on this now, and I am sure he
would rather not have anything in JET base_config try and see if the
instance in question is a zone or not.

So, maybe the easiest option is just to check if the host file entry is
already there or not, that will have to go into base_config and zones.
So essentially the FQHN/UQHN needs to be a Utils/lib script to save
duplication of work.




--

Bruce D Porter
Technical Consultant
YTC Systems LTD

"The internet is a huge and diverse community and not every one is
friendly"
http://www.ytc1.co.uk

ossiltd wrote:
>
>
> created a base zone using zone_base , made client etc, after tweaking
> template with name service etc.
>
> run jetzone on the global zone and it creates the zone ok, however.....
>
> a few problems hoping for some guidance on.
>
> 1: hosts file is full of multiple entries ie 6 lines of the same.
>
> i see there is a script to fix this, ie
> /var/opt/sun/jet/Utils/lib/JS_merge_ipnodes, and
> /var/opt/sun/jet/Utils/lib/JS_remove_host but this does not get called,
> cant find where it should be called from.

Mike may correct me, but those scripts are, I believe , for other
purposes but could be used to clean up. IIRC, even a non zone build has
extra/incorrect hosts entries.

There are a number of options, IMO.

1) jetzone attempts to cleanup by sorting/uniq
2) You make amendments by using the custom module to append hosts file entry
3) Perform a postbuild check to tidy up.

And before anyone says anything, yes 3 should not be the default option :-)



>
> 2: we need one of those lines to be a FQDN for kerberos to function
> correctly, how would you go about correcting the host file and adding a
> FQDN to it.

You can use the custom module to append required entries to the host file

>
> 3: we want to run nis and dns, however our nis finish script which works
> fine in the bare metal global zone , postinstall not getting run to
> enable the nis service. how have you overcome this.

Can you send us the template please, and the log file from the zone
(/var/opt/sun/jet/jumpstart.log)

I remember there are a few modules that do not work with zones, can't
remember if custom was one of them

>
> 4: adding any packages after install, as JS_get_cpu_arch does not seem
> to return anything for a zone, its difficult to get a product.matrix
> entry to work, hence adding any products fails to make the client as it
> can never get a product list.

I think Marty covered that one, its always annoyed us, but if we locked
the zone to an arch it would be cause more hassle.

Unless people think it would be a good idea to test *both* archs at
make_client stage ?

>
> 5: is there any more documentation on the jetzone stuff, beyond the
> sparse comments on the supplied files.

JET has always been documented in the modules, we would spnd more time
on that and then do our day jobs. Mike has done a good job on getting
the JET manual online. If I get time, I will do something about for the
Zones module (if Mike wants me to)

>
> regards peter winterflood
>
>


--

Bruce D Porter
Technical Consultant
YTC Systems LTD

"The internet is a huge and diverse community and not every one is
friendly"
http://www.ytc1.co.uk

Michael Ramchand wrote:
>
>
> (I was hoping Bruce would answer....) I'm busy till Friday, I'll look at
> it then if no-one else pipes up.

I've been away from email, 'gis a break !

>
> On 11 Nov 2009, at 07:14, ossiltd wrote:
>
>>
>>
>> ok , no response.......
>>
>> well heres some more info the output of jetzone with -x added
>>
>> hopefully this will prompt a reply.
>>
>> bash-3.00# jetzone -F tl0077
>> + CommandOpts=F
>> + CommandUsage=[-F] <zonename>
>> + CLEAN=
>> + getopts F option
>> + 2> /dev/null
>> + CLEAN=yes
>> + getopts F option
>> + 2> /dev/null
>> + shift 1
>> + [ 1 != 1 ]
>> + iphost=tl0077
>> + error_status=0
>> + echo JumpStart Enterprise Toolkit Zone creation: tl0077
>> JumpStart Enterprise Toolkit Zone creation: tl0077
>> + [ ! -f /etc/default/jetzone ]
>> + . /etc/default/jetzone
>> + JET_SERVER=10.100.240.100
>> + JET_CONFIG=/opt/SUNWjet
>> + JET_ZONEDIR=/zones
>> + SI_CONFIG_DIR=/tmp/jet.13791
>> + mkdir -p /tmp/jet.13791
>> + set -a
>> +
>>
PATH=/tmp/jet.13791/Utils/serverlib:/tmp/jet.13791/Utils/lib:/usr/bin:/usr/sbin:\
/usr/ucb:/apps/stdenv/bin:/usr/local/bin:/apps/adm/bin:/usr/sfw/bin:/usr/cluster\
/bin:/usr/cluster/lib/sc:/usr/ccs/bin
>> + ETCDIR=/usr/lib/jetzone
>> + export PATH ETCDIR
>> + + awk -F: $2 == zone { print $4; } zone=tl0077
>> + zoneadm list -icp
>> zonedir=/zones/tl0077
>> + [ -n /zones/tl0077 -a /zones/tl0077 != / ]
>> + [ -d /zones/tl0077 ]
>> + [ -n yes ]
>> + echo Cleaning out zone tl0077
>> Cleaning out zone tl0077
>> + awk -F: $2 == zone { print $3; } zone=tl0077
>> + zoneadm list -cp
>> + [ running = running ]
>> + echo Shutting down zone tl0077
>> Shutting down zone tl0077
>> + zoneadm -z tl0077 halt
>> + awk -F: $2 == zone { print $3; } zone=tl0077
>> + zoneadm list -cp
>> + [ installed != running ]
>> + echo Uninstall zone tl0077
>> Uninstall zone tl0077
>> + zoneadm -z tl0077 uninstall -F
>> + zonecfg -z tl0077 delete -F
>> + awk -F: $2 == zone { print $3; } zone=tl0077
>> + zoneadm list -cp
>> + [ -n ]
>> + echo Cleaning up zone area
>> Cleaning up zone area
>> + rm -r /zones/tl0077/*
>> + 2> /dev/null
>> + echo Mounting JET configuration area on /tmp/jet.13791
>> Mounting JET configuration area on /tmp/jet.13791
>> + mount -F nfs 10.100.240.100:/opt/SUNWjet /tmp/jet.13791
>> + [ 0 != 0 ]
>> + ROOTDIR=/
>> + export SI_CONFIG_DIR ROOTDIR
>> + [ ! -f /tmp/jet.13791/Clients/tl0077/host.config ]
>> + echo Loading zone tl0077 configuration data
>> Loading zone tl0077 configuration data
>> + . /tmp/jet.13791/Clients/tl0077/host.config
>> + base_config_products=base_config
>> + base_config_zone_autoboot=
>> + base_config_zone_ip_type=shared
>> + base_config_zone_pool=
>> + base_config_zone_pool_properties=
>> + base_config_zone_rctl_properties=
>> + base_config_zone_mem_cap=
>> + base_config_zone_ded_cpu=
>> + base_config_zone_cap_cpu=
>> + base_config_zone_max_lwps=8192
>> + base_config_zone_max_msg_ids=
>> + base_config_zone_max_sem_ids=
>> + base_config_zone_max_shm_ids=
>> + base_config_zone_max_shm_memory=
>> + base_config_zone_cpu_shares=
>> + base_config_zone_scheduling_class=
>> + base_config_zone_dir_override=
>> + base_config_zone_brand=
>> + base_config_zone_brand_preserve=
>> + base_config_zone_brand_flar=
>> + base_config_zone_brand_hostid=
>> + base_config_productdir=nfs://10.100.240.100/export/install/pkgs
>> <nfs://10.100.240.100/export/install/pkgs>
>> + base_config_patchdir=nfs://10.100.240.100/export/install/patches
>> <nfs://10.100.240.100/export/install/patches>
>> + base_config_sysidcfg_nameservice=DNS {domain_name=lehman.com
>> <http://lehman.com> name_server=10.124.3.14,10.69.23.79,10.124.131.10
>> search=lehman.com,lbcorp.lehman.com
>> <http://lehman.com>,leh.lbcorp.lehman.com}
>> + base_config_sysidcfg_network_interface=PRIMARY
>> + base_config_sysidcfg_ip_address=10.100.240.177
>> + base_config_sysidcfg_netmask=255.255.255.0
>> + base_config_sysidcfg_root_password=uy6KWXn7nr9qc
>> + base_config_sysidcfg_system_locale=C
>> + base_config_sysidcfg_timeserver=
>> + base_config_sysidcfg_timezone=GB-Eire
>> + base_config_sysidcfg_terminal=vt100
>> + base_config_sysidcfg_security_policy=NONE
>> + base_config_sysidcfg_protocol_ipv6=no
>> + base_config_sysidcfg_default_route=10.100.240.254
>> + base_config_nfsv4_domain=dynamic
>> + base_config_zone_lofs=
>> + base_config_zone_ufs=
>> + base_config_zone_zfs=
>> + base_config_zone_dataset=
>> + base_config_zone_whole_root_zone=true
>> + base_config_zone_rm_inherit_pkg_dir=
>> + base_config_zone_visible_devices=
>> + base_config_networkifs=
>> + base_config_networkif_le0=
>> + base_config_ipmp_networkifs=
>> + base_config_ipmp_networkif_qfe0_qfe1=
>> + base_config_nfs_mounts=
>> + base_config_nodename=
>> + base_config_dns_domain=
>> + base_config_dns_nameservers=
>> + base_config_dns_searchpath=
>> + base_config_update_terminal=yes
>> + base_config_enable_savecore=yes
>> + base_config_dumpadm_minfree=20000k
>> + base_config_noautoshutdown=pm_disabled
>> + base_config_enable_rootlogin=
>> + base_config_shutup_sendmail=
>> + base_config_poweroff_afterbuild=
>> + base_config_dedicated_dump_device=
>> + base_config_enable_altbreak=
>> + base_config_disable_sysid_probe=
>> + base_config_ClientOSName=solariszone
>> + base_config_debug_jumpstart_postinstall=
>> + [ -n ]
>> + zone_path=/zones/tl0077
>> + nawk -v fs=/zones/tl0077 $2 == fs {n=split($1,elems,"/");s="";for
>> (i=1;i<=n;i++) {s = s elems[i];system ("zfs mount " s);s=s "/"}}
>> + zfs list -t filesystem -o name,mountpoint -H
>> cannot mount 'tl0077': filesystem already mounted
>> + [ ! -d /zones/tl0077 ]
>> + echo Forcing permissions to 700 for /zones/tl0077
>> Forcing permissions to 700 for /zones/tl0077
>> + chmod 700 /zones/tl0077
>> + zoneadm list -c
>> + grep ^tl0077$
>> + [ -z ]
>> + echo Building zone tl0077 configuration
>> Building zone tl0077 configuration
>> + [ = ]
>> + base_config_zone_autoboot=false
>> + mach=
>> + [ ! -z ]
>> + cat
>> + 0<<
>> create -F ;
>> set zonepath=/zones/tl0077;
>> set autoboot=false;
>> 1> /tmp/zonecfg.13791
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n 8192 ]
>> + echo set max-lwps=8192
>> + 1>> /tmp/zonecfg.13791
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ -n ]
>> + [ = FSS ]
>> + [ -n true ]
>> + cat
>> + 0<<
>> 1>> /tmp/zonecfg.13791
>> + [ -n ]
>> + [ shared = exclusive ]
>> + [ PRIMARY = PRIMARY ]
>> + + get_primary_interface 10.100.240.177 255.255.255.0
>> netif=bge0
>> + [ -z bge0 ]
>> + echo Add network (bge0/10.100.240.177/255.255.255.0) to zone
>> Add network (bge0/10.100.240.177/255.255.255.0) to zone
>> + cat
>> + 0<<
>> add net;
>> set address=10.100.240.177;
>> set physical=bge0;
>> end;
>> 1>> /tmp/zonecfg.13791
>> + echo verify; commit;
>> + 1>> /tmp/zonecfg.13791
>> + echo Creating zone tl0077
>> Creating zone tl0077
>> + zonecfg -z tl0077 -f /tmp/zonecfg.13791
>> + [ 0 != 0 ]
>> + rm -f /tmp/zonecfg.13791
>> + brandedcmd=
>> + [ -n ]
>> + zoneadm list -cp
>> + awk -F: $2 == z { print $3;} z=tl0077
>> + [ configured = configured ]
>> + echo Installing zone tl0077
>> Installing zone tl0077
>> + zoneadm -z tl0077 install
>> Preparing to install zone <tl0077>.
>> Creating list of files to copy from the global zone.
>> Copying <57511> files to the zone.
>> Initializing zone product registry.
>> Determining zone package initialization order.
>> Preparing to initialize <737> packages on the zone.
>> Initialized <737> packages on zone.
>> Zone <tl0077> is initialized.
>> Installation of <3> packages was skipped.
>> Installation of these packages generated warnings: <SUNWkrbr>
>> The file </zones/tl0077/root/var/sadm/system/logs/install_log>
>> contains a log of the zone installation.
>> + [ 0 != 0 ]
>> + zonecfg -z tl0077 -f /tmp/zonecfg.13791
>> could not open file /tmp/zonecfg.13791: No such file or directory
>> + rm -f /tmp/zonecfg.13791
>> + + zoneadm list -cp
>> + awk -F: $2 == z { print $3;} z=tl0077
>> zonestatus=installed
>> + [ installed != installed ]
>> + [ installed = installed ]
>> + echo Populating zone tl0077 sysidcfg
>> Populating zone tl0077 sysidcfg
>> + cp /tmp/jet.13791/Clients/tl0077/sysidcfg
>> /zones/tl0077/root/etc/sysidcfg
>> + chmod 600 /zones/tl0077/root/etc/sysidcfg
>> + echo Add hosts entry for UQHN
>> Add hosts entry for UQHN
>> + echo 10.100.240.177 tl0077
>> + 1>> /zones/tl0077/root/etc/inet/hosts
>> + echo Add hosts entry for FQHN
>> Add hosts entry for FQHN
>> + echo 10.100.240.177 tl0077.
>> + 1>> /zones/tl0077/root/etc/inet/hosts
>> + echo Disable NFSv4 prompt
>> Disable NFSv4 prompt
>> + ed /zones/tl0077/root/etc/default/nfs
>> + cat
>> + 0<<
>> 1,$s/#NFSMAPID_DOMAIN=.*/NFSMAPID_DOMAIN=dynamic/g
>> w
>> q
>> + 1> /dev/null 2>& 1
>> + touch /zones/tl0077/root/etc/.NFS4inst_state.domain
>> + echo nfs4_domain=dynamic
>> + 1>> /zones/tl0077/root/etc/sysidcfg
>> + [ installed = installed ]
>> + echo Booting zone tl0077
>> Booting zone tl0077
>> + zoneadm -z tl0077 boot
>> + [ installed != running ]
>> + instest=1
>> + [ 1 -lt 450 ]
>> + sleep 2
>> + + zoneadm list -cp
>> + awk -F: $2 == z {print $3;} z=tl0077
>> zonestatus=running
>> + [ running = running ]
>> + instest=500
>> + + expr 500 +1
>> expr: syntax error
>> instest=
>> + [ -lt 450 ]
>> /usr/bin/jetzone[699]: test: argument expected
>> + [ running = installed -o running = running ]
>> + mkdir -p /zones/tl0077/root/var/opt/sun/jetzone
>> + finish=/zones/tl0077/root/var/opt/sun/jetzone/finish
>> + echo Adding JET hook to zone tl0077
>> Adding JET hook to zone tl0077
>> + + JS_get_netmask 10.100.240.177
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> cannot access parent directories
>> JS_netmask=255.255.255.0
>> + + JS_get_network 10.100.240.177 255.255.255.0
>> cannot access parent directories
>> JS_network=10.100.240.0
>> + + JS_server_interface_lookup 10.100.240.0 255.255.255.0
>> cannot access parent directories
>> SNJETSERVER=10.100.240.100
>> + [ -n 10.100.240.100 ]
>> + JET_SERVER=10.100.240.100
>> + [ -n ]
>> + sed -e s?###JETSERVER###?10.100.240.100? -e s?###JETDIR###?/opt/SUNWjet?
>> + cat
>> + 0<<
>> #!/usr/bin/ksh
>> #
>>
################################################################################\
#
>> # Customer acknowledges that the software script(s) are not a
>> # generally available standard Sun product and that it is a
>> # fundamental condition of supply of the software script(s) to
>> # Customer that Customer accepts the same "as is" and without
>> # warranty of any kind. No support services of any kind are
>> # available for the software script(s) and Sun does not represent
>> # to Customer that:
>> #
>> # (i) operation of any of the software script(s) shall be
>> # uninterrupted or error free, or
>> #
>> # (ii) functions contained in the software script(s) shall operate
>> # in the combinations which may be selected for use by
>> # Customer or meet Customer's requirements, or
>> #
>> # (iii) that upgraded versions of the software script(s) will be
>> # issued.
>> #
>> # If Customer wishes to have the software script(s) modified, or
>> # otherwise requires support, Sun may provide the same by means of
>> # a separate consulting agreement priced on a time and materials
>> # basis.
>> #
>>
################################################################################\
#
>> # Author: Marty Lee
>> # Date: $Date: 2009/05/07 16:12:32 $
>> # Version: $Revision: 1.50 $
>> #
>> # Synopsis: Hook to make JET think it is JumpStarting a zone
>> #
>>
################################################################################\
#
>> # Change history (most recent first)
>> #
>> # When Who Comments
>> # ---- --- --------
>> # 06-06-2004 Marty Lee Creation
>> #
>>
>> exec >/dev/msglog
>>
>> echo "Starting JumpStart Enterprise Toolkit helper script"
>>
>> set -a
>>
>> SI_CONFIG_DIR="/tmp/jet"
>> JETSERVER="###JETSERVER###"
>> JETDIR="###JETDIR###"
>>
>> if [ -z "${JETSERVER}" -o -z "${JETDIR}" ]; then
>> echo "Missing defaults. Exiting"
>> exit 1
>> fi
>>
>> mkdir -p ${SI_CONFIG_DIR}
>>
>> echo "Mounting JET filesystem"
>>
>> mount -F nfs ${JETSERVER}:${JETDIR} ${SI_CONFIG_DIR}
>> if [ $? != "0" ]; then
>> echo "Error mounting JET filesystem."
>> error_status=1
>> else
>>
>> ROOTDIR="/"
>>
>> export SI_CONFIG_DIR ROOTDIR
>>
>> #
>> # Now call the finish script for JET
>> #
>> if [ -x ${SI_CONFIG_DIR}/Utils/finish ]; then
>> echo "Starting JET finish script"
>> ${SI_CONFIG_DIR}/Utils/finish
>> else
>> echo "No finish script found in JET filesystem."
>> fi
>> fi
>>
>> #
>> # Now tidy up
>> #
>> umount ${SI_CONFIG_DIR}
>> mv -f $0 /var/tmp
>>
>> if [ -x /usr/bin/svcs ]; then
>> if [ -n "`/usr/bin/svcs -H svc:/site/jetzonefinish`" ]; then
>> echo "Disable & delete SMF tag svc:/site/jetzonefinish"
>> /usr/sbin/svcadm disable svc:/site/jetzonefinish
>> /usr/sbin/svccfg delete svc:/site/jetzonefinish
>> rm -f /var/svc/manifest/site/jetzonefinish.xml
>> fi
>> fi
>>
>> reboot
>>
>> + 1> /zones/tl0077/root/var/opt/sun/jetzone/finish
>> + chmod 755 /zones/tl0077/root/var/opt/sun/jetzone/finish
>> + cp /usr/lib/jetzone/jetzonefinish.xml
>> /zones/tl0077/root/var/svc/manifest/site/jetzonefinish.xml
>> + [ running = installed ]
>> + [ running = running ]
>> + echo Re-booting zone tl0077
>> Re-booting zone tl0077
>> + zoneadm -z tl0077 reboot
>> + echo To monitor the installation of the zone, please run the
>> command\n\tzlogin -C tl0077
>> To monitor the installation of the zone, please run the command
>> zlogin -C tl0077
>> + umount /tmp/jet.13791
>> + rm -rf /tmp/jet.13791
>> + exit 0
>> bash-3.00# zlogin -C tl0077
>> [Connected to zone 'tl0077' console] 150/150
>> Reading ZFS config: done.
>> Creating new rsa public/private host key pair
>> Creating new dsa public/private host key pair
>> Configuring network interface addresses: bge0.
>>
>> rebooting system due to change(s) in /etc/default/init
>>
>> [NOTICE: Zone rebooting]
>>
>> SunOS Release 5.10 Version Generic_141444-09 64-bit
>> Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
>> Use is subject to license terms.
>> Hostname: tl0077
>> Reading ZFS config: done.
>> Starting JumpStart Enterprise Toolkit helper script
>> Mounting JET filesystem
>> Starting JET finish script
>> Installation of tl0077 at 08:38 on 10-Nov-2009
>> Loading JumpStart Server variables
>> JumpStart Enterprise Toolkit version 4.7
>> Loading Client configuration file
>> Creating directory: /var/opt/sun/jet/post_install
>> Creating directory: /var/opt/sun/jet/Utils
>> Creating directory: /var/opt/sun/jet/config
>> Creating directory: /var/opt/sun/jet/js_media/patch
>> Nov 10 08:38:20 tl0077 svc.startd[19112]: system/webconsole:console
>> failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
>> Creating directory: /var/opt/sun/jet/js_media/pkg
>> Copying file Clients/tl0077/sysidcfg to //var/opt/sun/jet/config/sysidcfg
>> Copying file Clients/tl0077/host.config to
>> //var/opt/sun/jet/config/host.config
>> Copying file Utils/solariszone/releaseinfo to
>> //var/opt/sun/jet/config/releaseinfo
>> ERROR: JS_cp: Error occured while copying
>> /tmp/jet/Utils/solariszone/releaseinfo to
>> //var/opt/sun/jet/config/releaseinfo
>> Copying functions to //var/opt/sun/jet/Utils/lib
>> Copying file Clients/tl0077/module_hints to
>> //var/opt/sun/jet/config/module_hints
>> NFS Mounting Media Directories
>> Mounting nfs://10.100.240.100/export/install/patches
>> <nfs://10.100.240.100/export/install/patches> on
>> //var/opt/sun/jet/js_media/patch
>> Mounting nfs://10.100.240.100/export/install/pkgs
>> <nfs://10.100.240.100/export/install/pkgs> on
>> //var/opt/sun/jet/js_media/pkg
>> BASE_CONFIG: Installing base_config....
>> Add hosts entry for UQHN
>> Add hosts entry for FQHN
>> BASE_CONFIG: Product base_config started
>> BASE_CONFIG: Trying to use external matrix cmd
>> /tmp/jet/Products/zones/empty-matrix
>> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
>> BASE_CONFIG: Unable to locate package.matrix file... exiting.
>> BASE_CONFIG: No HW specific packages for platform SUNW,SPARC-Enterprise
>> BASE_CONFIG: Trying to use external matrix cmd
>> /tmp/jet/Products/zones/empty-matrix
>> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
>> BASE_CONFIG: Unable to locate patch.matrix file... exiting.
>> BASE_CONFIG: No HW specific patches for platform SUNW,SPARC-Enterprise
>> BASE_CONFIG: Set root password
>> BASE_CONFIG: Setting netmask for primary interface
>> BASE_CONFIG: Add netmask 10.100.240.0 / 255.255.255.0
>> BASE_CONFIG: Disabling power management
>> BASE_CONFIG: Creating directory: /var/opt/sun/jet/post_install/n-post
>> BASE_CONFIG: Register postinstall script 'setupdumpdevice' for boot n
>> BASE_CONFIG: Creating directory: /var/opt/sun/jet/post_install/n
>> BASE_CONFIG: Register postinstall script 'run_sshkeygen' for boot n
>> BASE_CONFIG: Setting system terminal type to vt100
>> BASE_CONFIG: Register postinstall script 'console' for boot n
>> BASE_CONFIG: Setting NFSv4 domain
>> BASE_CONFIG: Creating directory: /var/opt/sun/jet/system.add
>> BASE_CONFIG: Product base_config finished
>> BASE_CONFIG: Installing base_config....
>> Add hosts entry for UQHN
>> Add hosts entry for FQHN
>> BASE_CONFIG: Product base_config started
>> BASE_CONFIG: Trying to use external matrix cmd
>> /tmp/jet/Products/zones/empty-matrix
>> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
>> BASE_CONFIG: Unable to locate package.matrix file... exiting.
>> BASE_CONFIG: No HW specific packages for platform SUNW,SPARC-Enterprise
>> BASE_CONFIG: Trying to use external matrix cmd
>> /tmp/jet/Products/zones/empty-matrix
>> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
>> BASE_CONFIG: Unable to locate patch.matrix file... exiting.
>> BASE_CONFIG: No HW specific patches for platform SUNW,SPARC-Enterprise
>> BASE_CONFIG: Set root password
>> BASE_CONFIG: Setting netmask for primary interface
>> BASE_CONFIG: Disabling power management
>> BASE_CONFIG: Register postinstall script 'setupdumpdevice' for boot n
>> BASE_CONFIG: Register postinstall script 'run_sshkeygen' for boot n
>> BASE_CONFIG: Setting system terminal type to vt100
>> BASE_CONFIG: Register postinstall script 'console' for boot n
>> BASE_CONFIG: Setting NFSv4 domain
>> BASE_CONFIG: Product base_config finished
>> ----------------------------------------------------------
>> Product modules processed, finish up installation tasks
>> Creating directory: /var/opt/sun/jet/system.add/updated
>> Copying file etc/jumpstart.conf to //var/opt/sun/jet/config/jumpstart.conf
>> Copying file Utils/smf/jetjump.xml to //var/svc/manifest/site/jetjump.xml
>> Copying file Utils/S99jumpstart to
>> //var/opt/sun/jet/post_install/S99jumpstart
>> NFS Unmounting Media Directories
>> Unmounting /var/opt/sun/jet/js_media/pkg
>> Unmounting /var/opt/sun/jet/js_media/patch
>> Make a link to finish log...
>> Updating boot-archive
>> /: not a boot archive based Solaris instance
>> Disable & delete SMF tag svc:/site/jetzonefinish
>> Nov 10 08:38:24 tl0077 reboot: rebooted by root
>>
>> tl0077 console login: Nov 10 08:38:24 tl0077 syslogd: going down on
>> signal 15
>> Nov 10 08:38:24 /usr/lib/snmp/snmpdx: received signal 15
>>
>> [NOTICE: Zone rebooting]
>>
>> SunOS Release 5.10 Version Generic_141444-09 64-bit
>> Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
>> Use is subject to license terms.
>> Hostname: tl0077
>> Loading smf(5) service descriptions: 1/1
>> Reading ZFS config: done.
>> /var/opt/sun/jet/config/releaseinfo file unavailable
>> JumpStart (/var/opt/sun/jet/post_install/S99jumpstart) started @ Tue
>> Nov 10 08:38:37 GMT 2009
>> Loading JumpStart Server variables
>> Loading Client configuration file
>> No more reboots required
>> Running additional install files for reboot n
>> NFS Mounting Media Directories
>> Mounting nfs://10.100.240.100/export/install/patches
>> <nfs://10.100.240.100/export/install/patches> on
>> /var/opt/sun/jet/js_media/patch
>> Mounting nfs://10.100.240.100/export/install/pkgs
>> <nfs://10.100.240.100/export/install/pkgs> on
>> /var/opt/sun/jet/js_media/pkg
>> Nov 10 08:38:38 tl0077 svc.startd[20529]: system/webconsole:console
>> failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
>> BASE_CONFIG: Running 001.base_config.001.run_sshkeygen
>> BASE_CONFIG: Generating ssh keys...
>> BASE_CONFIG: Running 001.base_config.002.console
>> BASE_CONFIG: Setting terminal type to vt100
>> BASE_CONFIG: Running 001.base_config.003.run_sshkeygen
>> BASE_CONFIG: Generating ssh keys...
>> BASE_CONFIG: Running 001.base_config.004.console
>> BASE_CONFIG: Setting terminal type to vt100
>> BASE_CONFIG: Running 001.base_config.001.setupdumpdevice
>> BASE_CONFIG: Unable to execute /usr/sbin/dumpadm, check Solaris
>> version supports dumpadm(1M)
>> BASE_CONFIG: Running 001.base_config.002.setupdumpdevice
>> BASE_CONFIG: Unable to execute /usr/sbin/dumpadm, check Solaris
>> version supports dumpadm(1M)
>> NFS Unmounting Media Directories
>> Unmounting /var/opt/sun/jet/js_media/pkg
>> Unmounting /var/opt/sun/jet/js_media/patch
>> Disable & delete SMF tag svc:/site/jetjump
>> JumpStart is complete @ Tue Nov 10 08:38:51 GMT 2009
>>
>> --- In JETJumpStart@yahoogroups.com
>> <mailto:JETJumpStart%40yahoogroups.com>, "ossiltd"
>> <peter.winterflood@...> wrote:
>> >
>> > created a base zone using zone_base , made client etc, after
>> tweaking template with name service etc.
>> >
>> > run jetzone on the global zone and it creates the zone ok, however.....
>> >
>> > a few problems hoping for some guidance on.
>> >
>> > 1: hosts file is full of multiple entries ie 6 lines of the same.
>> >
>> > i see there is a script to fix this, ie
>> /var/opt/sun/jet/Utils/lib/JS_merge_ipnodes, and
>> /var/opt/sun/jet/Utils/lib/JS_remove_host but this does not get
>> called, cant find where it should be called from.
>> >
>> > 2: we need one of those lines to be a FQDN for kerberos to function
>> correctly, how would you go about correcting the host file and adding
>> a FQDN to it.
>> >
>> > 3: we want to run nis and dns, however our nis finish script which
>> works fine in the bare metal global zone , postinstall not getting run
>> to enable the nis service. how have you overcome this.
>> >
>> > 4: adding any packages after install, as JS_get_cpu_arch does not
>> seem to return anything for a zone, its difficult to get a
>> product.matrix entry to work, hence adding any products fails to make
>> the client as it can never get a product list.
>> >
>> > 5: is there any more documentation on the jetzone stuff, beyond the
>> sparse comments on the supplied files.
>> >
>> > regards peter winterflood
>> >
>>
>
> ---
> Mike Ramchand
> Principal Field Technologist
> Enterprise Technical Specialist
> Sun Microsystems (UK)
> Tel: +44 125 2421091, Ext: (70)21091, Mob: +44 780 1179593
>
>
>


--

Bruce D Porter
Technical Consultant
YTC Systems LTD

"The internet is a huge and diverse community and not every one is
friendly"
http://www.ytc1.co.uk

When JetZONES was developed, Zones were a moving target - they had only just
been
announced and with each rev of Solaris, things changed. JetZONES does have some
quirks - like multiple entries in the hosts files, but on the whole, it works.

Patches can be submitted to Mike if you are sure that things work across
different
versions of Solaris and have time to test.

About CPU type - it's been discussed on this email list before; the problem is
that
when you define a zone, it's CPU agnostic; you could deploy it on Sparc or X86
depending on when and where you ran the jetzone script. As such, trying to do
package/patch matrix at make_client time is futile.

That said, there are probably some good suggestions about how to overcome those
problems, but as yet, nobody has come forward with them. Mike is the only one
actively doing work with JET at Sun now from the original authors; Bruce and
myself
have departed and now do contract work. As such, I only tend to go and fix code
that
directly relates to pieces of work I'm directly involved in - I don't have time
to
get involved as much as I used too.

This is a community alias - there is no guarantee that you will get a response
and
even less chance that it'll be the response you are after! It's good that you
have
taken time so far to look at what JetZONES is doing, but in terms of missing
docs
etc, if you can't find them, help by writing something and then sharing it.

Cheers

m


On 11 Nov 2009, at 07:14, ossiltd wrote:

> ok , no response.......
>
> well heres some more info the output of jetzone with -x added
>
> hopefully this will prompt a reply.
>
> bash-3.00# jetzone -F tl0077
> + CommandOpts=F
> + CommandUsage=[-F] <zonename>
> + CLEAN=
> + getopts F option
> + 2> /dev/null
> + CLEAN=yes
> + getopts F option
> + 2> /dev/null
> + shift 1
> + [ 1 != 1 ]
> + iphost=tl0077
> + error_status=0
> + echo JumpStart Enterprise Toolkit Zone creation: tl0077
> JumpStart Enterprise Toolkit Zone creation: tl0077
> + [ ! -f /etc/default/jetzone ]
> + . /etc/default/jetzone
> + JET_SERVER=10.100.240.100
> + JET_CONFIG=/opt/SUNWjet
> + JET_ZONEDIR=/zones
> + SI_CONFIG_DIR=/tmp/jet.13791
> + mkdir -p /tmp/jet.13791
> + set -a
> +
PATH=/tmp/jet.13791/Utils/serverlib:/tmp/jet.13791/Utils/lib:/usr/bin:/usr/sbin:\
/usr/ucb:/apps/stdenv/bin:/usr/local/bin:/apps/adm/bin:/usr/sfw/bin:/usr/cluster\
/bin:/usr/cluster/lib/sc:/usr/ccs/bin
> + ETCDIR=/usr/lib/jetzone
> + export PATH ETCDIR
> + + awk -F: $2 == zone { print $4; } zone=tl0077
> + zoneadm list -icp
> zonedir=/zones/tl0077
> + [ -n /zones/tl0077 -a /zones/tl0077 != / ]
> + [ -d /zones/tl0077 ]
> + [ -n yes ]
> + echo Cleaning out zone tl0077
> Cleaning out zone tl0077
> + awk -F: $2 == zone { print $3; } zone=tl0077
> + zoneadm list -cp
> + [ running = running ]
> + echo Shutting down zone tl0077
> Shutting down zone tl0077
> + zoneadm -z tl0077 halt
> + awk -F: $2 == zone { print $3; } zone=tl0077
> + zoneadm list -cp
> + [ installed != running ]
> + echo Uninstall zone tl0077
> Uninstall zone tl0077
> + zoneadm -z tl0077 uninstall -F
> + zonecfg -z tl0077 delete -F
> + awk -F: $2 == zone { print $3; } zone=tl0077
> + zoneadm list -cp
> + [ -n ]
> + echo Cleaning up zone area
> Cleaning up zone area
> + rm -r /zones/tl0077/*
> + 2> /dev/null
> + echo Mounting JET configuration area on /tmp/jet.13791
> Mounting JET configuration area on /tmp/jet.13791
> + mount -F nfs 10.100.240.100:/opt/SUNWjet /tmp/jet.13791
> + [ 0 != 0 ]
> + ROOTDIR=/
> + export SI_CONFIG_DIR ROOTDIR
> + [ ! -f /tmp/jet.13791/Clients/tl0077/host.config ]
> + echo Loading zone tl0077 configuration data
> Loading zone tl0077 configuration data
> + . /tmp/jet.13791/Clients/tl0077/host.config
> + base_config_products=base_config
> + base_config_zone_autoboot=
> + base_config_zone_ip_type=shared
> + base_config_zone_pool=
> + base_config_zone_pool_properties=
> + base_config_zone_rctl_properties=
> + base_config_zone_mem_cap=
> + base_config_zone_ded_cpu=
> + base_config_zone_cap_cpu=
> + base_config_zone_max_lwps=8192
> + base_config_zone_max_msg_ids=
> + base_config_zone_max_sem_ids=
> + base_config_zone_max_shm_ids=
> + base_config_zone_max_shm_memory=
> + base_config_zone_cpu_shares=
> + base_config_zone_scheduling_class=
> + base_config_zone_dir_override=
> + base_config_zone_brand=
> + base_config_zone_brand_preserve=
> + base_config_zone_brand_flar=
> + base_config_zone_brand_hostid=
> + base_config_productdir=nfs://10.100.240.100/export/install/pkgs
> + base_config_patchdir=nfs://10.100.240.100/export/install/patches
> + base_config_sysidcfg_nameservice=DNS {domain_name=lehman.com
name_server=10.124.3.14,10.69.23.79,10.124.131.10
search=lehman.com,lbcorp.lehman.com,leh.lbcorp.lehman.com}
> + base_config_sysidcfg_network_interface=PRIMARY
> + base_config_sysidcfg_ip_address=10.100.240.177
> + base_config_sysidcfg_netmask=255.255.255.0
> + base_config_sysidcfg_root_password=uy6KWXn7nr9qc
> + base_config_sysidcfg_system_locale=C
> + base_config_sysidcfg_timeserver=
> + base_config_sysidcfg_timezone=GB-Eire
> + base_config_sysidcfg_terminal=vt100
> + base_config_sysidcfg_security_policy=NONE
> + base_config_sysidcfg_protocol_ipv6=no
> + base_config_sysidcfg_default_route=10.100.240.254
> + base_config_nfsv4_domain=dynamic
> + base_config_zone_lofs=
> + base_config_zone_ufs=
> + base_config_zone_zfs=
> + base_config_zone_dataset=
> + base_config_zone_whole_root_zone=true
> + base_config_zone_rm_inherit_pkg_dir=
> + base_config_zone_visible_devices=
> + base_config_networkifs=
> + base_config_networkif_le0=
> + base_config_ipmp_networkifs=
> + base_config_ipmp_networkif_qfe0_qfe1=
> + base_config_nfs_mounts=
> + base_config_nodename=
> + base_config_dns_domain=
> + base_config_dns_nameservers=
> + base_config_dns_searchpath=
> + base_config_update_terminal=yes
> + base_config_enable_savecore=yes
> + base_config_dumpadm_minfree=20000k
> + base_config_noautoshutdown=pm_disabled
> + base_config_enable_rootlogin=
> + base_config_shutup_sendmail=
> + base_config_poweroff_afterbuild=
> + base_config_dedicated_dump_device=
> + base_config_enable_altbreak=
> + base_config_disable_sysid_probe=
> + base_config_ClientOSName=solariszone
> + base_config_debug_jumpstart_postinstall=
> + [ -n ]
> + zone_path=/zones/tl0077
> + nawk -v fs=/zones/tl0077 $2 == fs {n=split($1,elems,"/");s="";for
(i=1;i<=n;i++) {s = s elems[i];system ("zfs mount " s);s=s "/"}}
> + zfs list -t filesystem -o name,mountpoint -H
> cannot mount 'tl0077': filesystem already mounted
> + [ ! -d /zones/tl0077 ]
> + echo Forcing permissions to 700 for /zones/tl0077
> Forcing permissions to 700 for /zones/tl0077
> + chmod 700 /zones/tl0077
> + zoneadm list -c
> + grep ^tl0077$
> + [ -z ]
> + echo Building zone tl0077 configuration
> Building zone tl0077 configuration
> + [ = ]
> + base_config_zone_autoboot=false
> + mach=
> + [ ! -z ]
> + cat
> + 0<<
> create -F ;
> set zonepath=/zones/tl0077;
> set autoboot=false;
> 1> /tmp/zonecfg.13791
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n 8192 ]
> + echo set max-lwps=8192
> + 1>> /tmp/zonecfg.13791
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ -n ]
> + [ = FSS ]
> + [ -n true ]
> + cat
> + 0<<
> 1>> /tmp/zonecfg.13791
> + [ -n ]
> + [ shared = exclusive ]
> + [ PRIMARY = PRIMARY ]
> + + get_primary_interface 10.100.240.177 255.255.255.0
> netif=bge0
> + [ -z bge0 ]
> + echo Add network (bge0/10.100.240.177/255.255.255.0) to zone
> Add network (bge0/10.100.240.177/255.255.255.0) to zone
> + cat
> + 0<<
> add net;
> set address=10.100.240.177;
> set physical=bge0;
> end;
> 1>> /tmp/zonecfg.13791
> + echo verify; commit;
> + 1>> /tmp/zonecfg.13791
> + echo Creating zone tl0077
> Creating zone tl0077
> + zonecfg -z tl0077 -f /tmp/zonecfg.13791
> + [ 0 != 0 ]
> + rm -f /tmp/zonecfg.13791
> + brandedcmd=
> + [ -n ]
> + zoneadm list -cp
> + awk -F: $2 == z { print $3;} z=tl0077
> + [ configured = configured ]
> + echo Installing zone tl0077
> Installing zone tl0077
> + zoneadm -z tl0077 install
> Preparing to install zone <tl0077>.
> Creating list of files to copy from the global zone.
> Copying <57511> files to the zone.
> Initializing zone product registry.
> Determining zone package initialization order.
> Preparing to initialize <737> packages on the zone.
> Initialized <737> packages on zone.
> Zone <tl0077> is initialized.
> Installation of <3> packages was skipped.
> Installation of these packages generated warnings: <SUNWkrbr>
> The file </zones/tl0077/root/var/sadm/system/logs/install_log> contains a log
of the zone installation.
> + [ 0 != 0 ]
> + zonecfg -z tl0077 -f /tmp/zonecfg.13791
> could not open file /tmp/zonecfg.13791: No such file or directory
> + rm -f /tmp/zonecfg.13791
> + + zoneadm list -cp
> + awk -F: $2 == z { print $3;} z=tl0077
> zonestatus=installed
> + [ installed != installed ]
> + [ installed = installed ]
> + echo Populating zone tl0077 sysidcfg
> Populating zone tl0077 sysidcfg
> + cp /tmp/jet.13791/Clients/tl0077/sysidcfg /zones/tl0077/root/etc/sysidcfg
> + chmod 600 /zones/tl0077/root/etc/sysidcfg
> + echo Add hosts entry for UQHN
> Add hosts entry for UQHN
> + echo 10.100.240.177 tl0077
> + 1>> /zones/tl0077/root/etc/inet/hosts
> + echo Add hosts entry for FQHN
> Add hosts entry for FQHN
> + echo 10.100.240.177 tl0077.
> + 1>> /zones/tl0077/root/etc/inet/hosts
> + echo Disable NFSv4 prompt
> Disable NFSv4 prompt
> + ed /zones/tl0077/root/etc/default/nfs
> + cat
> + 0<<
> 1,$s/#NFSMAPID_DOMAIN=.*/NFSMAPID_DOMAIN=dynamic/g
> w
> q
> + 1> /dev/null 2>& 1
> + touch /zones/tl0077/root/etc/.NFS4inst_state.domain
> + echo nfs4_domain=dynamic
> + 1>> /zones/tl0077/root/etc/sysidcfg
> + [ installed = installed ]
> + echo Booting zone tl0077
> Booting zone tl0077
> + zoneadm -z tl0077 boot
> + [ installed != running ]
> + instest=1
> + [ 1 -lt 450 ]
> + sleep 2
> + + zoneadm list -cp
> + awk -F: $2 == z {print $3;} z=tl0077
> zonestatus=running
> + [ running = running ]
> + instest=500
> + + expr 500 +1
> expr: syntax error
> instest=
> + [ -lt 450 ]
> /usr/bin/jetzone[699]: test: argument expected
> + [ running = installed -o running = running ]
> + mkdir -p /zones/tl0077/root/var/opt/sun/jetzone
> + finish=/zones/tl0077/root/var/opt/sun/jetzone/finish
> + echo Adding JET hook to zone tl0077
> Adding JET hook to zone tl0077
> + + JS_get_netmask 10.100.240.177
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> cannot access parent directories
> JS_netmask=255.255.255.0
> + + JS_get_network 10.100.240.177 255.255.255.0
> cannot access parent directories
> JS_network=10.100.240.0
> + + JS_server_interface_lookup 10.100.240.0 255.255.255.0
> cannot access parent directories
> SNJETSERVER=10.100.240.100
> + [ -n 10.100.240.100 ]
> + JET_SERVER=10.100.240.100
> + [ -n ]
> + sed -e s?###JETSERVER###?10.100.240.100? -e s?###JETDIR###?/opt/SUNWjet?
> + cat
> + 0<<
> #!/usr/bin/ksh
> #
>
################################################################################\
#
> # Customer acknowledges that the software script(s) are not a
> # generally available standard Sun product and that it is a
> # fundamental condition of supply of the software script(s) to
> # Customer that Customer accepts the same "as is" and without
> # warranty of any kind. No support services of any kind are
> # available for the software script(s) and Sun does not represent
> # to Customer that:
> #
> # (i) operation of any of the software script(s) shall be
> # uninterrupted or error free, or
> #
> # (ii) functions contained in the software script(s) shall operate
> # in the combinations which may be selected for use by
> # Customer or meet Customer's requirements, or
> #
> # (iii) that upgraded versions of the software script(s) will be
> # issued.
> #
> # If Customer wishes to have the software script(s) modified, or
> # otherwise requires support, Sun may provide the same by means of
> # a separate consulting agreement priced on a time and materials
> # basis.
> #
>
################################################################################\
#
> # Author: Marty Lee
> # Date: $Date: 2009/05/07 16:12:32 $
> # Version: $Revision: 1.50 $
> #
> # Synopsis: Hook to make JET think it is JumpStarting a zone
> #
>
################################################################################\
#
> # Change history (most recent first)
> #
> # When Who Comments
> # ---- --- --------
> # 06-06-2004 Marty Lee Creation
> #
>
> exec >/dev/msglog
>
> echo "Starting JumpStart Enterprise Toolkit helper script"
>
> set -a
>
> SI_CONFIG_DIR="/tmp/jet"
> JETSERVER="###JETSERVER###"
> JETDIR="###JETDIR###"
>
> if [ -z "${JETSERVER}" -o -z "${JETDIR}" ]; then
> echo "Missing defaults. Exiting"
> exit 1
> fi
>
> mkdir -p ${SI_CONFIG_DIR}
>
> echo "Mounting JET filesystem"
>
> mount -F nfs ${JETSERVER}:${JETDIR} ${SI_CONFIG_DIR}
> if [ $? != "0" ]; then
> echo "Error mounting JET filesystem."
> error_status=1
> else
>
> ROOTDIR="/"
>
> export SI_CONFIG_DIR ROOTDIR
>
> #
> # Now call the finish script for JET
> #
> if [ -x ${SI_CONFIG_DIR}/Utils/finish ]; then
> echo "Starting JET finish script"
> ${SI_CONFIG_DIR}/Utils/finish
> else
> echo "No finish script found in JET filesystem."
> fi
> fi
>
> #
> # Now tidy up
> #
> umount ${SI_CONFIG_DIR}
> mv -f $0 /var/tmp
>
> if [ -x /usr/bin/svcs ]; then
> if [ -n "`/usr/bin/svcs -H svc:/site/jetzonefinish`" ]; then
> echo "Disable & delete SMF tag svc:/site/jetzonefinish"
> /usr/sbin/svcadm disable svc:/site/jetzonefinish
> /usr/sbin/svccfg delete svc:/site/jetzonefinish
> rm -f /var/svc/manifest/site/jetzonefinish.xml
> fi
> fi
>
> reboot
>
> + 1> /zones/tl0077/root/var/opt/sun/jetzone/finish
> + chmod 755 /zones/tl0077/root/var/opt/sun/jetzone/finish
> + cp /usr/lib/jetzone/jetzonefinish.xml
/zones/tl0077/root/var/svc/manifest/site/jetzonefinish.xml
> + [ running = installed ]
> + [ running = running ]
> + echo Re-booting zone tl0077
> Re-booting zone tl0077
> + zoneadm -z tl0077 reboot
> + echo To monitor the installation of the zone, please run the
command\n\tzlogin -C tl0077
> To monitor the installation of the zone, please run the command
> zlogin -C tl0077
> + umount /tmp/jet.13791
> + rm -rf /tmp/jet.13791
> + exit 0
> bash-3.00# zlogin -C tl0077
> [Connected to zone 'tl0077' console] 150/150
> Reading ZFS config: done.
> Creating new rsa public/private host key pair
> Creating new dsa public/private host key pair
> Configuring network interface addresses: bge0.
>
> rebooting system due to change(s) in /etc/default/init
>
> [NOTICE: Zone rebooting]
>
> SunOS Release 5.10 Version Generic_141444-09 64-bit
> Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
> Use is subject to license terms.
> Hostname: tl0077
> Reading ZFS config: done.
> Starting JumpStart Enterprise Toolkit helper script
> Mounting JET filesystem
> Starting JET finish script
> Installation of tl0077 at 08:38 on 10-Nov-2009
> Loading JumpStart Server variables
> JumpStart Enterprise Toolkit version 4.7
> Loading Client configuration file
> Creating directory: /var/opt/sun/jet/post_install
> Creating directory: /var/opt/sun/jet/Utils
> Creating directory: /var/opt/sun/jet/config
> Creating directory: /var/opt/sun/jet/js_media/patch
> Nov 10 08:38:20 tl0077 svc.startd[19112]: system/webconsole:console failed
fatally: transitioned to maintenance (see 'svcs -xv' for details)
> Creating directory: /var/opt/sun/jet/js_media/pkg
> Copying file Clients/tl0077/sysidcfg to //var/opt/sun/jet/config/sysidcfg
> Copying file Clients/tl0077/host.config to
//var/opt/sun/jet/config/host.config
> Copying file Utils/solariszone/releaseinfo to
//var/opt/sun/jet/config/releaseinfo
> ERROR: JS_cp: Error occured while copying
/tmp/jet/Utils/solariszone/releaseinfo to //var/opt/sun/jet/config/releaseinfo
> Copying functions to //var/opt/sun/jet/Utils/lib
> Copying file Clients/tl0077/module_hints to
//var/opt/sun/jet/config/module_hints
> NFS Mounting Media Directories
> Mounting nfs://10.100.240.100/export/install/patches on
//var/opt/sun/jet/js_media/patch
> Mounting nfs://10.100.240.100/export/install/pkgs on
//var/opt/sun/jet/js_media/pkg
> BASE_CONFIG: Installing base_config....
> Add hosts entry for UQHN
> Add hosts entry for FQHN
> BASE_CONFIG: Product base_config started
> BASE_CONFIG: Trying to use external matrix cmd
/tmp/jet/Products/zones/empty-matrix
> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
> BASE_CONFIG: Unable to locate package.matrix file... exiting.
> BASE_CONFIG: No HW specific packages for platform SUNW,SPARC-Enterprise
> BASE_CONFIG: Trying to use external matrix cmd
/tmp/jet/Products/zones/empty-matrix
> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
> BASE_CONFIG: Unable to locate patch.matrix file... exiting.
> BASE_CONFIG: No HW specific patches for platform SUNW,SPARC-Enterprise
> BASE_CONFIG: Set root password
> BASE_CONFIG: Setting netmask for primary interface
> BASE_CONFIG: Add netmask 10.100.240.0 / 255.255.255.0
> BASE_CONFIG: Disabling power management
> BASE_CONFIG: Creating directory: /var/opt/sun/jet/post_install/n-post
> BASE_CONFIG: Register postinstall script 'setupdumpdevice' for boot n
> BASE_CONFIG: Creating directory: /var/opt/sun/jet/post_install/n
> BASE_CONFIG: Register postinstall script 'run_sshkeygen' for boot n
> BASE_CONFIG: Setting system terminal type to vt100
> BASE_CONFIG: Register postinstall script 'console' for boot n
> BASE_CONFIG: Setting NFSv4 domain
> BASE_CONFIG: Creating directory: /var/opt/sun/jet/system.add
> BASE_CONFIG: Product base_config finished
> BASE_CONFIG: Installing base_config....
> Add hosts entry for UQHN
> Add hosts entry for FQHN
> BASE_CONFIG: Product base_config started
> BASE_CONFIG: Trying to use external matrix cmd
/tmp/jet/Products/zones/empty-matrix
> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
> BASE_CONFIG: Unable to locate package.matrix file... exiting.
> BASE_CONFIG: No HW specific packages for platform SUNW,SPARC-Enterprise
> BASE_CONFIG: Trying to use external matrix cmd
/tmp/jet/Products/zones/empty-matrix
> BASE_CONFIG: External matrix cmd returned non-zero status or no entries
> BASE_CONFIG: Unable to locate patch.matrix file... exiting.
> BASE_CONFIG: No HW specific patches for platform SUNW,SPARC-Enterprise
> BASE_CONFIG: Set root password
> BASE_CONFIG: Setting netmask for primary interface
> BASE_CONFIG: Disabling power management
> BASE_CONFIG: Register postinstall script 'setupdumpdevice' for boot n
> BASE_CONFIG: Register postinstall script 'run_sshkeygen' for boot n
> BASE_CONFIG: Setting system terminal type to vt100
> BASE_CONFIG: Register postinstall script 'console' for boot n
> BASE_CONFIG: Setting NFSv4 domain
> BASE_CONFIG: Product base_config finished
> ----------------------------------------------------------
> Product modules processed, finish up installation tasks
> Creating directory: /var/opt/sun/jet/system.add/updated
> Copying file etc/jumpstart.conf to //var/opt/sun/jet/config/jumpstart.conf
> Copying file Utils/smf/jetjump.xml to //var/svc/manifest/site/jetjump.xml
> Copying file Utils/S99jumpstart to //var/opt/sun/jet/post_install/S99jumpstart
> NFS Unmounting Media Directories
> Unmounting /var/opt/sun/jet/js_media/pkg
> Unmounting /var/opt/sun/jet/js_media/patch
> Make a link to finish log...
> Updating boot-archive
> /: not a boot archive based Solaris instance
> Disable & delete SMF tag svc:/site/jetzonefinish
> Nov 10 08:38:24 tl0077 reboot: rebooted by root
>
> tl0077 console login: Nov 10 08:38:24 tl0077 syslogd: going down on signal 15
> Nov 10 08:38:24 /usr/lib/snmp/snmpdx: received signal 15
>
> [NOTICE: Zone rebooting]
>
> SunOS Release 5.10 Version Generic_141444-09 64-bit
> Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
> Use is subject to license terms.
> Hostname: tl0077
> Loading smf(5) service descriptions: 1/1
> Reading ZFS config: done.
> /var/opt/sun/jet/config/releaseinfo file unavailable
> JumpStart (/var/opt/sun/jet/post_install/S99jumpstart) started @ Tue Nov 10
08:38:37 GMT 2009
> Loading JumpStart Server variables
> Loading Client configuration file
> No more reboots required
> Running additional install files for reboot n
> NFS Mounting Media Directories
> Mounting nfs://10.100.240.100/export/install/patches on
/var/opt/sun/jet/js_media/patch
> Mounting nfs://10.100.240.100/export/install/pkgs on
/var/opt/sun/jet/js_media/pkg
> Nov 10 08:38:38 tl0077 svc.startd[20529]: system/webconsole:console failed
fatally: transitioned to maintenance (see 'svcs -xv' for details)
> BASE_CONFIG: Running 001.base_config.001.run_sshkeygen
> BASE_CONFIG: Generating ssh keys...
> BASE_CONFIG: Running 001.base_config.002.console
> BASE_CONFIG: Setting terminal type to vt100
> BASE_CONFIG: Running 001.base_config.003.run_sshkeygen
> BASE_CONFIG: Generating ssh keys...
> BASE_CONFIG: Running 001.base_config.004.console
> BASE_CONFIG: Setting terminal type to vt100
> BASE_CONFIG: Running 001.base_config.001.setupdumpdevice
> BASE_CONFIG: Unable to execute /usr/sbin/dumpadm, check Solaris version
supports dumpadm(1M)
> BASE_CONFIG: Running 001.base_config.002.setupdumpdevice
> BASE_CONFIG: Unable to execute /usr/sbin/dumpadm, check Solaris version
supports dumpadm(1M)
> NFS Unmounting Media Directories
> Unmounting /var/opt/sun/jet/js_media/pkg
> Unmounting /var/opt/sun/jet/js_media/patch
> Disable & delete SMF tag svc:/site/jetjump
> JumpStart is complete @ Tue Nov 10 08:38:51 GMT 2009
>
> --- In JETJumpStart@yahoogroups.com, "ossiltd" <peter.winterflood@...> wrote:
> >
> > created a base zone using zone_base , made client etc, after tweaking
template with name service etc.
> >
> > run jetzone on the global zone and it creates the zone ok, however.....
> >
> > a few problems hoping for some guidance on.
> >
> > 1: hosts file is full of multiple entries ie 6 lines of the same.
> >
> > i see there is a script to fix this, ie
/var/opt/sun/jet/Utils/lib/JS_merge_ipnodes, and
/var/opt/sun/jet/Utils/lib/JS_remove_host but this does not get called, cant
find where it should be called from.
> >
> > 2: we need one of those lines to be a FQDN for kerberos to function
correctly, how would you go about correcting the host file and adding a FQDN to
it.
> >
> > 3: we want to run nis and dns, however our nis finish script which works
fine in the bare metal global zone , postinstall not getting run to enable the
nis service. how have you overcome this.
> >
> > 4: adding any packages after install, as JS_get_cpu_arch does not seem to
return anything for a zone, its difficult to get a product.matrix entry to work,
hence adding any products fails to make the client as it can never get a product
list.
> >
> > 5: is there any more documentation on the jetzone stuff, beyond the sparse
comments on the supplied files.
> >
> > regards peter winterflood
> >
>
>

-----
Marty Lee                         e: marty@...
Technical Director                v: +44 845 869 2661
Maui Systems Ltd                  f: +44 871 433 8922
Scotland, UK                      w: http://www.maui-systems.co.uk

ok debugged some of this zones stuff and clearly the install is attempting to
update the hosts file with a hostname. and a hostname 3 times throughout this
install with no checks to see if it already has an entry

excerpts from the output

+ echo Populating zone tl0077 sysidcfg
Populating zone tl0077 sysidcfg
+ cp /tmp/jet.28262/Clients/tl0077/sysidcfg /zones/tl0077/root/etc/sysidcfg
+ chmod 600 /zones/tl0077/root/etc/sysidcfg
####################################################
+ echo Add hosts entry for UQHN
Add hosts entry for UQHN
+ echo 10.100.240.177 tl0077
+ 1>> /zones/tl0077/root/etc/inet/hosts
+ echo Add hosts entry for FQHN
Add hosts entry for FQHN
+ echo 10.100.240.177 tl0077.
+ 1>> /zones/tl0077/root/etc/inet/hosts
####################################################
+ echo Disable NFSv4 prompt
Disable NFSv4 prompt
+ ed /zones/tl0077/root/etc/default/nfs
+ cat
+ 0<<
1,$s/#NFSMAPID_DOMAIN=.*/NFSMAPID_DOMAIN=dynamic/g
w
q


BASE_CONFIG: Installing base_config....
+ + cd ./..
+ pwd
productdir=/tmp/jet/Products/base_config
+ + uname -p
cputype=sparc
##############################################
+ echo Add hosts entry for UQHN
Add hosts entry for UQHN
+ echo 10.100.240.177 tl0077
+ 1>> //etc/inet/hosts
+ echo Add hosts entry for FQHN
Add hosts entry for FQHN
+ echo 10.100.240.177 tl0077.
+ 1>> //etc/inet/hosts
################################################
+ [ -x /tmp/jet/Products/base_config/solaris/install ]
+ cd /tmp/jet/Products/base_config
+ ./solaris/install
+ JS_get_module_hint //var/opt/sun/jet/config base_config disable
bcdisableflag=
+ [ -n  ]
+ JS_display Product base_config started
+ [ 1 != 1 ]
+ JS_message INFO Product base_config started



BASE_CONFIG: Product base_config finished
BASE_CONFIG: Installing base_config....
+ + cd ./..
+ pwd
productdir=/tmp/jet/Products/base_config
+ + uname -p
cputype=sparc
###############################################
+ echo Add hosts entry for UQHN
Add hosts entry for UQHN
+ echo 10.100.240.177 tl0077
+ 1>> //etc/inet/hosts
+ echo Add hosts entry for FQHN
Add hosts entry for FQHN
+ echo 10.100.240.177 tl0077.
+ 1>> //etc/inet/hosts
###############################################
+ [ -x /tmp/jet/Products/base_config/solaris/install ]
+ cd /tmp/jet/Products/base_config
+ ./solaris/install
+ JS_get_module_hint //var/opt/sun/jet/config base_config disable
bcdisableflag=
+ [ -n  ]
+ JS_display Product base_config started
+ [ 1 != 1 ]
+ JS_message INFO Product base_config started


any ideas on why this is or is this a know problem with jetzones

regards peter

created a base zone using zone_base , made client etc, after tweaking template
with name service etc.

run jetzone on the global zone and it creates the zone ok, however.....

a few problems hoping for some guidance on.

1: hosts file is full of multiple entries ie 6 lines of the same.

i see there is a script to fix this, ie 
/var/opt/sun/jet/Utils/lib/JS_merge_ipnodes, and
/var/opt/sun/jet/Utils/lib/JS_remove_host but this does not get called, cant
find where it should be called from.

2: we need one of those lines to be a FQDN for kerberos to function correctly,
how would you go about correcting the host file and adding a FQDN to it.

3: we want to run nis and dns, however our nis finish script which works fine in
the bare metal global zone , postinstall not getting run to enable the nis
service.  how have you overcome this.

4: adding any packages after install, as JS_get_cpu_arch does not seem to return
anything for a zone, its difficult to get a product.matrix entry to work, hence
adding any products fails to make the client as it can never get a product list.

5: is there any more documentation on the jetzone stuff, beyond the sparse
comments on the supplied files.

regards peter winterflood