Why are my patches not in bundles?

[GXW_1]

On my ignite server I have installed FEATURE11i, HWEnable and QPKBASE and they show up fine when I do an swlist. They show up as bundles.

However, when I look at a server I built from a depot on my ignite server, I see a different picture. On there, I see no FEATURE11i, HWEnable and QPKBASE bundles at all, I just see hundreds of patches listed out individually at the end under "products not contained in a bundle".

Is this Working-As-Designed or have I done something wrong?

Here's the command I used to copy (e.g.) FEATURE11i into my depot:

swcopy -v -s /igx/patches/FEATURE11i_B.11.31.0809.326a.depot -x enforce_dependencies=false \* @ /depots/my_11iv3_Sep08

Is there another flag I need on swcopy which means "copy these as a bundle and not as individual patches"?

Any help would be appreciated. Thanks.

[Ivan Krastev]

Use the make_bundles - http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=148550


regards,
ivan

[Eric SAUBIGNAC]

Bonjour,

It should work well like this. You can check that swcopy has correctly copied the bundle with "swlist -s /depots/my_11iv3_Sep08". It should be correct.

Maybe the problem is due to the way you have followed to include this depot in the ignite configuration ?

[bright image]

You can use the software package builder (x-windows gui) to modify the contents of your depot, create bundles etc...

SPB is freely available from:

http://docs.hp.com/en/SPB/index.html

It is also very useful for creating custom depots and packages.

[GXW_1]

Thanks for the replies.

Ivan, I don't think I need to "make_bundles" as I already have the bundles.

Bright Image, thanks for the suggestion but I don't really think what I'm doing warrants use of SPB. I'm really not doing anything too far off the beaten track - its a very standard 11iv3 depot with just the 3 standard patch bundles added to it.

Eric, I tried the swlist and sure enough the 3 bundles are in there as plain as day.
As for the ignite config, again I don't really see where that can be wrong - as all it is is a make_config to make the config file which points to my depot, and a few manage_index commands to do the INDEX changes. If I was doing that bit wrong then surely the client wouldn't build at all. It does build, it's just that all the patches get taken out of the bundles and left separate for some reason.

Is it worth me posting this in the Ignite secion or do the same folks look in here as well?

[James R. Ferguson]

hI:

> Is it worth me posting this in the Ignite secion or do the same folks look in here as well?

No. The fact that this lives in the "HP-UX" family is more than sufficient to get the most attention.

Regards!

...JRF...

[Eric SAUBIGNAC]

Maybe you could check on the installed box the file /var/opt/ignite/local/install.log for any error or warning that could explain.

Something else.Don't know how you have configured the ignite server, but following your previous post I guess that you have created an entry dedicated to your patch depot. Something like :

cfg "HP-UX B.11.31 Default" {
description "This selection supplies the default system configuration that HP supplies for the B.11.31 release."
"/var/opt/ignite/config.local"
"/opt/ignite/data/Rel_B.11.31/config"
"/opt/ignite/data/Rel_B.11.31/hw_patches_cfg"
"/var/opt/ignite/data/Rel_B.11.31/core_cfg"
"/var/opt/ignite/data/Rel_B.11.31/YourBUNDLE_cfg"
}

Following this idea, you could also check that your patch bundle has been correctly selected at ignite time. Check for an entry like "init sw_sel "YourBundle"=TRUE in /var/opt/ignite/local/config

Eric

[GXW_1]

There's nothing worrying in the Ignite log, and the bundles are fine in the local config, e.g.:

init sw_sel "FEATURE11i"=TRUE

However, thats not how I configured Ignite. I don't have an extra line in the config for the bundles, I just swcopied the bundles INTO my core depot and the ignite config points to that depot. I thought that was a legitimate way of doing it?

[Eric SAUBIGNAC]

Well, don't really know what is the "legitimate" way, and even if it exists ;-)

Anyway, I create a separate depot because I prefer no to alter "official" depot created from installation DVD. So I do a make_config/manage_index operation for core OS depot then a second one for my separate depot.

You will find a recent post of my own [ from wich I still wait for answers :-( ]. http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1308169 In this tread there is an attachment that describes how I configure this. I did it successfully before for applications depot, but never tested with a patch depot. An I have a problem :-(

Just a silly question : which version of core OS do you have in your depot ? Because FEATURE11i_B.11.31.0809.326a is already included in 0908 core. Would not it be easier to create a new core depot with latest dvd ?

[bright image]

Although not ideal, a workaround for this could be to run a swinstall as an ignite post install script. (assuming a standard swinstall of the bundles works ok).

[GXW_1]

Bright Image, that would probably work fine as a workaround, but I'd rather get to the bottom of this so I understand it fully. Besides, I don't have access to the DVD drive as the box is 000s of miles away.

Eric, the attachment in your other thread is very interesting. I have a very similar situation now. I have split out the FEATURE, HWEnable and QPK bundles into a separate depot and made a separate config for it in the INDEX. All seems to work fine as I can see it in the TUI software tab prior to install, but it doesn't get installed. Subsequent swinstall of the same depot works fine too. Here's the error from my /var/opt/ignite/local/install.log:

======= 01/29/09 14:21:38 UTC BEGIN Software Install (user=root)
(jobid=000002)

* Reading Target System's Installed Product Database (IPD)
* Target IPD: mybox
* Reading Source Depot
* Source depot: 10.11.12.13:/igx/patches/depot
* Analyzing Software To Be Installed
* Creating Load Order
ERROR: No software was selected for install.
* Analysis Summary
- Reboot needed: No
- Kernel build needed: No
* Analyzing Software To Be Installed failed with 1 error.

======= 01/29/09 14:21:42 UTC END Software Install failed with 1 error.
(user=root) (jobid=000002)

Could it be something to do with the way the depot is created? I used the create_depot script supplied and it seems to have made an empty bundle called BUNDLE at the beginning of the depot? Is that suppsoed to be there?

Or is it something to do with the )=TRUE or load_with_any settings? I would have thought that if it shows up on the software tab as Marked = Yes then its good to go? And if it installs manually its in good shape too? So why does the ignite build say there's nothing to install?

[Eric SAUBIGNAC]

Slow answer, but did not want to say silly things ;-), so I did a test.

Your thinking that "I used the create_depot script supplied and it seems to have made an empty bundle called BUNDLE at the beginning of the depot?" is right. create_depot is designed to create a bundle named BUNDLE with downloaded patches. If you have also downloaded preconfigured bundles, like FEATURE11i, the newly created BUNDLE will not contained them. They will be kept as their own in the target depot. An example created with create_depot and a patch_manifest file where I discarded all stand alone patches :

# swlist -s /var/cheops/depot/depot

# Initializing...
# Contacting target "sap00"...
#
# Target: sap00:/var/cheops/depot/depot
#

#
# Bundle(s):
#

BUNDLE B.2009.01.30 Patch Bundle
HWEnable11i B.11.31.0809.326a Hardware Enablement Patches for HP-UX 11i v3, September 2008

And if you take a look at BUNDLE, you can see no product inside :

# swlist -l product -s /var/cheops/depot/depot BUNDLE
# Initializing...
# Contacting target "sap00"...
#
# Target: sap00:/var/cheops/depot/depot
#

BUNDLE B.2009.01.30 Patch Bundle

So, I suppose that the last error found is only due to the fact that BUNDLE is empty. You should remove it from your depot before creating the config file, or simply avoid to select it at ignite install time.

I suppose that if you have selected other bundles, FEATURE, HWEnable and QPK, they are now correctly installed ?

Eric

[GXW_1]

No, even though I selected them nothing got installed so I'm worse off than I was before when they WERE being installed but not in bundles!

I'll try removing the empty bundle from my depot but I'm sure that'll not make any difference.

[Eric SAUBIGNAC]

Well. I have just made a test for my other thread http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1308169 and when I remove the 2 fautives patches everything works well : my separate patches depot is now correctly installed.

So what you did should work ... but you did not answer to my silly question : which version of core OS do you have in your OE depot ?

And yes an other question : I hope you have registered your separate depot (swlist -l depot) ?

[GXW_1]

It is an old version of Core OS which is why I wanted to bring it up to date with the latest patch bundles. It is still 11iv3 obviously. I know there is an incompatibility with the difference between load_with_any ~ "HPUXBaseOS" and load_with_any ~ "OpEnvironments" but I thought once I'd worked round that the bundles would still apply.

How do I tell what version the core OS is by the way?

And yes, I have registered the patch depot.

[GXW_1]

OK, I think I'm getting closer to the answer here. First I removed the empty bundle from my depot. That didn't fix it but it can't have hurt.
The key thing I did was to upgrade Ignite to the latest available - something I should have done at the start, I know.
Anyway, the bundles apply now when I select them during the install dialog - and I mean apply as bundles as opposed to individual patches - so all is well.......
except the fact that I can't get them to install by default AND make them optional. I can either get them to be listed marked as "no" in the software tab, and manually switch that to yes, or I can use load_with_any in the cfg to force that to yes, but then if I DEselect them I get the following error:

----------------------------------
Message From: /opt/ignite/bin/itool ()
WARNING: Software selection: "FEATURE11i" cannot be deselected because either other software that is selected has a dependency on it or it is always to be loaded.
-----------------------------------

That's most likely the load_with_any to blame but I tried using "init sw_sel" instead of just "sw_sel" and that caused exactly the same problem.

Does anyone know what combination of cfg statements might get this working, and ideally, what make_config commands I can use to creat them (as I don't REALLY want to hack the cfg files)

[Eric SAUBIGNAC]

Bonsoir GXW,

Late to answer, but I am out of office from beginning of week, on a "hot" client site and have many things to do ... and no Internet connection in my hotel room :-(

Happy to see that with a separate depot, from which you have removed the empty bundle "BUNDLE", every thing goes better.

I suppose that the fact that you can't unselect "FEATURE11i" has something to deal with the fact it is already present in the OS depot AND in the separate depot, with different versions. In the OS depot, it is mandatory and sure you have dependencies with it. I don't know if you can see both versions in the selection screen. If yes, did you selected the good one ? I mean the one in the separate depot ? If you can't see both version, I am afraid you won't be able to unselect it because it is mandatory and ignite as no way do make difference between them.

May be it is just a silly idea (I have no way there to make a test), but I am pretty sure that if you create a depot of your own, that has no direct relation with the core OS depot, like FEATURE1i can have, you won't have to face such a situation. I mean you will be able to have it selected by defaut and still be able to manually unselect it.

Well, I am to return to my job ;-)