Description of problem: While creating Discovery Rule, Host Group parameter is mandatory but if any random Host Group ID is passed in hammer command creates the rule successfully. Also, if no Host Group is present and Host Group ID is provided then also Discovery Rule is created with no Host Group. [vagrant@centos7-hammer-devel ~]$ hammer -u admin -p changeme discovery-rule create --hostgroup-id 999 --locations="Default Location" --name "rabajaj" --search "last_report = Today" --organizations="Default Organization" Rule created Version-Release number of selected component (if applicable): Sat6.3 snap28 How reproducible: Steps to Reproduce: 1.hammer -u admin -p changeme discovery-rule create --hostgroup-id 999 --locations="Default Location" --name "rabajaj" --search "last_report = Today" --organizations="Default Organization" Actual results: Disocvery Rule created successfully. Expected results: Should not be created. Additional info:
Upstream fix involves creating foreign key, we are too late for this in 6.3. I am putting this onto backlog, let's deliver this in 6.4 it's not important issue.
This issue is resolved in the upstream.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.