Project

General

Profile

Actions

action #129739

closed

coordination #123583: [epic] Agama auto-installation

Create validation for user/password for default auto-installation with Agama

Added by JERiveraMoya over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2023-05-23
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Create new auto-installation with Agama (using your favorite format, .sh, .json or .jsonnet) with following characteristics besides default:

  • Add user.
  • Set password for that user.

Scope

Products: ALP Micro, ALP Bedrock and Tumbleweed
Architectures: x86_64 and aarch64

Acceptance criteria

AC1: New auto-installation is created with features above in O3 (or in OSD if already available).
AC2: System boots and login is possible for user with specified password.

Additional information

Note that we could also test auto-login here, but this settings most likely will be drop from the UI because in textmode that is not possible and we are installing system without desktop.

Actions #1

Updated by JERiveraMoya over 1 year ago

  • Subject changed from Automate auto-installation which add user with password to Automate auto-installation which adds user with password
Actions #2

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #3

Updated by coolgw over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to coolgw
Actions #4

Updated by coolgw over 1 year ago

Need confirm the detail requirement:

1)New data/yam/agama/auto/alp_test_user.sh contain new user like following:
+/usr/bin/agama config set user.userName=alp_user user.password=nots3cr3t

2)New test module tests/yam/agama/user.pm used for check alp_user and password.

3)New schedule file agama_auto_test_user.yaml
And put user.pm into new schedule/yam/agama_auto_test_user.yaml
- yam/agama/auto
+ - yam/agama/user

4)New 3 test case for ALP Micro, ALP Bedrock and Tumbleweed with setting AGAMA_AUTO=yam/agama/auto/alp_test_user.sh & YAML_SCHEDULE=schedule/yam/agama_auto_test_user.yaml
Test name will be:
agama_auto_tumbleweed_test_user
agama_auto_micro_test_user
agama_auto_bedrock_test_user

Actions #5

Updated by JERiveraMoya over 1 year ago

coolgw wrote:

Need confirm the detail requirement:

1)New data/yam/agama/auto/alp_test_user.sh contain new user like following:
+/usr/bin/agama config set user.userName=alp_user user.password=nots3cr3t

you can call the user 'bernhard' like in openQA, alp is a platform with many flavors and agama also install tw, so users should not contain those specific.

2)New test module tests/yam/agama/user.pm used for check alp_user and password.

should go in same folder created for validate product, ie: tests/yam/validate/validate_user.pm (if doesn't collide with existing test)

3)New schedule file agama_auto_test_user.yaml
And put user.pm into new schedule/yam/agama_auto_test_user.yaml
- yam/agama/auto
+ - yam/agama/user

the word 'test' should not appear, it always obvious by the context, we need 'verb' + 'noun' to identify better stuff, ie: agama_auto_add_user.yaml

4)New 3 test case for ALP Micro, ALP Bedrock and Tumbleweed with setting AGAMA_AUTO=yam/agama/auto/alp_test_user.sh & YAML_SCHEDULE=schedule/yam/agama_auto_test_user.yaml
Test name will be:
agama_auto_tumbleweed_test_user
agama_auto_micro_test_user
agama_auto_bedrock_test_user

Similar name for the test suite than for the schedule than suggested above.

Actions #6

Updated by coolgw over 1 year ago

coolgw wrote:

JERiveraMoya wrote:

coolgw wrote:

Need confirm the detail requirement:

1)New data/yam/agama/auto/alp_test_user.sh contain new user like following:
+/usr/bin/agama config set user.userName=alp_user user.password=nots3cr3t

you can call the user 'bernhard' like in openQA, alp is a platform with many flavors and agama also install tw, so users should not contain those specific.

2)New test module tests/yam/agama/user.pm used for check alp_user and password.

should go in same folder created for validate product, ie: tests/yam/validate/validate_user.pm (if doesn't collide with existing test)

Currently validate_product.pm is under tests/yam/agama. So do you mean create tests/yam/validate directory and put validate_user.pm and validate_product.pm under it, correct?
root#ll tests/yam/agama/
-rw-r--r-- 1 root root 999 May 22 08:13 agama_installation.pm
-rw-r--r-- 1 root root 494 May 28 19:14 auto.pm
-rw-r--r-- 1 root root 772 May 28 19:14 validate_product.pm <===

3)New schedule file agama_auto_test_user.yaml
And put user.pm into new schedule/yam/agama_auto_test_user.yaml
- yam/agama/auto
+ - yam/agama/user

the word 'test' should not appear, it always obvious by the context, we need 'verb' + 'noun' to identify better stuff, ie: agama_auto_add_user.yaml

4)New 3 test case for ALP Micro, ALP Bedrock and Tumbleweed with setting AGAMA_AUTO=yam/agama/auto/alp_test_user.sh & YAML_SCHEDULE=schedule/yam/agama_auto_test_user.yaml
Test name will be:
agama_auto_tumbleweed_test_user
agama_auto_micro_test_user
agama_auto_bedrock_test_user

Similar name for the test suite than for the schedule than suggested above.

Actions #8

Updated by JERiveraMoya over 1 year ago

  • Subject changed from Automate auto-installation which adds user with password to Create validation for user/password for default auto-installation with Agama

Updated title to reflect current state.

Actions #9

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF