Bug 1493381 - Timezone value got appended in the last record of Key/Value attributes field.
Summary: Timezone value got appended in the last record of Key/Value attributes field.
Keywords:
Status: CLOSED DUPLICATE of bug 1466032
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: All
OS: All
medium
high
Target Milestone: GA
: cfme-future
Assignee: Milan Zázrivec
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-20 05:35 UTC by Neha Chugh
Modified: 2021-06-10 13:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 12:48:37 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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