Improve knowing when first user is being created or edited #319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Reported bsc#1188068 has revealed that
InstUserFirstDialog
is using a not optimal way to know if the user is going to be created or edited (see comment#12). In fact, changes introduced at yast/yast-firstboot#126 broken it in a way thatinit_pw_for_root
starts failing.Solution
To use the
Y2Users::ConfigElement#attached?
method instead of relying on the password value, which looks prone to false positives.However, the check has to be performed and stored at the time to initialize the dialog because the private InstUserFirsDialogt#user method attaches the user to the current configuration for validation purposes.
Tests