Hide Forgot
Description of problem: When testing bug #1183196, I inadvertently tried creating org, associating it with a subnet that did not exist. When this occurs, user gets an error message that seems to have nothing to do with the subnet. Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-7-20150303.0 How reproducible: Steps to Reproduce: 1. Create capsules/smart proxiess; furthermore, create only one subnet. Or create zero, and modify hammer command below accordingly. 2. Attempt to create an org: hammer organization create --description "eeee" --name "eeee" --smart-proxy-ids=2 --domain-ids 1 --subnet-ids 1,2 3. View results Actual results: [root@rhsm-qe-2 ~]# hammer organization create --description "eeee" --name "eeee" --smart-proxy-ids=2 --domain-ids 1 --subnet-ids 1,2 [Foreman] Username: admin [Foreman] Password for admin: Could not create the organization: Resource organization not found by id '' Expected results: An error message that makes more sense -- "No subnet found for id '2'" or whatever Additional info:
Per 6.3 planning, moving out non acked bugs to the backlog
Created redmine issue http://projects.theforeman.org/issues/16846 from this bug
The actual output is slightly changed, but it still says doesn't make much sense. $ hammer organization create --description "eeee" --name "eeee" --smart-proxy-ids=1000 --domain-ids=5000 Could not create the organization: no resource loaded
here are we expecting a generic error message statement or error specific to a specific parameter wrongly passed, as the current message is generic for any resource not found, maybe we can revise the error message from "no resource loaded" to something like "some of the attribute values are inappropriate."
Does the above ^^ message seems valid, if so I can make necessary changes to fix it.
Can you tell which ones passed in are invalid? That would be the most helpful.
This issue is been merged in the upstream branch.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16846 has been resolved.
The fix to this bug will be delivered with release 6.3 of Satellite.