Bug 1392522

Summary: Time Zone Self Increments (RHVH interactive installation)
Product: Red Hat Enterprise Linux 7 Reporter: Jon Benedict <jbenedic>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-15 07:28:25 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 Jon Benedict 2016-11-07 16:39:30 UTC
Description of problem: during installation of RHVH from ISO image, the time will self-increment if you don't immediately select "done" after choosing the time zone.


Version-Release number of selected component (if applicable):
RHVH-4.0-20161018.0-RHVH-x86_64-dvd1.iso

How reproducible:
consistently during interactive install of iso image

Steps to Reproduce:
1. Launch installation of RHVH
2. at time zone selection choose time zone, in my case US EST
3. the time will change appropriately, base on the time zone
4. HOWEVER, the hour will then bump itself up 1 hour after a few seconds if the "done" button is not selected in time.

Actual results:
the hour self increments at the time zone page

Expected results:
the time zone should adjust and simply leave the time alone at that point

Additional info:
The configuration here is part of a nested virtualization lab. If necessary, I can record the setup and attach a link of the recording to show ~exactly~ what I'm doing.

Comment 3 RHEL Program Management 2021-01-15 07:28:25 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.