Bug 1670016
| Summary: | Storage profile provisioning fails due to vmodl.fault.InvalidArgument | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Jaroslav Henner <jhenner> | ||||
| Component: | Provisioning | Assignee: | Adam Grare <agrare> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jaroslav Henner <jhenner> | ||||
| Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | ||||
| Priority: | medium | ||||||
| Version: | 5.10.0 | CC: | dmetzger, jhardy, jhenner, obarenbo, simaishi | ||||
| Target Milestone: | GA | ||||||
| Target Release: | 5.11.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 5.11.0.2 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-12-12 13:35:20 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low. A general system error occurred: PBM error occurred during PreCloneCheckCommonCallback: Fault cause: vmodl.fault.InvalidArgument
;
Profile (pbm.profile.ProfileId) {
dynamicType = null,
dynamicProperty = null,
uniqueId = e4077d94-c627-11e5-9912-ba0be0483c18
} is not a requirement policy: (pbm.profile.CapabilityBasedProfile)
This error is straight from VMware, it looks like you selected an invalid profile.
Can you try picking a profile from "VM Storage Policies" and not "Storage Policy Components"? (See the "Policies and Profiles" section on the vsphere web client).
Looking at a recent SPBM SDK doc, it seems they added a new type of storage policy which cannot be added to VMs or disks as of vSphere 6.5: DATA_SERVICE_POLICY Indicates a data service policy that can be embedded into another storage policy. Policies of this type can't be assigned to Virtual Machines or Virtual Disks. Since 6.5 https://vdc-repo.vmware.com/vmwb-repository/dcr-public/da47f910-60ac-438b-8b9b-6122f4d14524/16b7274a-bf8b-4b4c-a05e-746f2aa93c8c/doc/pbm.profile.CapabilityBasedProfile.ProfileCategoryEnum.html I'll update our collector code to ignore these types. New commit detected on ManageIQ/manageiq-providers-vmware/master: https://github.com/ManageIQ/manageiq-providers-vmware/commit/8f07f66b6f8c285f5b0e6f456edce881d8dd01aa commit 8f07f66b6f8c285f5b0e6f456edce881d8dd01aa Author: Adam Grare <agrare> AuthorDate: Mon Apr 22 13:09:23 2019 -0400 Commit: Adam Grare <agrare> CommitDate: Mon Apr 22 13:09:23 2019 -0400 Don't collect storage profiles which can't be used Storage profiles in the DATA_SERVICE_POLICY category cannot be added to virtual machines or virtual disks. They can only be embedded in other storage profiles. Since we don't create/edit storage profiles we don't need to collect these. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1670016 app/models/manageiq/providers/vmware/infra_manager/refresher.rb | 5 +- 1 file changed, 4 insertions(+), 1 deletion(-) I was able to create a VM with custom storage policy 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/RHBA-2019:4199 |
Created attachment 1524194 [details] evm.log Description of problem: When trying to provisioning with storage profile, the provisioning task won't finish fine. It ends with error. Version-Release number of selected component (if applicable): Version 5.10.0.32.20190115185124_c957ada How reproducible: 2/2 Steps to Reproduce: 1. Add a VM in vsphere67-nested provider. With a storage profile selected 2. 3. Actual results: The task fails Expected results: Success. Additional info: