Bug 753199
| Summary: | User's env and org should not be required in the UI | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jeff Weiss <jweiss> |
| Component: | WebUI | Assignee: | Tom McKay <tomckay> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | dajohnso, tomckay |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-22 18:06:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 747354 | ||
Specifying a default env is not required for neither orgs nor users. commit 675939678e3029f1648a3ee35e0dfa8644c9130b Merge: bd2823b 0220075 Author: Tom McKay <thomasmckay> Date: Mon Nov 14 08:43:22 2011 -0500 Verified, katello-0.1.157-1.git.3.ebc2e52.el6.noarch |
Description of problem: <jweiss> thomasmckay: looks like API can still create users without default org/env: [10:20] <jweiss> https://katello-ci-rhel6.usersys.redhat.com/katello/users#panel=user_2 <jweiss> is that a problem? <thomasmckay> jweiss: in my mind this should still be allowed, though perhaps product people might disagree? [10:21] <thomasmckay> in any case, yes that was purposefully left to be allowed <jweiss> thomasmckay: why would the UI disallow it? [10:22] <thomasmckay> because it would be best practice :) i was going by the rule of thumb, "the ui doesn't have to do everything the command line can, but it can't do more" <thomasmckay> feel free to BZ it and broader audience can discuss [10:23] <jweiss> thomasmckay: it's not a big deal, but what i'd expect is enforcement of required fields would be done below the level of the gui/api interfaces [10:24] <jweiss> the ui could support that, but i wouldn't expect it to do enforcement where the model does not [10:25] <jweiss> maybe there are already other places in the ui that do this, but i don't know of any <thomasmckay> jweiss: valid point. BZ and i will make it optional [10:26] <jweiss> thomasmckay: what happens to users who don't have org/env? [10:29] <jweiss> what are those fields used for? <thomasmckay> those are just used when a system is registered <jweiss> and if the user doesn't have a default, the system that's registering has to specify? [10:30] <thomasmckay> if org/env is not specified explicitly, then they are required to be passed in <jweiss> i see <thomasmckay> and on older sub-mgr there are no options for env/org so those systems could not be registered w/o the user specified having defaults Version-Release number of selected component (if applicable): katello-0.1.101-1.git.29.06e63e6.el6.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: