yahoo-eng-team team mailing list archive

[Jan Collijs <launchpad@xxxxxxxxxxxxxxxxxxx>]

Public bug reported:

In our use case we only have one user we create with the cloud-init
configuration file. We need a password set for this user so we
configured him as the default_user as follows:

system_info:
  default_user:
   name: demo
     passwd: PASSWORDHASH
     shell: /bin/bash
     lock-passwd: False

But the password was always locked over and over again.

After some troubleshooting I figured the lock param was wrong.
Apparently for a normal user it's lock-passwd (with a hyphen) but for
the default user it's lock_passwd (with an underscore)

To me this was very confusing and I lost a lot of time on this little
difference. Is there any particular reason why the differ? Wouldn't it
be a better idea to streamline them using only one of the two options
for both?

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1521554

Title:
  lock_passwd  (default_user) vs lock-passwd (normal user)

Status in cloud-init:
  New

Bug description:
  In our use case we only have one user we create with the cloud-init
  configuration file. We need a password set for this user so we
  configured him as the default_user as follows:

  system_info:
    default_user:
     name: demo
       passwd: PASSWORDHASH
       shell: /bin/bash
       lock-passwd: False

  But the password was always locked over and over again.

  After some troubleshooting I figured the lock param was wrong.
  Apparently for a normal user it's lock-passwd (with a hyphen) but for
  the default user it's lock_passwd (with an underscore)

  To me this was very confusing and I lost a lot of time on this little
  difference. Is there any particular reason why the differ? Wouldn't it
  be a better idea to streamline them using only one of the two options
  for both?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1521554/+subscriptions