Howdie! I've been working on a build of BSA for provisioning but I'm running into a weird issue. Here's what I'm working with:
Sun SunFire X4100
4x quad-core CPU
4x 279GB HDD
Red Hat Enterprise Linux 6.1 (64bit)
BladeLogic Server Automation 8.3 (8.3.00)
Oracle Database 11gR2 patch-set 3 (184.108.40.206)
I've installed Linux with a minimal install and added the required packages after. I installed Oracle Database and ran all of the necessary scripts to populate the tablespace. Then I install BSA and everything appears to work properly. Here's where there's a problem:
1) When I click on Configuration->Provisioning Configurations and add a new OS type it works fine, but using that to create a System Package produces no OS components.
If I use the default SLES 11 provisioning configuration then I get OS components, like below, but this does not allow me to maintain multiple versions of the same OS (SLES 11.1, SLES 11.2, 32bit, 64bit, etc...). This issue proves true for all OS types that I try to create.
2) My second issue is that when I customize this system package, the ??DATA_STORE_IP?? value is never added to the autoyast or kickstart files that get passed to the client. The result is that I get an entry like "http:///redhat6/rhel61-x86_64" instead of "http://10.10.10.10/redhat6/rhel61-x86_64", and the systems won't provision unless I write a script to modify the file before it serves it to the client (which is a window of about 30 seconds when using Skip-Linux).
I have tried re-installing all components from the OS to the database to the application server over 20 times and I can't get it working right. Conversely, I have installed this in a VM under ESXi (running on Dell servers) and I can't get the VM to behave this way... the VM's work perfectly without flaw, but this system doesn't work. My VM's are running the same software versions and patch levels. Has anyone ever seen this sort of issue before?
3) The last issue with this server is that the Application Server fails to start when the system starts. If I disable blprocserv and blpxe then the appserv service will start automatically, but it fails when all services are enabled because one of the other services opens port 9750 before the Application Server finishes starting up. I don't have this issue when installed on the Dell or VM instances either