Now that Foreman 3.17 has a release candidate, this is the place to provide your feedback, whether it’s (possible) bugs, thoughts, the interface, or workflow. If you’re sure it’s a bug, a new Redmine issue can also be used.
A bit late but anyways!
Poked a bit around in Foreman + Katello, and everything seems to work well so far ![]()
The only things to note were the following, these are all no bugs but rather thoughts for feature enhancements.
-
The new improved notification panel is not able to be hidden by clicking anywhere else beside the notification panel. Maybe intentional, still wanted to point it out

-
And, the bulk actions for host overview page, isn’t this a bit confusing to have 2 panels for bulk actions?
Can surely also create issues for these if wanted ![]()
Cheers, Lukas
Thank you for sharing your thoughts on 3.17. Could @MariaAga and/or @jeremylenz chime in here, please?
The idea is that the “Schedule a Job” one is all remote execution-centered, and those are the REX jobs you can trigger. While the kebab (three dots) is other actions, that happen mostly on the server. This isn’t entirely consistent, however, since package and errata installs are also REX jobs.
cc @MariSvirik
Ah okay got it ![]()
for me that I know it now, doesn’t really matter, though the kebap menu seems a bit hidden, if there is also the big button for the REX stuff on top ![]()
The point for having 2 sections was to divide these actions (we had like 30 at the beginning) so users wouldn’t be overloaded (there are 2 sections in the old UI as well, I think)
Jeremy is correct, the upper ones are REX-related (more advanced or generic).
Packages and errata actions should be in the content section. Also, these actions take place in the modal on the All host page, like all the other actions in the kebab.
We have been teaching users to be aware of kebab actions in the toolbar that are connected to the table across the Foreman, so I think we are not really hiding anything, and it’s just a matter of getting used to it.
I hope this helps a bit. Thank you for raising your concerns.
