Multiple Ignite Images?

[Ed Melosh]

Here is the situation - I have an ignite server with different ignite images stored on it. When igniting a client and I select the B image, the client is ignited but the 'A' image is installed first and then the 'B' image is laid down on top of the 'A'. Is this the way it supposed to work? I wouldn't think so but if I remove the 'A' archive file from the system, then the install goes properly. Any thoughts?

[Steven E. Protter]

instl_adm -T

take a look at those configuration files. I think something is pointing the wrong way.

I think you should be able to set it up so you get one ignite golden image to install. Thats how it worked with us. We had multiple images, but there was no overlay ocurring.

SEP

[Scot Bean · Accepted solution]

Examine the main config file, /var/opt/ignite/INDEX.

Do any of the stanzas in this file run together, when they should be seperate?

This is not how it's supposed to work.

However, depending on what you are igniting, and how it is setup, different images can sometimes share a depot or config files.

Tell us more about what A & B contain.

[Bharat Katkar]

I doubt if you have config files already there for your clients on Ignite Server.

Check /var/opt/ignite/clients dir to see what exactly they say.

When you are selcting Image B then only Image B should get installed. WHat is happening is not the correct way.

Hope that helps.
Regards,

[Ed Melosh]

Upon further investigation, it appears that the problem lies in the /var/opt/ignite/data/Rel_B.11.00/core_700_archive_cfg file. I must have something wrong in the syntax calling out two different images. Does anyone have an example of their config file where it calls out 2 or more images available for install?