Description of problem: Summit 2017 Satellite lab Feedback - User should be warned if space(s) is prefixed in Discovery Rules -> Search field Version-Release number of selected component (if applicable): Satellite 6.2.9 How reproducible: Always Steps to Reproduce: 1. Navigate to Satellite UI -> Configure -> Discovery Rules. Create a new Discovery rule. 2. Trigger a user error scenario in which a space is prefixed in the Discovery Rule -> Search field - something like ` name~mac*` 3. Provision a host via pxe and check if auto provisioning works Actual results: Auto provisioning does not work when search field had space prefixed (by mistake) Expected results: Warn the user if any input field is prefixed with space(s) Additional info: This may be applicable to all Settings field and not Discovery alone.
I feel we should strip the spaces rather than displaying an error, what is your say lukas , sthirugn ?
Ah! i see, one space is maditory. I guess then handling it on the client side would be appropriate.
It's not mandatory, but users tend to press space in order to get dropdown helper, maybe stripping is better. We can also add model validator on top of that to make sure space won't sneak in via API.
I am unable to re-produce this bug on upstream. As I am looking into the database, the search field is already stripped.
Thanks please re-test.
Verified on snap-10, created a rule of " name = foobar" and it gets saved as "name = foobar"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. > > > > For information on the advisory, and where to find the updated files, follow the link below. > > > > If the solution does not work for you, open a new bug report. > > > > https://access.redhat.com/errata/RHSA-2018:0336