nacx approved this pull request.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/349#pullrequestreview-25621623
Rebased the branch and pushed the Image extension commit to
[master](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/dad3e99f)
and
[2.0.x](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/c1d36ce7)
(finally! ). The other commits in this PR were already merged. I've also
Closed #349.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/349#event-990266816
@nacx It works fine now i have updated the code with the changes requested.
Here is a [gist
](https://gist.github.com/alibazlamit/876cdccdcfcbecc6236e9234ef7d1c88)of the
test results
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
@alibazlamit pushed 1 commit.
1de696d minor changes
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/349/files/e940f59917a114c10032074fde0ffc2a186fa9e1..1de696d01b591a7cedd8505a2d0c084396a3f78d
Hi @alibazlamit! I've finally had some cycles to have a look at the login issue.
It fails because the adapter code *generates a random password if none has been
configured*. This means that jclouds will create the first server with a random
password, take an snapshot from it, and try to create
@nacx a friendly reminder anything on this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/349#issuecomment-277730418
That is just a hash of the password, not the real password so you won't be able
to use that. If it is not working it is possible that the new credentials are
not being properly populated in the jclouds entities. I'll checkout the branch
and have a look.
--
You are receiving this because you
When i log in using the password generate for the node it works, but the
password here `root:pw[b70cc7a33386dfbf78d32fc659e2710e]@46.16.76.181:22)` does
not work , where does this pw come from?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
nacx requested changes on this pull request.
I've commented on the image extension commit.
Regarding the SSH credentials, if not provided, is it possible that the compute
service is generating a new password for the node when creating it from the
image, but that node (being a snapshot), is not
@nacx Running the live tests it fails on `testSpawnNodeFromImage` with this
error
```
(root:pw[b70cc7a33386dfbf78d32fc659e2710e]@46.16.76.181:22)
(root:pw[b70cc7a33386dfbf78d32fc659e2710e]@46.16.76.181:22) error acquiring
{hostAndPort=46.16.76.181:22, loginUser=root, ssh=null,
11 matches
Mail list logo
