Closed brookemckim closed 3 years ago
i'm a little confused on why ubuntu user wouldn't exist on the server given its standard in cloud images.
DO doesn't use our standard cloud images. They are pressing their own ubuntu images on premise from what I know. So it stands to reason there's some differences here.
As part of the manual provider JuJu will ensure the
ubuntu
user exists on all machines added. This is triggered here https://github.com/juju/juju/blob/master/provider/manual/provider.go#L26 and you can see the script it adds here https://github.com/juju/juju/blob/8da94246468a4da71e62894f7a8a1bbbce112697/environs/manual/init.go#L177Without the
ubuntu
user the services will fail to work because the bootstrap machine attempts to connect to the new machines viassh ubuntu@[host]
. I haven't been able to track down why that codepath isn't being run, but I assume it has to do with the fact the python-jujuclient is being used to RPC into the apiserver library.Here is what the user-data script looks like to bootstrap new machines
As you can see it does not include adding the ubuntu user.