[Bug 569248] Re: deregistered node is still reported on the CLC

2010-12-03 Thread Launchpad Bug Tracker
[Expired for eucalyptus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: eucalyptus (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu.

[Bug 569248] Re: deregistered node is still reported on the CLC

2010-04-26 Thread Thierry Carrez
Carlos, when you say still, the CLC lists them, you mean that running sudo euca_conf --list-nodes on the CLC still results in: registered nodes: 10.55.55.3 UEC-TEST1 10.55.55.6 UEC-TEST1 10.55.55.8 UEC-TEST1 10.55.55.3 UEC-TEST2 10.55.55.6 UEC-TEST2 10.55.55.8 UEC-TEST2 ? **

[Bug 569248] Re: deregistered node is still reported on the CLC

2010-04-26 Thread C de-Avillez
Yes, this is what I found. On the other hand, there was also a misconfiguration of topo4 (CLC+Walrus, {CC1+SC1, NC1}, {CC2+SC2, NC2-1, NC2-2}). Both CCs were configured with the same cluster name (UEC- TEST1), which caused a series of issues. This *might* have contributed: the correct topology

[Bug 569248] Re: deregistered node is still reported on the CLC

2010-04-23 Thread C de-Avillez
A note: due to the misconfiguration, both CC/SC's started their life as UEC-TEST1. I manually edited santol's config for UEC-TEST2. -- deregistered node is still reported on the CLC https://bugs.launchpad.net/bugs/569248 You received this bug notification because you are a member of Ubuntu

[Bug 569248] Re: deregistered node is still reported on the CLC

2010-04-23 Thread C de-Avillez
Hum. Deregistering both CCs, and re-registering them again corrects it: ubu...@cempedak:~$ sudo euca_conf --list-nodes registered nodes: 10.55.55.8 UEC-TEST1 10.55.55.3 UEC-TEST2 10.55.55.6 UEC-TEST2 ubu...@cempedak:~$ -- deregistered node is still reported on the CLC