action #60074
closed
- Copied to action #60077: [functional][y][SLE-7216][SLE-7104] Test offline installer added
- Copied to deleted (action #60077: [functional][y][SLE-7216][SLE-7104] Test offline installer )
- Description updated (diff)
- Subject changed from [functional][y][SLE-7216][SLE-7104] Test repoless installer to [functional][y][SLE-7216][SLE-7104] Test repoless (online) installer
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 5.00 h
- Status changed from Workable to In Progress
- Due date changed from 2019-12-17 to 2019-12-31
- Assignee set to ybonatakis
- Due date changed from 2019-12-31 to 2019-12-17
- Assignee deleted (
ybonatakis)
I tested online medium starting with build 105.4 and i continued with build 108.1 all against x86_64.
The Minimal requirements were met. So registration is forced and when you try to skip you get a proper warning as expected:
- that registration is required
- suggesting to use the full medium otherwise
I tested the following testcases today
TC0: regular installation with default options - all as expected
TC1: installation with separate /home partition - ok
TC2: installation above existing one with encrypted partition and separate /home partition. - the installer could recognize the encrypted partition and asked for the passphrase. Installation havent finished but looks good so far. the installer even asked to import existing user.
Other TCs to follow is testing autoyast installations
Second day: i performed some autoyast installations.
Observation:
- the generated autoinst.xml doesnt work (i cloned the installed system from the TC2 from yesterday). even worse it doesnt stop when base pattern is not found and delete the installed system
- Using one from osd finished the installation successfully.
I filed two bugs regarding autoyast. https://bugzilla.suse.com/show_bug.cgi?id=1159472 and https://bugzilla.suse.com/show_bug.cgi?id=1159477
I think i will perform some tests with corrupted networking tomorrow.
- Assignee set to ybonatakis
- Due date changed from 2019-12-17 to 2019-12-31
Today i tested the installation manipulating the network traffic. The registration step found difficulties to connect to the server and the process terminated. Then you are able to restart if you want. the package corruption had been set 55% in this case.
Setting the latter value for the traffic to 30% the installation was slow but doable.
For automation, @JRivrain and @syrianidou_sofia have provided some ideas. but the one i think it needs to be reenabled/created is the skip_registration for the online installer (installer should force registration).
- Status changed from In Progress to Feedback
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
Shifting ticket after holiday period.
- Due date changed from 2019-12-31 to 2020-01-14
- Status changed from Feedback to Resolved
It's done, we will check if bug with skip registration is still valid.
Also available in: Atom
PDF