Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle disabled and failing add-ons #2988

Merged
merged 2 commits into from
Nov 12, 2020

Conversation

poncovka
Copy link
Contributor

If the add-on started by the start-module script fails before the
timeout of sixty seconds, return its exit status. Otherwise, return zero.

If the add-on fails to start, just remove it from the list of available modules
and continue. Don't abort the whole installation because of that.

This will allow the kdump add-on to refuse to run its DBus module if it is
not enabled via the inst.kdump_addon boot option.

@poncovka poncovka added the master Please, use the `f39` label instead. label Nov 11, 2020
@poncovka poncovka force-pushed the master-support_disabled_addons branch from dc560a5 to ffad7b2 Compare November 11, 2020 17:18
VladimirSlavik
VladimirSlavik previously approved these changes Nov 12, 2020
Copy link
Contributor

@VladimirSlavik VladimirSlavik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thank you!

jkonecny12
jkonecny12 previously approved these changes Nov 12, 2020
Copy link
Member

@jkonecny12 jkonecny12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Nice improvement with the timeout!

If the Python module started by the start-module script fails before the
timeout of sixty seconds, return its exit status. Otherwise, return zero.

This will speed up the propagation of the error to the boss. Otherwise,
we wait for the timeout of service_start_timeout defined by the Anaconda
message bus.

The start-module script runs in a separate process and doesn't block the
message bus, the boss or the installer.
If the add-on fails to start, just remove it from the list of available modules
and continue. Don't abort the whole installation because of that.

This fix will allow the kdump add-on to refuse to run its DBus module if it is
not enabled via the inst.kdump_addon boot option.
@poncovka
Copy link
Contributor Author

Rebased to fix the tests.

@poncovka poncovka merged commit 8b89aca into rhinstaller:master Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master Please, use the `f39` label instead.
3 participants