Description of problem: Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. In this page https://beaker-devel.app.eng.bos.redhat.com/view/dev-kvm-guest-01.rhts.eng.bos.redhat.com#access-policy 2. Add 1 valid group 3. Add 1 non-existent group 4. Choose some 5. Click Save changes Actual results: No error report during these action. For group section, here're some logs capture from server-debug.log Jan 17 07:27:44 beaker-devel.app.eng.bos.redhat.com beaker-server[3082]: bkr.server.model.activity DEBUG Tentative SystemActivity: object_id=14L, service=u'HTTP', field=u'Access Policy Rule', action=u'Added', old=None, new='<grant view to dowang-test-displayname>', user=dowang Jan 17 07:27:44 beaker-devel.app.eng.bos.redhat.com beaker-server[3082]: bkr.server.model.activity DEBUG Tentative SystemActivity: object_id=14L, service=u'HTTP', field=u'Access Policy Rule', action=u'Added', old=None, new='<grant view to abcd-list>', user=dowang Jan 17 07:27:44 beaker-devel.app.eng.bos.redhat.com beaker-server[3082]: bkr.server.wsgi DEBUG Rolling back for 400 response It's not real add access policy. Expected results: Like only add a non-existent group or user, give some error message. Additional info: I think it would be better when user want to add a non-existent user/group, the '+Add' button should not clickable.
Same steps for add non-existent user.
I can reproduce it now. The good thing is that the invalid user/group is not saved in the backend if the user adds another user/group straight after saving and without a reload of the view. The bad thing is, that valid user/group entries are also not saved :(
(In reply to Roman Joost from comment #4) > I can reproduce it now. The good thing is that the invalid user/group is not > saved in the backend if the user adds another user/group straight after > saving and without a reload of the view. The bad thing is, that valid > user/group entries are also not saved :( Can we just allow user add valid user/group. Because that textbox can list valid value.
Issue still applies. Valid entries are not removed as Roman says but there really is no error message for invalid entries if you don't refresh the page.
Hello, thank you for opening issue in Beaker project. This issue was marked with component "web ui". As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX. New UI will be reimplemented within new versions of Beaker. If you have any questions feel free to reach out to me. Best regards, Martin <martin.styk>