Bug 1493381

Summary: Timezone value got appended in the last record of Key/Value attributes field.
Product: Red Hat CloudForms Management Engine Reporter: Neha Chugh <nchugh>
Component: UI - OPSAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: medium    
Version: 5.8.0CC: cpatters, hkataria, ikaur, jhardy, mpovolny, mzazrivec, obarenbo, sacpatil, smallamp
Target Milestone: GAKeywords: Reopened
Target Release: cfme-future   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 12:48:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neha Chugh 2017-09-20 05:35:30 UTC 
Description of problem:
Timezone value got appended in the third record of Key/Value attributes field.

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

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Configuration -> Settings -> Schedules
2. Create a schedule to run a custom automate instance. Choose the action as Automate task.
3. Add the Attribute/value pairs and click on save button
4. Click on the schedule and you will observe the timezone value get appended in the third record of the Attribute/value pairs.

Actual results:
Timezone value get appended in the third record of the Attribute/value pairs.

Expected results:
It should only show the attribute/value pairs. No timezone value should be appended.

Additional info:
Comment 3 Milan Zázrivec 2018-01-19 14:06:13 UTC 
I tried the described steps with both current ManageIQ master
as well as the 5.8 code and cannot reproduce it with either.

I'm closing this report with worksforme. Please reopen if
the problem reappears.
Comment 5 Milan Zázrivec 2018-03-29 12:48:37 UTC 

*** This bug has been marked as a duplicate of bug 1466032 ***