Bug 1784535
| Summary: | [RFE] RedHat Domain vmware_best_placement_with_scope Automate method error "not an eligible resource for this provisioning instance". | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> | ||||
| Component: | Provisioning | Assignee: | Patrik Kománek <pkomanek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jaroslav Henner <jhenner> | ||||
| Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | ||||
| Priority: | high | ||||||
| Version: | 5.10.0 | CC: | dgaikwad, dmetzger, gekis, jhardy, jhenner, mperina, mshriver, obarenbo, pkomanek, rciatti, sigbjorn, smallamp, tfitzger | ||||
| Target Milestone: | GA | Keywords: | ZStream | ||||
| Target Release: | 5.11.2 | Flags: | pm-rhel:
cfme-5.11.z+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 5.11.2.0 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1698183 | Environment: | |||||
| Last Closed: | 2020-02-12 05:02:44 UTC | Type: | --- | ||||
| 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: | |||||||
| Bug Depends On: | 1698183 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Comment 2
Devidas Gaikwad
2020-01-22 15:36:01 UTC
Hi Devidas, Can you explain more about the steps you took to validate this issue? Were you able to see the method fail, then work? Thanks, Tina Hey @Tina, As I mentioned above I just checked source code no other things and I am not having knowledge around Automate domains and methods. Could you please give me test steps and expected results. So that I can verify this BZ. Please help :) Thanks, Devidas Gaikwad I found these two problems when verifying: * vmware_best_fit_with_tags is present in the RedHat Domain, but I couldn't check it is working as I was unable to set the tags on the VMNetwork on the VMware. I couldn't find the control for it so far. * I tried the similar with the rhev provider. I didn't find any "redhat_best_fit_with_tags" which IIUC should be present as I am getting: [----] E, [2020-02-03T12:58:29.677558 #7230:2abf28cfa5b4] ERROR -- : Q-task_id([r6_miq_provision_6]) State=<Placement> running raised exception: <Method [redhat_best_fit_with_tags] not found in class [BZ_1784535/Infrastructure/VM/Provisioning/Placement]> in the automation.log Created attachment 1657394 [details]
available methods
We had to add the tag to some additional items in the cfme to make the network get selectable in the provisioning dialog. I didn't set the Support tag for the Host and Datastore. I tried to provision the VM with both user_user and auser_admin. I ended up with the VM created fine in both cases. Both cases produced an INFO line in the automation log: [----] I, [2020-02-04T05:46:35.139861 #30925:2abf349f7a54] INFO -- : Q-task_id([r10_miq_provision_10]) <AEMethod vmware_best_fit_with_tags> Selected Datastore:<THE_DATASTORE> where the THE_DATASTORE was never nil OK. I have found we did mark some other datastore with the Support tag and terefore it got selected. After untagging it I got: [----] I, [2020-02-04T09:10:34.725247 #65523:2abf3b21a3fc] INFO -- : Q-task_id([r12_miq_provision_12]) <AEMethod vmware_best_fit_with_tags> Selected Datastore:<nil> I think this works well. 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-2020:0452 |