Project

General

Profile

Actions
Copy link

action #61946

closed

[functional][y] Automate yast2-ntp-client module

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

Status:
Resolved
Priority:
Normal
Assignee:
syrianidou_sofia
Category:
New test
Target version:
SUSE QA - Milestone 32
Start date:
2019-11-20
Due date:
2020-05-05
% Done:

0%

Estimated time:
Difficulty:

Description

Exploratory manual testing was done in https://progress.opensuse.org/issues/60086 and now we can automate with AutoYaST.

Check that systemd timers are used and and not cron. Basically we need to check:

Acceptance criteria

  1. Timers are covered for yast2 ntp
  2. Installation is validated after ntp is configured
  3. Generation of the profile is also validated

Further info

For checking the service we need to fill in on the UI a proper ntp server.
It was forgotten to attach the AutoYaST profile in previous ticket, so first thing is cloned the system and create some
minimal profile to work on and finally do some validation of the file and the service involved.

We also could combine this with other existing autoyast

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

Actions
Copy link
 #1

Updated by JERiveraMoya over 4 years ago

  • Copied from action #60086: [functional][y][SLE-9115][SLE-9103][timeboxed:16h] Test yast2-ntp-client uses systemd timers and not cron added
Actions
Copy link
 #2

Updated by JERiveraMoya over 4 years ago

  • Copied from deleted (action #60086: [functional][y][SLE-9115][SLE-9103][timeboxed:16h] Test yast2-ntp-client uses systemd timers and not cron)
Actions
Copy link
 #3

Updated by riafarov about 4 years ago

  • Due date set to 2020-03-10
  • Target version changed from Milestone 30 to Milestone 32
Actions
Copy link
 #4

Updated by JERiveraMoya about 4 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by JERiveraMoya about 4 years ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by JERiveraMoya about 4 years ago

  • Description updated (diff)
Actions
Copy link
 #7

Updated by JERiveraMoya about 4 years ago

  • Due date changed from 2020-03-10 to 2020-03-24

no capacity

Actions
Copy link
 #8

Updated by JERiveraMoya about 4 years ago

  • Due date changed from 2020-03-24 to 2020-04-07
Actions
Copy link
 #9

Updated by riafarov about 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00 h
Actions
Copy link
 #10

Updated by riafarov about 4 years ago

  • Due date changed from 2020-04-07 to 2020-04-21
Actions
Copy link
 #11

Updated by syrianidou_sofia about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions
Copy link
 #12

Updated by syrianidou_sofia about 4 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #13

Updated by riafarov about 4 years ago

There are sporadic failures.

Actions
Copy link
 #15

Updated by riafarov about 4 years ago

  • Estimated time deleted (5.00 h)

Not yet enabled in the job group.

Actions
Copy link
 #16

Updated by riafarov about 4 years ago

  • Due date changed from 2020-04-21 to 2020-05-05
Actions
Copy link
 #17

Updated by syrianidou_sofia about 4 years ago

Test enabled. Verification run : https://openqa.suse.de/tests/4143808

Actions
Copy link
 #18

Updated by syrianidou_sofia about 4 years ago

  • Status changed from Feedback to Resolved

Test looks stable

Actions
Copy link

Also available in: Atom PDF