Bug 1390572 - Cannot copy provisioning requests
Summary: Cannot copy provisioning requests
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Aparna Karve
QA Contact: Shveta
URL:
Whiteboard: provisioning
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 12:22 UTC by Ievgen Zapolskyi
Modified: 2016-11-18 22:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
linux, Chrome Version 54.0.2840.90 (64-bit)
Last Closed: 2016-11-07 16:38:10 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
error message (94.96 KB, image/png)
2016-11-01 12:22 UTC, Ievgen Zapolskyi
no flags Details
cfme logs (5.90 MB, application/x-gzip)
2016-11-01 12:27 UTC, Ievgen Zapolskyi
no flags Details

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.


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