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.

Sign up for GitHub

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

Jump to bottom

AppScale fails to start if eth0's IP is not externally accessible #143

Closed
shatterednirvana opened this issue Nov 27, 2012 · 0 comments
Closed

AppScale fails to start if eth0's IP is not externally accessible #143

shatterednirvana opened this issue Nov 27, 2012 · 0 comments
Assignees
@shatterednirvana
Labels
Type: Bug
Milestone
1.6.5

Comments

@shatterednirvana
Copy link
Contributor

The AppController currently assumes that eth0 always has an IP address that other nodes (and the tools) can communicate with it via. This is not true if we're running VirtualBox on our laptop and the VM gets an accessible IP on eth1 (or many other scenarios that conceptually reduce to this).
shatterednirvana added a commit to shatterednirvana/appscale that referenced this issue Nov 27, 2012
@shatterednirvana
correctly starting AppScale if more than one eth device is present (a…
71023b1 
…nd the IP to use is not on eth0), fixing issue AppScale#143
@shatterednirvana shatterednirvana mentioned this issue Nov 27, 2012
Merged
nlake44 added a commit to nlake44/appscale that referenced this issue Sep 30, 2013
@nlake44
Merge pull request AppScale#143 from shatterednirvana/removed-ruby-tools
e6f6604 
removed ruby tools implementation since it's all python now
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shatterednirvana shatterednirvana

Labels
Type: Bug
Projects
None yet
Milestone
1.6.5
Development

No branches or pull requests
1 participant
@shatterednirvana