Advanced search
Log In
New Account
  
Home My Page Project Cloud Code Snippets Project Openings ESbox
Summary Forums Tracker Lists Tasks News SCM Files Wiki

Bugs: Browse | Download .csv

[#4710] Handle changing host address better

Please login

State:
Open
Date:
2009-10-21 15:02
Priority:
3
Submitted By:
Ed Swartz (eswartz)
Assigned To:
Nobody (None)
Summary:
Handle changing host address better

Detailed description
When using VMs, the host and target address are both important.  When the target address is wrong, it's obvious something
is wrong (since the dialogs show this address).  But when the host address is wrong, you can only tell this in the warning
page in the Build Machines setup.  A wrong address will cause shared folder mounting to fail (or existing shares to
fail) but this is not detected or reported anywhere else.

Probably this should be fixed in two ways: 

(1) Validate the host address in more places.  Ping the host from the VM to validate it.

(2) Allow the Machine Setup pane to use a floating host address (e.g. "<auto>").  Generally you want
the host address on the same subnet as the target address, unless the target address is for NAT.  We might be able to
guess this in most cases.

Followup

Message
Date: 2009-11-05 15:30
Sender: Ed Swartz

I fixed this using option (1) during the validate machines operation
in rev 2371.

Also, a recommendation that is more flexible in general is to
simply use a hostname (not an IP) in the "local address"
field.  This way, the setting is less prone to DHCP changes.
With a few fixes with regard to address equality checks, this
has worked for me for a few weeks over several DHCP changes.

Attached Files:

Name Download
No Files Currently Attached

Changes:

Field Old Value Date By
ResolutionNone2009-11-05 15:31eswartz

Terms of Use    Privacy Policy    Contribution Guidelines    Feedback

Powered By GForge Collaborative Development Environment