Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionLukáš Hellebrandt
2018-05-28 14:24:11 UTC
Description of problem:
'hammer compute-resource create' command doesn't support specifying Quota ID as WebUI does.
Version-Release number of selected component (if applicable):
Tested with Sat6.4, Hammer 0.13.0
How reproducible:
Deterministic
Steps to Reproduce:
hammer compute-resource create --help | grep -i quota
Actual results:
No --quota or similar parameter
Expected results:
Quota should be specifiable
Comment 6Lukáš Hellebrandt
2018-07-16 09:58:25 UTC
FailedQA with Sat 6.4 snap 12.
The Quota isn't set by either 'hammer create' or 'hammer update'. The field is left empty. This might be caused by bug 1583243 still not being fixed. Anyway, the result is that the Quota can't be set by Hammer in the current snap -> failed.
Comment 7Lukáš Hellebrandt
2018-07-16 10:00:50 UTC
Moving to on_qa because the bug it depends on is also on_qa.
Please note - ovirt-quota expects an id and not a name.
There is an RFE to change that but this is currently the expected behavior.
Comment 11Lukáš Hellebrandt
2019-05-29 12:57:13 UTC
Verified with Sat 6.6 snap 4.
It is possible to set Quota for a new CR, it is possible to update Quota in an existing CR. It is possible not to set any Quota (so default Quota is used).
To get Quota ID, I ran ovirt-shell in the RHEV server's command line and inside, I ran "list quotas --parent-datacenter-name <datacenter-name>".
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3172