[Bug 572388] Re: NC not available when auto registrating with second cloud present

[brian mullan]

Are both "clouds" on the same network segment?
If so is there any chance that the NC of the 2nd cloud confused as to which
CLC it belongs to?
Is DHCP configured in both CLC's?


On Wed, May 19, 2010 at 3:52 AM, Torsten Spindler <torsten at canonical.com>wrote:

> The first existing cloud was using the simple topology: one front-end,
> one node controller. The cloud we installed first was made up of 3
> machines: 1 CLC+Walrus, 1 CC+SC, 2 NC.
>
> After installing the second cloud, both clouds had two clusters
> registered against it. However, the output of euca-describe-
> availability-zones verbose showed that the nodes were not registered
> correctly against the CC of the second cloud. So we could never start an
> instance in the second cloud.
>
> --
> NC not available when auto registrating with second cloud present
> https://bugs.launchpad.net/bugs/572388
> You received this bug notification because you are subscribed to
> eucalyptus in ubuntu.
>

-- 
NC not available when auto registrating with second cloud present
https://bugs.launchpad.net/bugs/572388
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.