So what this seems to be indicating is either a) the ssh key isn't properly setup as part of the MAAS cloud unit script, b) the private key doesn't match the public key installed, c) something else I can't think of at the moment.
Can we get the full maas-deployer logs? That may shed some light on what's going on. Artur, perhaps something else comes to mind? It's almost as if it's not fully cleaned up... Billy The maas-deployer should be creating/using the ssh key that's available in /root/.ssh/id_maas according to the logs, because it's running as root. I don't currently have access to the script for this (02-maasdeploy.sh) so I'm not 100% sure of the context you are running this. If you don't have another maas environment setup on the same host, something you can try is to remove the /root/.ssh/id_maas* keys On Friday, December 4, 2015, zhangyuanyou <[email protected]> wrote: > Hi Artur Tyloch, > I'm working on maas+juju to deploy openstack,now I edit the > 02-maasdeploy.sh and excute it. > But this line "maas-deployer -c deployment.yaml -d --force" can't pass ,it > always let me to input the password like this: > > *2015-12-04 17:45:54,032 DEBUG Executing: 'virt-install --connect > qemu:///system --name opnfv-maas-intel --ram 4096 --vcpus 4 --disk > vol=default/opnfv-maas-intel-root.img,format=qcow2,bus=virtio,io=native > --disk > vol=default/opnfv-maas-intel-seed.img,format=raw,bus=virtio,io=native > --network bridge=brAdm,model=virtio --network bridge=brData,model=virtio > --network bridge=brPublic,model=virtio --noautoconsole --vnc --import' > stdin=''* > *2015-12-04 17:45:55,145 DEBUG Executing: 'virsh -c qemu:///system > autostart opnfv-maas-intel' stdin=''* > *2015-12-04 17:45:55,162 DEBUG Waiting for MAAS vm to come up for ssh..* > *2015-12-04 17:45:55,163 DEBUG Using ip address specified: 192.168.212.140* > *2015-12-04 17:45:55,163 DEBUG Executing: 'ssh -i /root/.ssh/id_maas -o > UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no > [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');> > true' stdin=''* > > > *[email protected]'s > <javascript:_e(%7B%7D,'cvml','[email protected]%5Cx27s');> password: *I > edited the file deployment.yaml like this: > *demo-maas:* > * maas:* > * # Defines the general setup for the MAAS environment, including > the* > * # username and password for the host as well as the MAAS server.* > * user: root* > * password: root* > > * # Contains the virtual machine parameters for creating the MAAS > virtual* > * # server. Here you can configure the name of the virsh domain, > the* > * # parameters for how the network is attached.* > * name: opnfv-maas-intel* > * interfaces: > ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']* > * memory: 4096* > * vcpus: 4* > * arch: amd64* > * pool: default* > * disk_size: 160G* > > * # Apt http proxy setting(s)* > * apt_http_proxy:* > > * apt_sources:* > * - ppa:maas/stable* > * - ppa:juju/stable* > > * # Virsh power settings* > * # Specifies the uri and keys to use for virsh power control of > the * > * # juju virtual machine. If the uri is omitted, the value for the* > * # --remote is used. If no power settings are desired, then do not* > * # supply the virsh block.* > * virsh:* > * rsa_priv_key: /home/ubuntu/.ssh/id_rsa* > * rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub* > *# uri: qemu+ssh://[email protected]/system > <http://[email protected]/system>* > > * # Defines the IP Address that the configuration script will use > to* > * # to access the MAAS controller via SSH.* > ip_address: 192.168.212.140 > > Could you help me to resolve the question ? Any assistance is greatly > appreciated. > > Thanks. > Yuanyou > > > > > -- Billy Olsen [email protected] Software Engineer Canonical USA
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
