Red Hat Bugzilla – Bug 636565
RFE: needs install machine only with @base group
Last modified: 2018-02-05 19:41:31 EST
Description of problem:
We need install machine only with @base + needed beaker packages and not any other, without needs of own kickstart.
Beaker installs more packages than its in @base group.
When we schedule single task and beaker machine is installed then there are many groups in section %packages of file /root/cobbler.ks
there is option in Makefile to have ability to install only @base / @core group.
@echo "Requires: @base" >> $(METADATA)
and that's it
it blocks our testing of missing dependencies 627859#c9
Having own kickstarts for each rhel distro is too much maintaining.
(In reply to comment #0)
> Expected results:
> there is option in Makefile to have ability to install only @base / @core
In my opinion, it should not be an option of our tests, it should be a parameter to /distribution/install, or maybe some attribute of recipe/packages.
The business justification for this RFE is that we just had a false positive while testing Satellite because we had an extra package installed which happened to address certain issue. But the customer will not have that package installed because it was not pulled in via Required for our packages -- it was just there already.
That's why we need to be able to get the distribution as bare as possible (while understanding that the beaker client side requirement will need to be there).
I'm trying to figure out how to make two groups happy. The desktop group requested that these be there for the default install. They argue that the automated install should act like the default manual install.
I'm cc'ing firstname.lastname@example.org to see if he has any suggestions.
(In reply to comment #3)
> I'm trying to figure out how to make two groups happy. The desktop group
> requested that these be there for the default install. They argue that the
> automated install should act like the default manual install.
> I'm cc'ing email@example.com to see if he has any suggestions.
So is this configured in beaker or is that kickstart configuration in the lab which defines the groups?
I can imagine we could start our tests with
but the problem is that <packages> only add, not override the default group selection. So if there was some other tag (or attribute to packages) which would allow us to override the default, that would be completely sufficient.
If on the other hand, if it's distro/kickstart configuration in the lab, maybe new set of kickstart/distros would be created, and we would simply /distribution/install RHEL5-Server-U5-base instead of RHEL5-Server-U5.
I've added this as an item to bring up in the stake holder meeting.
Fix seems to be quite simple from my point of view, thanks to cheetah. Is it problem to add some kind of ks_meta in sort of "suppress-desktop" to omit these packages?
Question is what's reasonable default. In my opinion it is @base and "enable-desktop" ks_meta as option.
And when implementing this RTT would really appreciate also existence of ks_meta like "packages-empty" for clean/(or no) %packages section
It is simple, the hard part is nailing down all the different combinations and getting sane defaults.
I think I need to create a table to see all the combinations. Adding in Cameron to this ticket so its not a surprise.
I also need only @core and @base groups when running reserve workflow.
I install additional packages manually afterwards.
Installing only these groups would trim installation times to absolute minimum (it takes about 5 minutes to install minimal rhel5 to a xen PV guest...).
just a note regarding to @base group. As far as I know Fedora intentionally does not contain @base anymore and there's new @standard group. So desired default installation may vary on different distributions.
What's the status here?
(In reply to Orion Poplawski from comment #11)
I'm not sure what happened to the bug state here, but this was indeed fixed a long time ago in Beaker 0.6.11.
Beaker populates %packages with only the packages required by the tasks in the recipe, nothing more. Anaconda implicitly adds @core so that you get a kernel and whatnot. For manual reservations (no recipe) Beaker instead puts %packages --default, which gives you the same package set as a human clicking through the graphical install.
As a compromise the dependencies that were previously hardcoded in the kickstart are now listed as requirements of /distribution/install. It's not an ideal solution (it's difficult for us to ever remove them now, because of the breakage it would cause) but it means you can opt out of /distribution/install or use an alternative version without the heavy requirements.
Ah, I just noticed that this bug is on the wrong product, which must be why you were pinging it Orion :-)
Actually some of these additional packages are added by /distribution/install task which is now part of beaker and it is added to each recipe by default:
So this bug might be considered fixed in same way as still present. ;)
Luckily /distribution/install isn't much important or useful and it can be removed from the job without significant impact (/distribution/dummy can be placed instead of it to keep the results "nice"). Command line tools have option for this. Anyway this is just a workaround and as such it does not have to satisfy all the users.