Bug 2175229

Hi, just giving an update this is going to be delivered by upstream PR:
* https://github.com/oamg/leapp-repository/pull/1081

The solution expect creation of custom actor that generates required msgs to
* install the package inside the target userspace container (TargetUserspaceUpgradeTasks)
* install the package on the system during the upgrade (RpmTransactionTasks)
* install the driver inside the upgrade initramfs (UpgradeInitramfsTasks)
* install the driver inside the target initramfs - for the upgraded system (TargetInitramfsTasks

The example below expects the custom repository is defined alraedy inside
    /etc/leapp/files/leapp_upgrade_repositories.repo


Disclaimer:
The code of a possible custom actor below is untested and I am appending it here just to provide
a picture how this could be in future (most likely) solved with the upcoming changes. It's still
possible that some changes could happen yet before the release, but currently this is what we expect.

It seems little bit longer due to number of comments as I prepared it for the possible future template
for other similar cases. I understand that better would be the possibility to configure just configure
the upgrade in this case, but that's plan for another future feature.

~~~
from leapp.actors import Actor
from leapp.models import (
    KernelModule,
    RpmTransactionTasks,
    TargetInitramfsTasks,
    TargetUserSpaceUpgradeTasks,
    UpgradeInitramfsTasks
)
from leapp.tags import ChecksPhaseTag, IPUWorkflowTag


class AddKernelDriverArcmsr(Actor):
    """
    Install the driver arcmsr driver during the upgrade

    Install the arcmsr kernel module in the upgrade & target initramfs.
    In this scenario it requires the package with the module is installed
    on the target system and inside the target userspace container.

    In case of the scenario when the module should be copied from a directory
    existing on the host system, specify the path from where it should
    be copied/installed instead, e.g.:
        KernelModule(name='arcmsr', module_path='/path/to/the/module')
    """

    name = 'addkerneldriverarcmsr'
    consumes = ()
    produces = (RpmTransactionTasks, TargetInitramfsTasks, TargetUserSpaceUpgradeTasks, UpgradeInitramfsTasks)
    tags = (IPUWorkflowTag, ChecksPhaseTag)

    def process(self):
        # IMPORTANT: For these package installations the (custom) repository
        # must be enabled! Ideal solution is to define the repos inside the
        # /etc/leapp/files/leapp_upgrade_repositories.repo file or using the
        # --enablerepo option when running leapp.
        # this will create task to install the package with desired driver
        # into the target userspace container
        self.produce(TargetUserSpaceUpgradeTasks(install_rpms=['kmod-arcmsr']))

        # and we want the package to be installed also during the upgrade,
        # so the driver can be used also on the upgraded system
        self.produce(RpmTransactionTasks(to_install=['kmod-arcmsr']))

        # this will require installation of the module in the upgrade and the
        # target initramfs
        k_module = KernelModule(name='arcmsr')
        self.produce(UpgradeInitramfsTasks(include_kernel_modules=[k_module]))
        self.produce(TargetInitramfsTasks(include_kernel_modules=[k_module]))
~~~

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

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 "RHEL-" 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.