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.
Vatsal, note that since the is a map that can list several pvcs, it should be provided as one.
Therefore instead of:
"volumes_attributes" : {"name":"gluster-default-volume", "capacity":"1"}
The expected is:
"volumes_attributes": {
"0": { "storage_class": "gluster-default-volume", "capacity": "1"}
}
With recent fix, if capacity is not provided, an exception will be thrown with a clear message.
vatsal,
According to the error, you are using a wrong subnet ID:
Key (subnet_id)=(2) is not present in table "subnets"
please, try again with subnet id that exists.
Comment 7Lukáš Hellebrandt
2019-04-29 07:47:55 UTC
I suppose the needinfo was meant for vatsal, not me.
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
Vatsal, note that since the is a map that can list several pvcs, it should be provided as one. Therefore instead of: "volumes_attributes" : {"name":"gluster-default-volume", "capacity":"1"} The expected is: "volumes_attributes": { "0": { "storage_class": "gluster-default-volume", "capacity": "1"} } With recent fix, if capacity is not provided, an exception will be thrown with a clear message.