You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 24, 2019. It is now read-only.
Install hangs on step 11 using current ubuntu aws ami.
Run task: 05-install-euca2ools
Run task: 06-patch-boto
Run task: 07-host-information
Run task: 10-create-volume
The EBS volume id is AWS
Run task: 11-attach-volume
.............................................................................
I checked the AWS console, dont see the volume. So perhaps the volume is not being created?
The text was updated successfully, but these errors were encountered:
I meet the same problem, the root cause iss I misuse the access/secret keys after I check the task 11's script and log. After I exchange the access/secret keys, everything goes well.
In order to boot up the instance correctly, there are several manual steps to fix the problems: 1) linux-image is not installed, which cause the grubdom error. 2) dns configuration is missed; 3) ssh publickey login is not handled well by AWS, the authorized_keys has to been added by manual.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Install hangs on step 11 using current ubuntu aws ami.
Run task: 05-install-euca2ools
Run task: 06-patch-boto
Run task: 07-host-information
Run task: 10-create-volume
The EBS volume id is AWS
Run task: 11-attach-volume
.............................................................................
I checked the AWS console, dont see the volume. So perhaps the volume is not being created?
The text was updated successfully, but these errors were encountered: