Bug 1203795 - Time synchronization not taking place (RPi4)
Time synchronization not taking place (RPi4)
Status: NEW
Classification: openSUSE
Product: PUBLIC SUSE Linux Enterprise Micro 5.2
Classification: openSUSE
Component: Installation
unspecified
aarch64 openSUSE Leap 15.4
: P5 - None : Normal
: ---
Assigned To: E-mail List
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-09-27 12:33 UTC by Felix Niederwanger
Modified: 2022-10-06 06:45 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
kanderssen: needinfo? (felix.niederwanger)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Niederwanger 2022-09-27 12:33:37 UTC
The installer does not synchronize the system time after the NTP configuration step on a Raspberry Pi 4. This results in download issues due to the https certificate being not yet valid.

I am installing Leap Micro 5.2 on a Raspberry Pi 4 using the UEFI Arm 64-bit server iso image. After the system setup, the installer starts but at the end it denies to download resources from download.opensuse.org, due to certificate issues. The system time is set to June 24, despite the default NTP server has been used during the system installation.

The Raspberry Pi has no realtime clock, so unless we perform a time synchronization during the installation, downloading any resources via https will fail due to the system time being out-of-sync.

I had to manually add the eth0 interface, the onboard network NIC was not automatically detected. However after adding this interface manually (as a network bridge), the connectivity is working properly: I could switch to tty2 and ping google.com.
Comment 1 Lukas Ocilka 2022-09-27 16:05:20 UTC
So as it seems, the problem is not that it does not sync the time, but that the network device is not properly detected / configured. Which of course results in non-working NTP as that uses network. Is that right?

That looks like duplicate of https://bugzilla.suse.com/show_bug.cgi?id=1199820
Comment 2 Felix Niederwanger 2022-09-28 07:01:20 UTC
Not sure. I've manually added a network device (Ethernet) and configured it before proceeding. I checked that the connectivity is established in tty2 by pinging google.com, which was working.

So from my point of view, the connectivity was present yet the time was not synchronized.
Comment 3 Michal Filka 2022-09-29 06:00:13 UTC
Could you attach output of "chronyc sources -v" once you're after time sync dialog? Thanks
Comment 4 Felix Niederwanger 2022-10-04 14:23:57 UTC
(In reply to Michal Filka from comment #3)
> Could you attach output of "chronyc sources -v" once you're after time sync
> dialog? Thanks

In the YaST installer, after the NTP page:

> tty2:rabbit:/ # ping google.com
> ... (works)
> 
> tty2:rabbit:/ # date
> Fir 24 Jun 2022 12:39:18 PM UTC
> tty2:rabbit:/ # chronyc sources -v
> 506 Cannot talk to daemon

I did this on tt2 after the NTP server page, where I continued with the default selection of "1.suse.pool.ntp.org"
Comment 5 Knut Alejandro Anderssen González 2022-10-05 10:46:25 UTC
(In reply to Felix Niederwanger from comment #4)
> (In reply to Michal Filka from comment #3)
> > Could you attach output of "chronyc sources -v" once you're after time sync
> > dialog? Thanks
> 
> In the YaST installer, after the NTP page:
> 
> > tty2:rabbit:/ # ping google.com
> > ... (works)
> > 
> > tty2:rabbit:/ # date
> > Fir 24 Jun 2022 12:39:18 PM UTC
> > tty2:rabbit:/ # chronyc sources -v
> > 506 Cannot talk to daemon
> 
> I did this on tt2 after the NTP server page, where I continued with the
> default selection of "1.suse.pool.ntp.org"

So, it looks like chronyd is enabled during the installation and therefore it is not running. 

just check systemctl status chronyd
Comment 6 Knut Alejandro Anderssen González 2022-10-05 10:48:36 UTC
Looks related to https://bugzilla.suse.com/show_bug.cgi?id=1202067
Comment 7 Felix Niederwanger 2022-10-05 14:11:19 UTC
(In reply to Knut Alejandro Anderssen González from comment #5)

Here's the output:

> tty2:rabbit:/ # systemctl status chronyd
> System has not been booted with systemd as init system (PID 1). Can't operate
> Failed to connect to bus: Host ist down
> tty2:rabbit:/ # pgrep chronyd
> tty2:rabbit:/ # 

Looks like chronyd is not running at all.
Comment 8 Knut Alejandro Anderssen González 2022-10-06 06:45:19 UTC
(In reply to Knut Alejandro Anderssen González from comment #5)
> (In reply to Felix Niederwanger from comment #4)
> > (In reply to Michal Filka from comment #3)
> > > Could you attach output of "chronyc sources -v" once you're after time sync
> > > dialog? Thanks
> > 
> > In the YaST installer, after the NTP page:
> > 
> > > tty2:rabbit:/ # ping google.com
> > > ... (works)
> > > 
> > > tty2:rabbit:/ # date
> > > Fir 24 Jun 2022 12:39:18 PM UTC
> > > tty2:rabbit:/ # chronyc sources -v
> > > 506 Cannot talk to daemon
> > 
> > I did this on tt2 after the NTP server page, where I continued with the
> > default selection of "1.suse.pool.ntp.org"
> 
> So, it looks like chronyd is enabled during the installation and therefore
> it is not running. 

I meant it is not enabled :P 

> 
> just check systemctl status chronyd


BTW, logs are always appreciated, and in case of https://bugzilla.suse.com/show_bug.cgi?id=1202067 it was caused by the role selected, so maybe same case here.