[Bug 684816] [NEW] Node Controller (NC) fail to register

Public bug reported: I had been having problems with UEC on ubuntu 10.10 getting the Node Controllers (NC) to register correctly. Finally, after searching both the Ubuntu and Eucalyptus forums (and launchpad bugs) I found the following message on the Eucalyptus forum: = = = = = = =

[Bug 684816] Re: Node Controller (NC) fail to register

** Description changed: I had been having problems with UEC on ubuntu 10.10 getting the Node Controllers (NC) to register correctly. Finally, after searching both the Ubuntu and Eucalyptus forums (and launchpad bugs) I found the following message on the Eucalyptus forum: = = = = =

Re: [Bug 684816] Re: Node Controller (NC) fail to register

I've done that. (use sudo to register the nodes).. the NC does not register correctly.. From google searches It seems a lot of people are having this same problem ? thanks tho'. On Mon, Dec 6, 2010 at 11:00 AM, C de-Avillez hgg...@ubuntu.com wrote: Thank you for opening this bug and helping

Re: [Bug 684816] Re: Node Controller (NC) fail to register

I'd forgotten about this because I'd gotten an email that someone had junked it already? That was a couple months ago. I would have to go back and retest but from watching some of the lists there still seems to be a fair number of people describing the same symptoms. On Fri, Mar 25, 2011 at

Re: [Bug 493422] Re: ubuntu enterprise cloud's store downlonad image

On Ubuntu's website a search for UEC (ubuntu enterprise cloud) give you: https://help.ubuntu.com/community/UEC/PackageInstall Since UEC is based on Eucalyptus I think you could learn a lot by downloading and reading the Eucalyptus Beginner’s Guide – UEC edition v2.0 –

Re: [Bug 577237] Re: Default UEC install using 1 pc 4 CLC, CC, Walrus etc 1 NC - VM subnet mask is created as 255.255.255.255 - unreachable by a 192.168.1.x 255.255.255.0 class C subnet

Mattias the wireless router attached to my cable modem provides a NAT'd DHCP 192.16.x.x network *clc* (192.168.x.x 255.255.255.*0*) --- |--[*wireless bridge*]---[ (wifi=192.168.1.1)* wireless router *(eth=70.x.x.x)

[Bug 1149410] Re: Stuck on Trying to connect to the Juju environment

I have the same problem as reported in the original post of this bug ... except ... my use case is different. I created an OpenStack instance of ubuntu 14.04. I installed juju on that instance and configured it for Local Provider (re lxc). I then bootstrapped and deployed Juju-GUI which

Re: [Bug 1373981] Re: ubuntu 14.10 server, amd64 - lxc-start fails to start container

Serge I don't have the problem now. But there was a round of sw upgrades during that time and I suspect whatever had caused it was fixed somewhere. The original AMI though should still exhibit the problem I guess. *ubuntu-utopic-14.10-beta1-amd64-server-20140826 (ami-3021fb58)* Brian On

[Bug 1400745] [NEW] lxc-create -t download and specifying Lucid for release ends w/only IPv6 addr

Public bug reported: I don't know if this is considered an LXC bug or a bug in the download rootfs build process but I recently had a need to use a container with a lucid image. I created it using: $ sudo lxc-create -t download -n my_test and specified Lucid, amd64 after creating the

[Bug 1512749] [NEW] lxcbr0 dissappears on Ubuntu 15.10

Public bug reported: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn

Re: [Bug 1512749] Please test proposed package

will do... On Tue, Nov 3, 2015 at 4:20 PM, Stéphane Graber wrote: > Hello brian, or anyone else affected, > > Accepted network-manager into wily-proposed. The package will build now > and be available at https://launchpad.net/ubuntu/+source/network- >