Bug 1390572

Summary: Cannot copy provisioning requests
Product: Red Hat CloudForms Management Engine Reporter: Ievgen Zapolskyi <izapolsk>
Component: UI - OPSAssignee: Aparna Karve <akarve>
Status: CLOSED NOTABUG QA Contact: Shveta <sshveta>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: ckacergu, dclarizi, hkataria, izapolsk, jhardy, mpovolny, obarenbo
Target Milestone: GAKeywords: Regression
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: provisioning
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
linux, Chrome Version 54.0.2840.90 (64-bit)
Last Closed: 2016-11-07 16:38:10 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:
Attachments:
Description Flags
error message
none
cfme logs none

Description Ievgen Zapolskyi 2016-11-01 12:22:46 UTC
Created attachment 1216088 [details]
error message

Description of problem:
When I try to make a copy of failed provisioning request and click next tab there, I get "Unexpected error encountered" page (see screenshot).


Version-Release number of selected component (if applicable):
5.6.2.2


How reproducible:
100%

Steps to Reproduce:
1. Create a provisioning request (I had failed request) in CFME
2. Make a copy of this request in Services->Requests
3. Click any tab in cloned request

Actual results:
"Unexpected error encountered" page appears.
Error text: 
undefined method `[]=' for nil:NilClass [miq_request/prov_field_changed]

Expected results:
copy request functionality shouldn't lead to any errors

Additional info:
logs and screenshots are attached.

Comment 2 Ievgen Zapolskyi 2016-11-01 12:27:55 UTC
Created attachment 1216095 [details]
cfme logs

Comment 3 Chris Kacerguis 2016-11-01 14:51:15 UTC
Sending to Dan, this is the Classic UI

Comment 5 Ievgen Zapolskyi 2016-11-07 09:16:16 UTC
I just figured out that the issue can be reproduced only using Chrome (cannot reproduce it in FF). My Chrome Version 54.0.2840.90 (64-bit).

I prepared an appliance for you. You can reach it at https://10.8.199.127
There is a prepared provisioning request that you can use for reproducing the issue.

Comment 7 Ievgen Zapolskyi 2016-11-07 16:38:10 UTC
I've figured out that there is some chrome extension causing such issue. So, I'm closing the bug.