Remove backend widget status #4418
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Katello 4.18+ does not provide the Backend System Status widget anymore. The code was moved to Foreman and will be part of Foreman 4.17+. Refs PR 11473 in katello Refs PR 10651 in foreman Refs Redmine issue 38667 (Extend Backend system status widget) Refs Redmine issue 38668 (Remove Backend System Status widget)
github-actions
bot
added
Needs tech review
|
The PR preview for d5f3242 is available at theforeman-foreman-documentation-preview-pr-4418.surge.sh The following output files are affected by this PR: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are you introducing?
Rephrase procedure to check the status of Foreman/Katello because the widget is gone from Katello 4.18 and not yet part of Foreman 3.16.
If you think that it's essential to show the procedure multiple times, then I will revert the change that drops the context attribute & readd it.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
As of now, the procedure does not work for Foreman 3.16/Katello 4.18. I know that the PR is against "master".
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
I made a suggestion to cherry-pick from develop to 3.16 in foreman prior to the 3.16.1 release. This would require a small rework of my PR.
Foreman Community Forum: comment on Release Meeting 2025-10-22
Contributor checklists
Please cherry-pick my commits into: