Bug 1826630

Summary: create a silence then edit the silence, during value is not populated
Product: OpenShift Container Platform Reporter: hongyan li <hongyli>
Component: Management ConsoleAssignee: Andrew Pickering <anpicker>
Status: CLOSED ERRATA QA Contact: hongyan li <hongyli>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, jokerman, juzhao, xiaocwan
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:29:58 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:

Description hongyan li 2020-04-22 07:49:39 UTC
Description of problem:
create a silence then edit the silence, during value is not populated

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

How reproducible:

Steps to Reproduce:
1.Go to Monitoring-Alerts, click combo icon to selience an alert
2.set during value, such as 1d, click silence button
3.click Actions - edit silence

Actual results:
during value input has no value, it shows "-" on UI

Expected results:
during value input should have value we set, even the create silence page has a default value 2h

Additional info:

Comment 5 hongyan li 2020-04-30 03:06:07 UTC
test with payload 4.5.0-0.nightly-2020-04-29-215453
now create a silence, edit the silence check the during value can be populated, but when edit the silence the during value will be gone

Comment 9 hongyan li 2020-05-06 01:27:22 UTC
Test with payload 4.5.0-0.nightly-2020-05-04-113741
When edit silence, start time is now and end time is as set before, so duration has no value.

Comment 10 errata-xmlrpc 2020-07-13 17:29:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.