Never mind! We were able to identify the root cause. It’s to do with translations and how the value is passed to the API from the translated UI. Thanks for raising this @siriwliw !
Thank you for the time you gave me to solve this bug.
So, do I need to update my server to apply the latest correction ? Or just modify these files “ContentViewsConstants.js” “component_view_presenter.rb” as indicated in this Github link : https://github.com/Katello/katello/pull/9859/files ?
The javascript part of the patch might not help locally as installed katello instances use a pre-compiled version. However, the .rb file changes should be ok to apply and restarting the server should bring in that fix. The .rb fix should unblock you while 4.3 is packaged and goes GA.
We’re also targeting a larger patch around the same to take translations into account in 4.3.1.
@siriwliw : Just remembered a more straight-forward way to get you unblocked.
The old UI is still available at https://yourserver.com/legacy/content_views .
You can use that for this particular task while we get the fix released in 4.3 GA.