Bug 2236212

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Hi, I have POC PR [0] that does not remove network drivers and packages,
however the problem is that the image size is now double what it has been before,
1021 MB to be specific.

@saydas
I can build the ISO for the client (based on the upstream version),
do you think that the client could try it and verify the fix?

Another discussion should be if we want to deliver the iso with WIFI
drivers to everyone, with the fact that it has double size than before.

IMHO if clients are using it to provision laptops, which is not the primary
use case of discovery-image, they should have their version of the image
with network drivers and packages specifically for this use case.

[0] https://github.com/theforeman/foreman-discovery-image/pull/163

Hello,

A) Yes, My client should be able to test with that Image ( hopefully ) if someone can give it to him. There are other affected customers present as well who might be interested in the testing

B) About the second point, Just because of that only, I recommended having a public-facing document that explains how to build\customize your own discovery image. We used to have it ( when Pulp2 was alive ) documented but then since Pulp 3 ( sat 6.10 ), it was removed.  

I completely agree that We cannot possibly expect to be able to test every hardware or hardware component with FDI So,

--> We need to set some expectations for the end-users about the default FDI we ship and the level of support RedHat can provide with it. 

--> We need to document the FDI image build\rebuild\customization process on RHEL 8, in a publicly accessible place, so that end-users can create their own version of images as per their needs.

There is an downstream documentation: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html/provisioning_guide/configuring-the-discovery-service#building-a-discovery-image

For upstream, building the image is quite easy:
On Registered RHEL8 machine (and up to date)
```
dnf install -y lorax anaconda pykickstart wget qemu-kvm '*guestf*' git
cd /root
git clone git:theforeman/foreman-discovery-image.git foreman-discovery-image-upstream
cd /root/foreman-discovery-image-upstream;mkdir result

# Build kickstart file
./build-livecd fdi-centos8.ks
# Verify that building image is working
./build-livecd-root X.Y ./result nonvirt
```

that's it, the image should be in the result folder.

And please ignore my comment about the size of the ISO, I checked the wrong file, sorry.

Hello,

We cannot recommend the upstream instructions as that is based on CentOS. 

About the downstream doc you pointed out, That is specific to Pulp2 and RHEL 7. Please see https://bugzilla.redhat.com/show_bug.cgi?id=2089339 for more context.

For downstream, Users would need to know that, on a RHEL 8 system, using lorax and RHEL downstream repos, how to build the FDI but in the BZ mentioned, It was decided to not put any additional time\effort on the same. 

Maybe it's worth reopening w.r.t our ongoing BZ situation?


-- Sayan

PR [0] with WIFI drivers and tools has been merged,
@Frank can you process with downstream release?

[0] https://github.com/theforeman/foreman-discovery-image/pull/163

Let's hold on here. 

It seems, a large initrd can cause some problems e.g. https://issues.redhat.com/browse/RHEL-4389 

While i cannot replicate this on VMs + UEFI, my customer can reproduce a similar situation on every physical system he has tried.  Perhaps the inclusion of Wifi drivers has increased the size of a the image a bit too much ?

Moving this BZ back to the ASSIGNED state as per the offline discussion that happened with Leos. We will need more time to understand how best we can create the image and test it so that we don't run into any weird issues ( e.g. https://issues.redhat.com/browse/RHEL-4389 )

Due to the issue in https://issues.redhat.com/browse/RHEL-4389, we are unable to deliver it in the 6.15

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.