11.23 Golden Image not available via configuration tab

[Berd]

I have been working on creating 11.11 and 11.23 Golden Images to aid with the building of servers.

I have successfully followed the Ignite documentation to create a 11.11 Golden Image, creating all the necessary config files, updating my INDEX file and finally utilised the image successfully.

I then followed the same process to generate a 11.23 Golden Image. Yet when I use the Ignite GUI to rebuild a server, the 11.23 image is not visible as a option on the 'Configuration' tab. I have confirmed that my config files are ok by running instl_adm -T.

Any ideas ?

Regards,
Berd

[Steven E. Protter]

Shalom Berd,

Probably an error in the INDEX file or permissions referred to in the INDEX file.

It would probably be useful if you posted the INDEX file.

SEP

[Berd]

Hi Steven,

Here's the contents of the INDEX file

cfg "HP-UX B.11.00 Default" {
description "This selection supplies the default system configuration that HP supplies for the B.11.00 release."
"/opt/ignite/data/Rel_B.11.00/config"
"/opt/ignite/data/Rel_B.11.00/hw_patches_cfg"
"/var/opt/ignite/config.local"
}
cfg "HP-UX B.11.11 Default" {
description "This selection supplies the default system configuration that HP supplies for the B.11.11 release."
"/opt/ignite/data/Rel_B.11.11/config"
"/opt/ignite/data/Rel_B.11.11/hw_patches_cfg"
"/var/opt/ignite/config.local"
}
cfg "HP-UX B.11.11 Golden Image" {
description "Golden Image created 19th Feb 2007"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/opt/ignite/data/Rel_B.11.11/core_archive_cfg"
"/opt/ignite/data/Rel_B.11.11/passanda_patch_cfg"
"/var/opt/ignite/config.local"
}
cfg "HP-UX B.11.23 Golden Image" {
description "Golden Image created 20th Feb 2007 "
"/opt/ignite/data/Rel_B.11.23/config"
"/var/opt/ignite/data/Rel_B.11.23/core_archive_cfg"
"/var/opt/ignite/config.local"
}
cfg "HP-UX B.11.23 Default" {
description "This selection supplies the default system configuration that HP supplies for the B.11.23 release."
"/opt/ignite/data/Rel_B.11.23/config"
"/opt/ignite/data/Rel_B.11.23/hw_patches_cfg"
"/var/opt/ignite/config.local"
}
cfg "2006-11-27,08:23 Recovery" {
description "Recovery Archive"
"/var/opt/ignite/clients/0x00306E4A2D3D/recovery/2006-11-27,08:23/system_cfg"
"/var/opt/ignite/clients/0x00306E4A2D3D/recovery/2006-11-27,08:23/control_cfg"
"/var/opt/ignite/clients/0x00306E4A2D3D/recovery/2006-11-27,08:23/archive_cfg"
"/var/opt/ignite/saved_cfgs/2006-11-27,08:23_Recovery_Archive"
}

Regards,
Berd

[Scot Bean]

INDEX file looks OK to me. The problem must be in your custom config file

"/var/opt/ignite/data/Rel_B.11.23/core_archive_cfg"

The syntax that creates the menu item is "sw_sel". Make sure the names and titles in there are unique. If you are like me and re-use files, maybe the names are the same.

[Berd]

Scot,

Not sure what you mean ? Here's a subset of my /var/opt/ignite/data/Rel_B.11.23

########################################################################
# File: B.11.23.golden_image.cfg
#
# This one configuration file will be used to define all Ignite-UX needs
# to know about a golden image archive.
########################################################################

########################################################################
# Define where our software comes from.
#
# "sw_source" - defines the method you will use to access a
# "source of software" (i.e. either an "SD depot"
# or an "archive")
########################################################################
sw_source "golden image archive" {
description = "YELL HP-UX Golden Image Archive - 11.23"
load_order = 0
source_format = archive
source_type = "NET"

# When using this configuration file with a tape or CD-ROM where the
# archive is on the same piece of media, uncomment the next line to
# prevent a prompt to change media during installation.
# change_media=FALSE

# The following 2 scripts should be reviewed to see if the defined
# defaults are applicable. If you need to modify them, copy them
# to /var/opt/ignite/scripts first and change the paths here.
post_load_script = "/opt/ignite/data/scripts/os_arch_post_l"
post_config_script = "/opt/ignite/data/scripts/os_arch_post_c"

# If nfs_source is used, be sure to export the source.
nfs_source = "10.200.2.208:/var/opt/ignite/archives/Rel_B.11.23"
}########################################################################
# Define the archives.
#
# "sw_sel" - Each of these defines a software object (such as an
# archive) which can be obtained via methods defined in the
# "sw_source" stanza above.
#
# Note: Remove the stanza below that will not be used by the golden
# image archive. For example, if your golden image archive
# is specific to PA-RISC systems, remove the "is_ia64" stanza
# below.
########################################################################
#-----------------------------------------------------------------------
# The IA archive
#-----------------------------------------------------------------------
(is_ia64) {
init sw_sel "B.11.23 IA golden image archive" {
description = "YELL - B.11.23 IA golden image archive"
sw_source = "golden image archive"
sw_category = "HPUXEnvironments"
archive_type = gzip tar

# For NFS, the path to the archive is relative to the mount point
# specified in the "nfs_source" keyword within the sw_source stanza
# above:
archive_path = "yell_golden_11.23_image.gz"

# Here we describe how much space is used in each of the mentioned
# subdirectories. This information is obtained by running the
# "archive_impact" command against an archive as follows:
# /opt/ignite/lbin/archive_impact -tg B.11.23_archive_IA.gz
# The output from the above command should replace the "impacts"
# statements below.
#
impacts = "/" 17Kb
impacts = "/.ssh" 4Kb
impacts = "/dev" 12Kb
impacts = "/etc" 192517Kb
impacts = "/home" 46Kb
impacts = "/opt" 2654313Kb
impacts = "/sbin" 109838Kb
impacts = "/stand" 29292Kb
impacts = "/usr" 1616981Kb
impacts = "/var" 1300785Kb
impacts = "/yputils" 303Kb
} = TRUE
}


#-----------------------------------------------------------------------
# The PA archive
#-----------------------------------------------------------------------
(is_hppa) {
init sw_sel "B.11.23 PA golden image archive" {
description = "YELL - B.11.23 PA golden image archive"
sw_source = "golden image archive"
sw_category = "HPUXEnvironments"
archive_type = gzip tar
archive_path = "yell_golden_11.23_image.gz"

#
# Here we describe how much space is used in each of the mentioned
# subdirectories. This information is obtained by running the
# "archive_impact" command against an archive as follows:
# /opt/ignite/lbin/archive_impact -tg B.11.23_archive_PA.gz
# The output from the above command should replace the "impacts"
# statements below.
#
impacts = "/" 17Kb
impacts = "/.ssh" 4Kb
impacts = "/dev" 12Kb
impacts = "/etc" 192517Kb
impacts = "/home" 46Kb
impacts = "/opt" 2654313Kb
impacts = "/sbin" 109838Kb
impacts = "/stand" 29292Kb
impacts = "/usr" 1616981Kb
impacts = "/var" 1300785Kb
impacts = "/yputils" 303Kb
} = TRUE
}

Which 'names' maybe duplicated ?

From reading other threads on the ITRC I'm a little unclear on my understanding of how Ignite functions. Would I be correct in saying that both 11.11 and 11.23 Golden Images should be visible via the configuration button on the basic tab of the gui ?

Some threads suggest the O/S version is driven via the host being recovered during the initial boot ?

Regards,
Berd

[Scot Bean]

Looks like unique selection titles, such as:
init sw_sel "B.11.23 IA golden image archive"

I would try 2 simplifications to see if you can get these visible

1. For now, remove the conditional wrappers is_ia64 and is_hppa

2. Remove the 2 default selections =TRUE at the end of each section.

If this works, then experiment by putting these back one at a time. Having 2 TRUEs may be an issue. Also the target machine gets involved in the other options.

Continue to run instl_adm -T when making changes.

[Berd]

Found the error of my ways.

There was no issue with the 11.23 Golden Image, or the manner in which I configured Ignite. The image will not be visible on the Ignite GUI Basic Confiurations tab until the point at which you issue your bootsys command. You then tell Ignite to boot with the B.11.23 INTALL/WINSTALL file, adn then when the server gets to the Ignite display you will see the 11.23 Golden Image as a visible configuration.

I was trying to confirm my setup to early in the process.

Many thanks for your input, I now have a better understanding of how Ignite functions.

Regards,
Berd