Project

General

Profile

Actions

Bug #16846

closed

Org create returns unclear message when trying to assign a non-existent subnet

Added by Adam Ruzicka about 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1199604

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:


Related issues 3 (0 open3 closed)

Related to Foreman - Bug #16813: Confusing error message on association not found errorClosedMarek Hulán10/06/2016Actions
Related to Katello - Bug #18063: Org create returns unclear message when trying to assign a non-existent subnetClosedAmit Karsale01/13/2017Actions
Related to OpenSCAP - Bug #18501: Tests broken after recent change in coreClosedOndřej Pražák02/14/2017Actions
Actions

Also available in: Atom PDF