Comment 2 for bug 1978422

Thanks Mike,

James, will these errors halt the install process entirely? Or will it continue on without expected users?

Will fixing this (adding aliases?) cause unexpected *success* in cloud-config use in deployments? If we add aliases, what happens if someone supplies both lock_passwd and lock-passwd keys in their user data?

I'm a bit surprised this is the first we're hearing a consequence of a change from two years ago.

Thanks