What version of SuSE are you working with?
two versions actually - 10.4 and 11.2
Thanks Bill these are great - how far back do these instructions cover?
I would love to have the client upgrade their existing BBSA install to 8.2, but it aint happening until long after this project is over. The project is specifically on BBSA version 8.1.03 (.312 I believe) - are there any gocthas or workarounds in this version related to SuSe 10 and/or 11?
The same instructions for SuSE 10 from the 8.2 docs will work for in 8.1.x. I have not tested with SuSE 11 myself, but you can give it a try as a starting point.
I can provision both but it appears that BSA is ignoring our modified autoYaSt file.
The same base install is being performed no matter what entries are made in the autoyast.
Have also seen the "Customize the AutoYaSt file" check box will some times uncheck itself between saving.
Would it be better to put the package list entries in the edit box under the OS components tab let and BSA build the file?
I've not see any issues with the UI as you describe when saving a system packae. Do you notice this with other system package types as well (if you have them) or just SuSE?
As a work around you could try using the OS Components tab as you note. Then you should see your customization in the auto-generated autoyast file preview.
We found that even if we put the packages in the os components they are
ignored. Even the disk partitioning wizard entries are being ignored.
if you check the 'customize autoyast' option then it will not pickup any changes to the rest of the system package and any changes should be made in the autoyast tab directly. is there a reason you are using the customize autoyast ?
if you want to just customze the packages being installed you should use the 'use script for os components' and put in the appropriate syntax for that section of the autoyast.xml - i don't believe you can simply insert package names there.
Initially we chose to customize the autoyast file because we had a complete
file that should have built the server to client's spec.
Found that the system is ignoring the custom file. Found out further when
we let BSA generate the autoyast it is ignoring all entries in the disk
part wizard as well (along with the os components entries)
Is there a setting we are missing that tells BSA to ignore the system
What do you mean by ‘ignoring’ ? there’s not really a way to ignore the autoyast file – does the provision fail to start because of incorrect sections ?
Can you export the system package, zip it up and attach it to this thread ?
In 8.1.x and before, if the System Package is updated for any field value, a new Job needs to be created for changes to reflect. Some fields like network settings can be overwritten in the Job, which can be directly modified in the job, thus not needing a job recreate.
Note that this behavior has been changed in 8.2, where the changes made in System Package are directly reflected in the Job for fields which are not overwritten via Job.
David, as I understand your problem is already resolved by creating a new Job, still updating the thread for others who might face similar issue.