You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Andy Kurth (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/08 20:59:57 UTC
[jira] [Resolved] (VCL-256) configure_networking.vbs script cannot
identify private/public interfaces when using virtualization software
[ https://issues.apache.org/jira/browse/VCL-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Kurth resolved VCL-256.
----------------------------
Resolution: Fixed
Script is no longer called.
> configure_networking.vbs script cannot identify private/public interfaces when using virtualization software
> ------------------------------------------------------------------------------------------------------------
>
> Key: VCL-256
> URL: https://issues.apache.org/jira/browse/VCL-256
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.0, 2.1, 2.2, incubation
> Environment: Windows XP bare metal or VMware images
> Reporter: Tony Miller
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> The configure_networking.vbs script, which identifies the private and public network interfaces for use by vcld, does not gracefully handle the case where additional network interfaces are created by VirtualBox, VMware, or other software. Because there are now more than the normal two, the script has a difficult time identifying privarte vs. public. The end result is that the script sets the public interface to 0.0.0.0. That further leads to the machine not properly bringing up sshd and the management nodes never completing reservations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira