Bug 1529080
| Summary: | "VM Lifecycle" Request last message do not indicate actual problem-invalid vm name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Ilanit Stein <istein> | ||||
| Component: | Provisioning | Assignee: | William Fitzgerald <wfitzger> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Dave Johnson <dajohnso> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.9.0 | CC: | cpelland, gblomqui, istein, jfrey, jhardy, obarenbo, simaishi, tfitzger | ||||
| Target Milestone: | GA | ||||||
| Target Release: | cfme-future | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | CFME Core | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-06-12 19:18:11 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | Bug | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Sending to GregM to see if there's something we can do to better propagate this to the UI side. If not, then it probably needs to be looked at by the RHV team. llanit, I used "Provision VM from a template" and tried to provision a vm with the name of billy_wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd. My Request Last Message was very similar to you one you received. I will include a screenshot. I noticed in the automation.log this error message which is similar to what you received : [----] E, [2018-04-17T15:15:30.304005 #52566:3d3ed4] ERROR -- : <AEMethod check_provisioned> ProvisionCheck error <[Ovirt::Error]: [Cannot add VM. The given name is too long.]> If this is the same as the problem you reported, the reason this is happening because the Request Last Message value is being truncated. Can you let me know if this re-creates your problem or if something else is going on. Thanks Billy Created attachment 1423259 [details]
really long vm name for RHEV
llanit, Can you let me know if this re-creates your problem or if something else is going on. Thanks Billy Thanks Billy. This indeed recreates the reported problem. The last message I got is mentioned in the bug description, and is the same as the last message you attached. llanit, The problem is that data is larger than the field and we are truncating the data. Can I close this ? Billy Billy, I fully understand that the VM name data is truncated. This is a result of a negative test I was running, checking the VM name length validation is in place. This bug is about that the user is not displayed an error that reflect the problem. Such error exist in evm.log: "[VM Template name must not exceed 40 characters, Attribute: _name]" Would have been good to pass this message to the VM provision "Last message" field. Thanks. |
Description of problem: When running Publish VM from Template, with VM name, that exceeds the length max limit (40 chars), The Request will fail, with last message, that do not indicate the root cause. Example for Request Last message, for RHV-4.1.8 provider: [EVM] VM [wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd] Step [CheckProvisioned] Status [Error... While the failure root cause, as can be seen in evm.log: [----] I, [2017-12-12T03:48:17.017853 #23038:869994] INFO -- : Calling Create Notification type: automate_user_error subject type: MiqRequest id: 5 options: {:message=>"VM Provision Error: [EVM] VM [wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd] Step [CheckProvisioned] Status [Error Creating Template] Message [[OvirtSDK4::Error]: Fault reason is \"Operation Failed\". Fault detail is \"[VM Template name must not exceed 40 characters, Attribute: _name]\". HTTP response code is 400.] "} [----] E, [2017-12-12T03:48:17.038525 #23038:869994] ERROR -- : <AEMethod update_provision_status> VM Provision Error: [EVM] VM [wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd] Step [CheckProvisioned] Status [Error Creating Template] Message [[OvirtSDK4::Error]: Fault reason is "Operation Failed". Fault detail is "[VM Template name must not exceed 40 characters, Attribute: _name]". HTTP response code is 400.] Note that this bug is probably relevant for the other VM/Template lifecycle operations: "Clone Template to a VM", "Provision VM from a template", that share same entities and tables in the code. Version-Release number of selected component (if applicable): CFME-5.9.0.14 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: