Project

General

Profile

Actions

action #60086

closed

coordination #60071: [functional][y][epic] SLE 15 SP2 feature testing

[functional][y][SLE-9115][SLE-9103][timeboxed:16h] Test yast2-ntp-client uses systemd timers and not cron

Added by riafarov over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Spike/Research
Target version:
SUSE QA - Milestone 30
Start date:
2019-11-20
Due date:
2020-01-14
% Done:

0%

Estimated time:
Difficulty:

Description

Exploratory manual testing.

Acceptance criteria

  1. Scope of changes is learned
  2. Exploratory testing is conducted for the parts which are not covered by the automated tests
  3. Follow-up tickets for automated tests are created with detailed description in case are considered to be useful (efforts vs profit)
  4. jira ticket is updated accordingly

Further info

See https://jira.suse.com/browse/SLE-9115 and https://jira.suse.com/browse/SLE-9103

NOTE: registration is forced for online installation, no unregistered installations should be possible.

Actions #1

Updated by riafarov over 4 years ago

  • Subject changed from [functional][y][SLE-9115][SLE-9103] Test yast2-ntp-client uses suystemd timers and not cron to [functional][y][SLE-9115][SLE-9103][timeboxed:16h] Test yast2-ntp-client uses systemd timers and not cron
  • Status changed from New to Workable
Actions #2

Updated by JERiveraMoya over 4 years ago

  • Assignee set to JERiveraMoya
Actions #3

Updated by JERiveraMoya over 4 years ago

  • Status changed from Workable to In Progress
Actions #4

Updated by JERiveraMoya over 4 years ago

When selecting "Synchronize without Daemon": cron daemon is running but I cannot find any configuration file written in /var/spool/cron/tabs. Neither in SLE-12-SP5.
When using daemon, I cannot find any .timer file, only the service named yast-timesync.service.
As of now there is not single scenario working for migration where this change might be implemented (according to the code it seems to be trigger only for migration)

Actions #5

Updated by JERiveraMoya over 4 years ago

  • Due date changed from 2019-12-03 to 2019-12-17
  • Status changed from In Progress to Blocked
Actions #6

Updated by riafarov over 4 years ago

  • Due date changed from 2019-12-17 to 2020-01-28
  • Assignee changed from JERiveraMoya to riafarov

Setting assignee to me to track the bug.

Actions #7

Updated by mgriessmeier about 4 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions #8

Updated by JERiveraMoya about 4 years ago

  • Due date changed from 2020-01-28 to 2020-01-14
  • Status changed from Blocked to In Progress

So after checking with YaST folks, the timer file is dynamic, it is created only if user wants to sync in intervals, otherwise is deleted.
Only manually:
Service stopped, time file yast2-timersync.timer not exists (it is delete it if existing previously).

Synchronize without daemon:
It creates a timer file yast2-timersync.timer where there is a section [Timer] with OnUnitActiveSec=min

Now and on boot:
Service is started immediately and is enabled, file yast2-timersync.timer is not present (or delete it if previously existed).

Actions #9

Updated by JERiveraMoya about 4 years ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by JERiveraMoya about 4 years ago

  • Copied to action #61946: [functional][y] Automate yast2-ntp-client module added
Actions #11

Updated by JERiveraMoya about 4 years ago

  • Copied to deleted (action #61946: [functional][y] Automate yast2-ntp-client module)
Actions #12

Updated by JERiveraMoya about 4 years ago

  • Assignee changed from riafarov to JERiveraMoya
Actions #13

Updated by JERiveraMoya about 4 years ago

zKVM: verified time file /etc/systemd/system/yast2-timersync.timer is added/edited/removed properly depending on the option selected in module yast2 ntp-client.
When cloning profile with yast2 clone_system it is found the following:

  • Only manually: <ntp-client> contains <ntp_sync>manual</ntp_sync> and <service>chronyd</service> is not in <enable_config>.
  • Synchronize without daemon: <ntp-client> contains <ntp_sync>{{interval_selected}}</ntp_sync> and <service>chronyd</service> is not in <enable_config>.
  • Now and on boot: <ntp-client> contains <ntp_sync>systemd</ntp_sync> and <service>chronyd</service> is in <enable_config>.
Actions

Also available in: Atom PDF