action #49331
closedcoordination #49244: YaST Command Line Options TRACKER
Regression test yast security
Added by vpelcak about 5 years ago. Updated almost 2 years ago.
0%
Description
Verify ability to:
- specify the security level of the host
- set the value of specific options
- display a summary of the current security configuration
Updated by pstivanin almost 5 years ago
- Due date set to 2019-05-10
- Status changed from New to In Progress
- Assignee set to pstivanin
- Start date changed from 2019-03-14 to 2019-04-30
- Estimated time set to 24.00 h
Updated by pstivanin almost 5 years ago
- Start date changed from 2019-04-30 to 2019-05-02
Updated by pstivanin almost 5 years ago
- % Done changed from 0 to 40
- Estimated time changed from 24.00 h to 16.00 h
Updated by pstivanin almost 5 years ago
- % Done changed from 60 to 80
Code has been implemented, now testing it everywhere
Updated by pstivanin almost 5 years ago
- Target version changed from QAM tests - future to QAM tests - current
- % Done changed from 80 to 100
PR is ready for review: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7381
Updated by pstivanin almost 5 years ago
Changing the security level of the host doesn't work, so I opened a bug for that: https://bugzilla.suse.com/show_bug.cgi?id=1134013
Updated by pstivanin almost 5 years ago
YaST2 security is not 'integrated' with passwd, so in order to verify that the 'min passwor' feature works, the 'Users' module should be used.
This could be a thing to keep in mind if we want to increase the test coverage
Updated by pstivanin almost 5 years ago
- Estimated time changed from 16.00 h to 10.00 h
Updated by pstivanin almost 5 years ago
- Status changed from In Progress to Resolved
Updated by vpelcak almost 5 years ago
- Status changed from Resolved to In Progress
Test does something completely different than described in the reference:
https://www.suse.com/documentation/sles-15/singlehtml/book_sle_admin/book_sle_admin.html#id-1.3.3.6.13.6.29
https://progress.opensuse.org/issues/49244 is about yast in cli, not gui.
Testcase is very useful, but doesn't test CLI at all.
Updated by pstivanin almost 5 years ago
- Due date changed from 2019-05-10 to 2019-06-10
- Start date changed from 2019-05-02 to 2019-05-30
- % Done changed from 100 to 0
- Estimated time changed from 10.00 h to 8.00 h
Updated by pstivanin almost 5 years ago
@Vit: changing the security level does not work at the moment. See the bug I opened above.
Should we proceed anyway to develop this test?
Updated by pstivanin almost 5 years ago
- Start date set to 2019-03-14
due to changes in a related task
Updated by pstivanin almost 5 years ago
- Due date deleted (
2019-06-10) - Status changed from In Progress to Workable
- Assignee deleted (
pstivanin) - Start date deleted (
2019-05-30) - Estimated time deleted (
8.00 h)
Updated by pstivanin almost 5 years ago
Until the aforementioned bug is solved there's not much we can do on our side.
Using the CLI, the only available commands are:
- level (which does not work)
- set
- summary (which displays only "custom settings" due to the bug) There's no "get" command, so even if we developed a test that sets somethings we would have no way to know whether the settings has been correctly applied.
Updated by brhavel over 4 years ago
- Subject changed from [qam] Regression test yast security to [qam][maint][yast2-security] - Regression test yast security
- Status changed from Workable to Feedback
Updated by tjyrinki_suse almost 4 years ago
- Status changed from Feedback to Blocked
The bug is still open.
Updated by tjyrinki_suse over 3 years ago
- Project changed from 119 to qe-yam
- Target version deleted (
QAM tests - current)
Updated by riafarov over 3 years ago
- Subject changed from [qam][maint][yast2-security] - Regression test yast security to Regression test yast security
- Target version set to future
Updated by okurz over 2 years ago
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).