I can't remember the exact details, but I believe that this change was
landed to support a CloudStack deployment that didn't support SSH keys
at all.  In my ignorance of the broader CloudStack ecosystem, I assumed
that this was true of all CloudStack deployments, so setting it in the
data source made sense (so that people would be able to access their
instances somehow).

Given that my assumption is false, I would be happy with backing out
that setting _provided there is a way for vendors to set it back_.  I
believe backing out the setting will regress existing CloudStack
deployments that expect the current behaviour (and regress them in a
serious way; it would completely deny users' access to their VMs).

Does CloudStack support vendor data[0]?  If it does, then we can ensure
that (a) it's possible to use vendor data to restore the old behaviour,
and (b) we document how people do so.  If it doesn't, then I'd be
hesitant to make this change.


[0] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+ConfigDrive+for+Metadata%2C+Userdata+and+Password
 suggests "maybe" to me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747705

Title:
  "ssh_pwauth" always true on CloudStack datasource with password

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to