Bug 1699737 - [Kubevirt-Foreman] Failed to create a compute kubevirt1 (KubeVirt) instance test-api-host.example.com: undefined method `+' for nil:NilClass
Summary: [Kubevirt-Foreman] Failed to create a compute kubevirt1 (KubeVirt) instance t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - CNV
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Shira Maximov
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-15 06:30 UTC by Vatsal Parekh
Modified: 2019-10-22 19:48 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-foreman_kubevirt-0.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:48:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github masayag foreman_kubevirt pull 78 0 None None None 2019-04-23 04:56:48 UTC

Comment 3 Moti Asayag 2019-04-23 04:56:48 UTC
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.

Comment 6 Shira Maximov 2019-04-28 07:38:58 UTC
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 7 Lukáš Hellebrandt 2019-04-29 07:47:55 UTC
I suppose the needinfo was meant for vatsal, not me.

Comment 9 Bryan Kearney 2019-10-22 19:48:11 UTC
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


Note You need to log in before you can comment on or make changes to this bug.