Bug 1202067 - MicroOS Desktop: unacceptable TLS certificate
MicroOS Desktop: unacceptable TLS certificate
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: MicroOS
Current
aarch64 Other
: P5 - None : Normal (vote)
: ---
Assigned To: Kubic Bugs
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-08-02 15:15 UTC by Axel Braun
Modified: 2022-08-16 11:13 UTC (History)
8 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2logs (2.65 MB, application/gzip)
2022-08-04 11:29 UTC, Axel Braun
Details
gnome-initial-setup timezone page (360.08 KB, image/png)
2022-08-05 09:18 UTC, David Diaz
Details
Status of NTP service (393.50 KB, image/png)
2022-08-05 09:20 UTC, David Diaz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2022-08-02 15:15:15 UTC
Installation of MOS on Raspi4 from openSUSE-MicroOS-DVD-aarch64-Snapshot20220729-Media.iso 
After first boot, adding flatpak repo fails with the above error message.
As Raspi does not have a RTC, Date/time is wrong, as chronyd is installed, but not activated
After manually installation, adding installing firefox from flathub still fails
Comment 1 Guillaume GARDET 2022-08-02 15:20:36 UTC
Firefox is not available on aarch64 via upstream flatpak: https://bugzilla.mozilla.org/show_bug.cgi?id=1646462

Anyway, the date/time should be set on boot via NTP, by default.
Comment 2 Axel Braun 2022-08-02 15:37:08 UTC
yes, no FF for ARM on flathub. I installed LibreWolf instead (which probably means we should modify the firstboot script)
Comment 3 Guillaume GARDET 2022-08-03 12:25:09 UTC
I can reproduce here as well. 
My workaround is:
  sudo systemctl enable --now chronyd
Comment 4 David Diaz 2022-08-04 07:49:22 UTC
Could you guys please attach the YaST logs? They can help us to see what is going on there.

Thanks in advance.

https://en.opensuse.org/openSUSE:Report_a_YaST_bug
Comment 5 Axel Braun 2022-08-04 08:29:19 UTC
Problem is that MicroOS comes w/o YaST, and by this w/o save_y2logs as well. How to proceed?
Comment 6 Lukas Ocilka 2022-08-04 08:59:14 UTC
Attach /var/log/YaST2 directory PLS.
Comment 7 David Diaz 2022-08-04 09:24:09 UTC
But(In reply to Axel Braun from comment #5)
> Problem is that MicroOS comes w/o YaST, and by this w/o save_y2logs as well.
> How to proceed?

I see, but the system was installed using YaST, right?

So, there are two options:

  - Collect and upload files found in /var/log/YaST2
  - Install yast2-logs and proceed as usual

Does any of those two options work for you?
Comment 8 Axel Braun 2022-08-04 11:29:38 UTC
Created attachment 860606 [details]
y2logs
Comment 9 Knut Alejandro Anderssen González 2022-08-05 08:29:42 UTC
It is related to https://bugzilla.suse.com/show_bug.cgi?id=1135342.

Basically the NTP configuration is not written at the end of the installation because it is not modified and no one is taking care of enabling chrony or systemd-timesync.

When the micro_os_role is selected it runs an additional dialog (see https://github.com/yast/skelcd-control-MicroOS/blob/master/control/control.MicroOS.xml#L242) for configuring the ntp-servers and therefore the configuration is modified and written at the end of the installation but this is not the case of the micro_os_gnome_desktop_role.

The current clients are in caasp module (see https://github.com/yast/yast-caasp/tree/master/src/clients).

The desktop role executes the gnome-initial-setup for configuring the timezone.

Assigning the bug to microos-bugs.
Comment 10 David Diaz 2022-08-05 09:18:37 UTC
Created attachment 860631 [details]
gnome-initial-setup timezone page

During the gnome-initial-setup, a timezone selector is displayed.

BTW, it seems to be a little buggy. When I typed "Canary" it allows me to select "Gran Canaria, Canary Islands" but it selects Madrid timezone instead. Anyway, something to report in another bug tracker ;)
Comment 11 David Diaz 2022-08-05 09:20:08 UTC
Created attachment 860632 [details]
Status of NTP service

As it can be seen, none NTP service is active after gnome-initial-setup despite it shown its timezone page.
Comment 12 David Diaz 2022-08-05 09:21:24 UTC
(In reply to Knut Alejandro Anderssen González from comment #9)
> 
> The desktop role executes the gnome-initial-setup for configuring the
> timezone.

See comment #10 and comment #11
Comment 13 Jan Zerebecki 2022-08-09 16:47:53 UTC
I don't think anyone reachable via microos-bugs knows enough about yast or the skelcd control file. CC-ing the relevant bugowner instead:
> osc bugowner -A yast2-caasp
Defined in project:  YaST:Head
  bugowner of yast2-caasp : 
   yast2-maintainers
> osc bugowner -A skelcd-control-MicroOS
Defined in project:  YaST:Head
  bugowner of skelcd-control-MicroOS : 
   yast2-maintainers
Comment 14 Thorsten Kukuk 2022-08-09 17:01:58 UTC
(In reply to Jan Zerebecki from comment #13)
> I don't think anyone reachable via microos-bugs knows enough about yast or
> the skelcd control file. CC-ing the relevant bugowner instead:

That's per se not a YaST problem, but it looks like the MicroOS Desktop system role was choosen? Axel, would be nice if you would explain what you did install and not let others guess or make wrong assumptions. Because it looks like this is not "MicroOs" as you claims but "MicroOS Desktop"?

Richard, who is responsible for the GNOME Desktop case to setup the time correct?

(In reply to Axel Braun from comment #5)
> Problem is that MicroOS comes w/o YaST, and by this w/o save_y2logs as well.
> How to proceed?

This is not correct or a bug in the Desktop selection, MicroOS comes with save_y2logs. It's an extra package for that reason.
Richard?
Comment 15 Axel Braun 2022-08-09 18:33:33 UTC
(In reply to Thorsten Kukuk from comment #14)
> (In reply to Jan Zerebecki from comment #13)
> > I don't think anyone reachable via microos-bugs knows enough about yast or
> > the skelcd control file. CC-ing the relevant bugowner instead:
> 
> That's per se not a YaST problem, but it looks like the MicroOS Desktop
> system role was choosen? Axel, would be nice if you would explain what you
> did install and not let others guess or make wrong assumptions. Because it
> looks like this is not "MicroOs" as you claims but "MicroOS Desktop"?

Thats right, as the headline says, I have chosen MicroOS Desktop for installation. As the Raspi does not have a Real-time-Clock, its date and time settings are inaccurate unless it gets a date/time from NTP...but that is not active by default

> Richard, who is responsible for the GNOME Desktop case to setup the time
> correct?
> 
> (In reply to Axel Braun from comment #5)
> > Problem is that MicroOS comes w/o YaST, and by this w/o save_y2logs as well.
> > How to proceed?
> 
> This is not correct or a bug in the Desktop selection, MicroOS comes with
> save_y2logs. It's an extra package for that reason.

..but it is not installed by default....
Comment 16 David Diaz 2022-08-10 07:03:04 UTC
(In reply to Jan Zerebecki from comment #13)
> I don't think anyone reachable via microos-bugs knows enough about yast or
> the skelcd control file. CC-ing the relevant bugowner instead:
> > osc bugowner -A yast2-caasp
> Defined in project:  YaST:Head
>   bugowner of yast2-caasp : 
>    yast2-maintainers
> > osc bugowner -A skelcd-control-MicroOS
> Defined in project:  YaST:Head
>   bugowner of skelcd-control-MicroOS : 
>    yast2-maintainers

Probably by accident because of the module name. 

Asking Richard Brown, who created and updated the skelcd. See output from git blame https://github.com/yast/skelcd-control-MicroOS/blame/509289c27796cbbdaa7cbfad8b93fdcd618469cf/control/control.MicroOS.xml#L257
Comment 17 Richard Brown 2022-08-10 11:07:50 UTC
(In reply to David Diaz from comment #16)
> (In reply to Jan Zerebecki from comment #13)
> > I don't think anyone reachable via microos-bugs knows enough about yast or
> > the skelcd control file. CC-ing the relevant bugowner instead:
> > > osc bugowner -A yast2-caasp
> > Defined in project:  YaST:Head
> >   bugowner of yast2-caasp : 
> >    yast2-maintainers
> > > osc bugowner -A skelcd-control-MicroOS
> > Defined in project:  YaST:Head
> >   bugowner of skelcd-control-MicroOS : 
> >    yast2-maintainers
> 
> Probably by accident because of the module name. 
> 
> Asking Richard Brown, who created and updated the skelcd. See output from
> git blame
> https://github.com/yast/skelcd-control-MicroOS/blame/
> 509289c27796cbbdaa7cbfad8b93fdcd618469cf/control/control.MicroOS.xml#L257

Hi all,

The problem we face with the MicroOS Desktop is as follows

- We _cannot_ have YaST produce a user account, because we need the gnome initial setup tool to do that
- YaST does so on regular MicroOS as part of the inst_user_first module
- Therefore the inst_user_first module must not be run when installing the MicroOS Desktop, which is why it was removed
- When removing inst_user_first I didn't add back the inst_microos_role we use elsewhere

I don't really care for the RPi as a desktop platform but I'll fix this as it will make the Desktop more in sync with what we have on regular MicroOS
Comment 19 Richard Brown 2022-08-10 11:55:35 UTC
PR merged, bug fixed
Comment 20 Axel Braun 2022-08-16 11:13:36 UTC
(In reply to Richard Brown from comment #19)
> PR merged, bug fixed

Thank you!