The proposal to merge ~rjschwei/cloud-init:handleUsrLocked into 
cloud-init:master has been updated.

Commit message changed to:

Handle a locked user

At present if the user exists and is already locked, either previous
user creation or user is created locked by default the lock action
exception is propagated. However, if the user is already locked we
have the condition we want to achieve and thus should move on.
Addresses 

LP: #1793193

For more details, see:
https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/355254
-- 
Your team cloud-init commiters is requested to review the proposed merge of 
~rjschwei/cloud-init:handleUsrLocked into cloud-init:master.

_______________________________________________
Mailing list: https://launchpad.net/~cloud-init-dev
Post to     : cloud-init-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~cloud-init-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to