Skip to content
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

error: EC2 machine 'm' does not have a private IPv4 address (yet) #48

Open
coretemp opened this issue Apr 25, 2018 · 2 comments
Open

error: EC2 machine 'm' does not have a private IPv4 address (yet) #48

coretemp opened this issue Apr 25, 2018 · 2 comments

Comments

@coretemp
Copy link

I am looking in the AWS Console, and I see after a refresh that machine m has a private IPv4 address. However, nixops ssh m reports:

error: EC2 machine 'm' does not have a private IPv4 address (yet)

This is a bug or a design bug. It could use the AWS EC2 API to locate the IPv4 address for example.

@coretemp
Copy link
Author

There is another inconsistency here, which is that
ssh -i a.pem root@<ip as rapported by AWS Console> works.

IMHO, nixops ssh m should work in at least the cases that ssh works as displayed by the Amazon Connect button.

All this happened when I was downgrading (the instance type) of two exactly the same machines of which only one came up fine (let's call that machine n).

@coretemp
Copy link
Author

nixops check returns:

m............> warning: IP address has changed, you may need to run ‘nixops deploy’, which is not useful, because nixops deploy has no effect at all.

@grahamc grahamc transferred this issue from NixOS/nixops Apr 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant