On Tue, 18 Sep 2018 06:56:41 +0000 "Chan, Aaron Chun Yew" aaron.chun.yew.chan@intel.com wrote:

Hi Linaro Validation,

I have a used case where by during auto_login the Clear OS, we have 1st password prompt and follow by 2nd password prompt to verity the password creation is set properly.

Password creation is not supported by auto-login action. This is also unlikely to be added because auto-login action has already become much more complex than is really desirable. It will become even more difficult to run the functional tests for auto-login with enough coverage for all of the supported permutations. A completely separate class which only supported this variant would need an explicit set of functional tests and a clear division from the existing syntax in the test job definitions, but you would need to do all that work to create it and the tests.

Password creation is a task for the build system, not the automation system.

I would like to know if the current dispatcher scripts is able to support this use case, whereby a second password prompt is expected follow by the a second password re-entry. Let me know your thoughts on where I can start with this if there is a need to add in an extra key into the boot action methods.

The init system may need modification to disable this behaviour, to pre-configure a password or to not require a password in the first place, just to drop immediately to a root prompt.

Currently if I used this on my LAVA Job it returns me with this error:

Invalid definition: extra keys not allowed @ data['actions'][1]['boot']['auto_login']['password_prompt_retry']

auto_login: { login_prompt: 'login:', username: root, password_prompt: 'Password:', password: password123, password_prompt_retry: 'New Password:', password_reentry: password123 }

Regards, Chan, Aaron SSG Embedded Linux - Yocto Project Contact : +6042536861 Location: PG12/L1/A318