-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using latest vagrant version throws an exception #14
Comments
I can re-create this error and also can confirm that adding the workaround you pointed to resolves the issue:
Once I got all cleaned up, I will create a new PR for the AWS fixes. |
hseipp
added a commit
to hseipp/StorageScaleVagrant
that referenced
this issue
Jul 2, 2021
Fix issue #14 (IBM#14) by adding the work-around as described in the vagrant-aws project to the Vagrantfiles. Fix issue #15 (IBM#15) which is in fact a vagrant-aws one by documenting a work-around. Fix issue #16 (IBM#16) by excempting the management network key configuration for the AWS deployment. On AWS there exists no management network. Object deployment is supported by adding a VIP address to the single NIC on an AWS deployment and using that for the CES services as well as for the Spectrum Scale cluster network.
hseipp
added a commit
that referenced
this issue
Dec 1, 2023
Merge pull request #46 from hseipp/main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running the vagrant up throws the following exception:
It is related to this issue: mitchellh/vagrant-aws#566
I solved the issue using the workaround suggested on this comment: mitchellh/vagrant-aws#566 (comment)
I think
vagrant-aws
seems to be not very actively maintained, general solution would be to use differnt aws vagrant plugin.The text was updated successfully, but these errors were encountered: