Bug 1290192
| Summary: | Edit menu for CFME database backup schedule displays a wrong Starting time. | |||
|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> | |
| Component: | Appliance | Assignee: | Roman Blanco <rblanco> | |
| Status: | CLOSED ERRATA | QA Contact: | Alex Newman <anewman> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 5.4.0 | CC: | abellott, cpelland, dajohnso, gtanzill, jhardy, mfeifer, ngupta, obarenbo, snansi, tcarlin | |
| Target Milestone: | GA | Keywords: | Reopened, ZStream | |
| Target Release: | 5.5.2 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 5.5.2.1 | Doc Type: | Bug Fix | |
| Doc Text: |
In the previous version of CloudForms Management Engine, the wrong time zone and backup start time was displayed when editing the CloudForms Management Engine database backup schedule. This bug was caused by storing the incorrect timezone when creating the database backup schedule. This bug was fixed by correctly saving the timezone when creating the database backup schedule. The correct time zone and backup start time is displayed when editing the database backup schedule in the new version of CloudForms Management Engine.
|
Story Points: | --- | |
| Clone Of: | 1278410 | |||
| : | 1297005 (view as bug list) | Environment: | ||
| Last Closed: | 2016-02-10 15:23:40 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | Bug | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1274270, 1278410 | |||
| Bug Blocks: | 1297005 | |||
|
Comment 2
Tim Wade
2015-12-15 16:38:35 UTC
fixed by 32b9cb23c0828f9daaff516d9cbec7e518bfa28d verified 5.5.2.1.20160114044944_395c086 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. https://access.redhat.com/errata/RHBA-2016:0159 |