Bug 2229207

Summary: initial-setup always sets the RTC to local mode
Product: [Fedora] Fedora Reporter: Davide Cavalca <davide>
Component: anacondaAssignee: anaconda-maint
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: anaconda-maint, asahi-sig, janne-fdr, vslavik, w
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:40:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
inital-set/anaconda log from an affected fedora asahi remix system none

Description Davide Cavalca 2023-08-04 15:54:04 UTC 
In the Fedora Asahi Remix we've noticed that inital-setup (which uses anaconda under the hood) is always setting the RTC to local by writing LOCAL to /etc/adjtime. We would expect it to use UTC instead.

Reproducible: Always

Steps to Reproduce:
1. Get an Apple Silicon Mac (M1 mac mini or macbook is the easiest)
2. curl https://fedora-asahi-remix.org/install | sh
3. go through the install
4. check the time
Comment 1 Janne Grunau 2023-08-04 16:31:05 UTC 
Created attachment 1981677 [details]
inital-set/anaconda log from an affected fedora asahi remix system

from browsing through the anaconda source code I suspect the problem is that time_initialize() https://github.com/rhinstaller/anaconda/blob/f076f51c9c56ef226dc7ee56fce3feefa5cf2032/pyanaconda/timezone.py#L55 is not called.

I do not see an execution of `hwclock --hwtosys ...` logged. From my cursory browsing think the program execution should be logged and `hwclock --systohw --local` is logged.

timezone_proxy.IsUtc defaults to false resulting in the system being configured LOCAL in etc/adjtime.
Comment 2 Aoife Moloney 2024-05-28 13:40:39 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.