euca_conf --register-nodes returns 0 but the node is not registered

I'm also exhibiting the same problem, some of the background is here: http://open.eucalyptus.com/forum/cc-not-able-registersee-nodes

This needs to be reproduced, since not everyone is having that issue... Setting back to New so that we spend some cycles investigating that one.

I will reinstall our cloud and if i see this problem again i warn you.

On 25 August 2010 12:34, Thierry Carrez <email address hidden> wrote:

> This needs to be reproduced, since not everyone is having that issue...
> Setting back to New so that we spend some cycles investigating that one.
>
> ** Changed in: eucalyptus (Ubuntu)
> Status: Triaged => New
>
> ** Changed in: eucalyptus (Ubuntu)
> Importance: High => Medium
>
> --
> Problems with node registration
> https://bugs.launchpad.net/bugs/585108
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Eucalyptus: New
> Status in “eucalyptus” package in Ubuntu: New
> Status in “eucalyptus” source package in Lucid: New
>
> Bug description:
> Using ubuntu 10.04, i have eucalyptus-nc running in the node controller but
> does not have nc.log. In the cc, if i run euca_conf --discover-nodes it find
> no nodes. Even if i run euca_conf --register-nodes NODE_IP, i receive a
> success message (done), but no nodes are showed with euca_conf --list-nodes.
> euca-describe-availability-zones verbose returns 0/0 for all types.
>
> My hw configuration are with 2 machines, 1 clc, cc, sc and 1 nc.
>
> I've deregistered everything, cluster through web interface and node
> through command line, then rebooted clc/cc/sc and the nc. After reboot, the
> cluster was automatically registered, i changed the eucalytptus-cc.conf and
> the eucalyptus-sc.conf to c3cluster1 again. But euca_conf --list-nodes show
> no nodes. Even after --register-nodes 192.168.1.2 getting success message.
>
> Im sad because with ubuntu 9.10 everything was working and now with 10.04
> it does not work for some unknow reason.
>
> I have the clc/cc and the nc linked through a hub. The clc/cc have 2 NIC's,
> 1 public(10.1.2.x) and 1 private(192.168.1.X) that is used to comunicate
> with the node. In the hub i have a dhcp server that assigns IP's in the
> 10.1.2.X subnet, and it is the gw too. The network configuration in the NC
> is manual(192.168.1.2), in the private iface of CLC/CC is manual
> too(192.168.1.1) and the public iface is dhcp.
>
> Below goes all my logs and conf files, if with this you cant help me, there
> is no solution for me =/
>
> This is also discussed at
> http://forum.eucalyptus.com/forum/no-nclog#comment-11351
> CONFS:
>
> eucalytpus.conf - http://pastebin.com/w2BUzU2v
> eucalyptus.local.conf - http://pastebin.com/xBJSg5XS
> eucalyptus-cc.conf <http://pastebin.com/xBJSg5XS%0Aeucalyptus-cc.conf> -
> CC_NAME="c3cluster1"
> eucalytpus-sc.conf - SC_NAME="c3cluster1"
> eucalytpus-ipaddr.conf - http://pastebin.com/xeAaYUZC
> httpd.conf - http://pastebin.com/8FctTYiX
> /etc/network/interfaces<http://pastebin.com/8FctTYiX%0A/etc/network/interfaces>-
> http://pastebin.com/K59BWSDi
>
> LOGS:
> http-cc_error_log - http://pastebin.com/rU6ZJY9c
> axis2c.log - http://pastebin.com/8DF6s1VF
> cc.log - http://pastebin.com/K50x3aZr
> cloud-debug.log - http://pastebin.com/2jPR1X4S
> cloud-error.log <http://pastebin.com/2jPR1X4S%0Acloud-error.log> -
> http://pastebin.com/BSQUSVZZ
> cloud-output.log - http://pastebin.com/26sudQh8
> registration.log - http://pastebin.com/UvWzs8DP
>
> ...

OK, I just reproduced this one.

Autoregistration calls euca_conf --register-nodes correctly, and euca_conf --register nodes returns 0 (SUCCESS). It writes the new node IP to /var/lib/eucalyptus/nodes.list, but:

- the new node doesn't show up in euca_conf --list-nodes
- the new node doesn't get polled

this is on Maverick 20100831 ISO.

This might just be a consequence of bug 627963.

Great. If you need any help, im here to help with what i can.

On 1 September 2010 06:46, Thierry Carrez <email address hidden> wrote:

> OK, I just reproduced this one.
>
> Autoregistration calls euca_conf --register-nodes correctly, and
> euca_conf --register nodes returns 0 (SUCCESS). It writes the new node
> IP to /var/lib/eucalyptus/nodes.list, but:
>
> - the new node doesn't show up in euca_conf --list-nodes
> - the new node doesn't get polled
>
> this is on Maverick 20100831 ISO.
>
> ** Changed in: eucalyptus (Ubuntu)
> Importance: Medium => High
>
> ** Changed in: eucalyptus (Ubuntu)
> Status: New => Confirmed
>
> ** Summary changed:
>
> - Problems with node registration
> + euca_conf --register-nodes returns 0 but the node is not registered
>
> --
> euca_conf --register-nodes returns 0 but the node is not registered
> https://bugs.launchpad.net/bugs/585108
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Eucalyptus: New
> Status in “eucalyptus” package in Ubuntu: Confirmed
> Status in “eucalyptus” source package in Lucid: New
>
> Bug description:
> Using ubuntu 10.04, i have eucalyptus-nc running in the node controller but
> does not have nc.log. In the cc, if i run euca_conf --discover-nodes it find
> no nodes. Even if i run euca_conf --register-nodes NODE_IP, i receive a
> success message (done), but no nodes are showed with euca_conf --list-nodes.
> euca-describe-availability-zones verbose returns 0/0 for all types.
>
> My hw configuration are with 2 machines, 1 clc, cc, sc and 1 nc.
>
> I've deregistered everything, cluster through web interface and node
> through command line, then rebooted clc/cc/sc and the nc. After reboot, the
> cluster was automatically registered, i changed the eucalytptus-cc.conf and
> the eucalyptus-sc.conf to c3cluster1 again. But euca_conf --list-nodes show
> no nodes. Even after --register-nodes 192.168.1.2 getting success message.
>
> Im sad because with ubuntu 9.10 everything was working and now with 10.04
> it does not work for some unknow reason.
>
> I have the clc/cc and the nc linked through a hub. The clc/cc have 2 NIC's,
> 1 public(10.1.2.x) and 1 private(192.168.1.X) that is used to comunicate
> with the node. In the hub i have a dhcp server that assigns IP's in the
> 10.1.2.X subnet, and it is the gw too. The network configuration in the NC
> is manual(192.168.1.2), in the private iface of CLC/CC is manual
> too(192.168.1.1) and the public iface is dhcp.
>
> Below goes all my logs and conf files, if with this you cant help me, there
> is no solution for me =/
>
> This is also discussed at
> http://forum.eucalyptus.com/forum/no-nclog#comment-11351
> CONFS:
>
> eucalytpus.conf - http://pastebin.com/w2BUzU2v
> eucalyptus.local.conf - http://pastebin.com/xBJSg5XS
> eucalyptus-cc.conf <http://pastebin.com/xBJSg5XS%0Aeucalyptus-cc.conf> -
> CC_NAME="c3cluster1"
> eucalytpus-sc.conf - SC_NAME="c3cluster1"
> eucalytpus-ipaddr.conf - http://pastebin.com/xeAaYUZC
> httpd.conf - http://pastebin.com/8FctTYiX
> /etc/network/interfaces<http://pastebin.com/8FctTYiX%0A/etc/network/interfaces>-
> http://pastebin.com/K59BWSDi
>
> LOGS:
> http-cc_...

Right, this behavior happens when the CC is not running, in which case it would not be a root issue, only a consequence.
If you happen to reproduce it, please confirm that the CC is not running (nothing flowing in /var/lib/eucalyptus/cc.log), in which case you could close that one as a dupe of the other...

When i executed the register node command, im sure the cc was running.

On 1 September 2010 11:36, Thierry Carrez <email address hidden> wrote:

> Right, this behavior happens when the CC is not running, in which case it
> would not be a root issue, only a consequence.
> If you happen to reproduce it, please confirm that the CC is not running
> (nothing flowing in /var/lib/eucalyptus/cc.log), in which case you could
> close that one as a dupe of the other...
>
> ** Changed in: eucalyptus (Ubuntu)
> Importance: High => Medium
>
> --
> euca_conf --register-nodes returns 0 but the node is not registered
> https://bugs.launchpad.net/bugs/585108
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Eucalyptus: New
> Status in “eucalyptus” package in Ubuntu: Confirmed
> Status in “eucalyptus” source package in Lucid: New
>
> Bug description:
> Using ubuntu 10.04, i have eucalyptus-nc running in the node controller but
> does not have nc.log. In the cc, if i run euca_conf --discover-nodes it find
> no nodes. Even if i run euca_conf --register-nodes NODE_IP, i receive a
> success message (done), but no nodes are showed with euca_conf --list-nodes.
> euca-describe-availability-zones verbose returns 0/0 for all types.
>
> My hw configuration are with 2 machines, 1 clc, cc, sc and 1 nc.
>
> I've deregistered everything, cluster through web interface and node
> through command line, then rebooted clc/cc/sc and the nc. After reboot, the
> cluster was automatically registered, i changed the eucalytptus-cc.conf and
> the eucalyptus-sc.conf to c3cluster1 again. But euca_conf --list-nodes show
> no nodes. Even after --register-nodes 192.168.1.2 getting success message.
>
> Im sad because with ubuntu 9.10 everything was working and now with 10.04
> it does not work for some unknow reason.
>
> I have the clc/cc and the nc linked through a hub. The clc/cc have 2 NIC's,
> 1 public(10.1.2.x) and 1 private(192.168.1.X) that is used to comunicate
> with the node. In the hub i have a dhcp server that assigns IP's in the
> 10.1.2.X subnet, and it is the gw too. The network configuration in the NC
> is manual(192.168.1.2), in the private iface of CLC/CC is manual
> too(192.168.1.1) and the public iface is dhcp.
>
> Below goes all my logs and conf files, if with this you cant help me, there
> is no solution for me =/
>
> This is also discussed at
> http://forum.eucalyptus.com/forum/no-nclog#comment-11351
> CONFS:
>
> eucalytpus.conf - http://pastebin.com/w2BUzU2v
> eucalyptus.local.conf - http://pastebin.com/xBJSg5XS
> eucalyptus-cc.conf <http://pastebin.com/xBJSg5XS%0Aeucalyptus-cc.conf> -
> CC_NAME="c3cluster1"
> eucalytpus-sc.conf - SC_NAME="c3cluster1"
> eucalytpus-ipaddr.conf - http://pastebin.com/xeAaYUZC
> httpd.conf - http://pastebin.com/8FctTYiX
> /etc/network/interfaces<http://pastebin.com/8FctTYiX%0A/etc/network/interfaces>-
> http://pastebin.com/K59BWSDi
>
> LOGS:
> http-cc_error_log - http://pastebin.com/rU6ZJY9c
> axis2c.log - http://pastebin.com/8DF6s1VF
> cc.log - http://pastebin.com/K50x3aZr
> cloud-debug.log - http://pastebin.com/2jPR1X4S
> cloud-error.log <http://pastebin.com/2jPR1X4S%0Acloud-error...

Node registration amounts to only two things: the IP being added to NODES= in eucalyptus.conf (or to nodes.list on the UEC) and keys synchronized between the CC node and the NC node. Neither CLC nor CC are involved in the operation, so they do not need to be running. For keys to be present, though, CLC must have generated them and synchronized them with the CC during cluster registration. Once CC notices a change in eucalyptus.conf, it will attempt to re-parse it, thus picking up a changed NODES= entry. (I suspect the change to nodes.list in UEC is not picked up, so CC probably needs to be re-started.)

Using Lucid 10.04:

--register-nodes success and ip-address found in /var/lib/eucalyptus/nodes.lists
but no echo from --list-nodes
and 0/0 from euca-describe-availibility-zones verbose

fix this with:
--deregister-cluster
--register-cluster

Now echo from --list-nodes and no 0/0 in free/max

NODES in /etc/eucalyptus/eucalyptus.conf is empty al the time.

Sure that cc was running!

Using Marverick Meerkat 10.10:

When trying to --register-cluster the same cluster: failed to register new cluster, please log in to the admin interface and check cloud status.

This is described in bug 627963!

Can we get confirmation this is still present?

I reinstalled the servers and this bug does not appear again.

thanks for the confirmation: I will keep the bug incomplete for a bit longer in case of more feedback, then I will mark it invalid.

No problem, if i get a error like this again i let you know.

On 22 December 2011 06:16, graziano obertelli <email address hidden>wrote:

> thanks for the confirmation: I will keep the bug incomplete for a bit
> longer in case of more feedback, then I will mark it invalid.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/585108
>
> Title:
> euca_conf --register-nodes returns 0 but the node is not registered
>
> Status in Eucalyptus:
> Incomplete
> Status in “eucalyptus” package in Ubuntu:
> Confirmed
> Status in “eucalyptus” source package in Lucid:
> New
>
> Bug description:
> Using ubuntu 10.04, i have eucalyptus-nc running in the node
> controller but does not have nc.log. In the cc, if i run euca_conf
> --discover-nodes it find no nodes. Even if i run euca_conf --register-
> nodes NODE_IP, i receive a success message (done), but no nodes are
> showed with euca_conf --list-nodes. euca-describe-availability-zones
> verbose returns 0/0 for all types.
>
> My hw configuration are with 2 machines, 1 clc, cc, sc and 1 nc.
>
> I've deregistered everything, cluster through web interface and node
> through command line, then rebooted clc/cc/sc and the nc. After
> reboot, the cluster was automatically registered, i changed the
> eucalytptus-cc.conf and the eucalyptus-sc.conf to c3cluster1 again.
> But euca_conf --list-nodes show no nodes. Even after --register-nodes
> 192.168.1.2 getting success message.
>
> Im sad because with ubuntu 9.10 everything was working and now with
> 10.04 it does not work for some unknow reason.
>
> I have the clc/cc and the nc linked through a hub. The clc/cc have 2
> NIC's, 1 public(10.1.2.x) and 1 private(192.168.1.X) that is used to
> comunicate with the node. In the hub i have a dhcp server that assigns
> IP's in the 10.1.2.X subnet, and it is the gw too. The network
> configuration in the NC is manual(192.168.1.2), in the private iface
> of CLC/CC is manual too(192.168.1.1) and the public iface is dhcp.
>
> Below goes all my logs and conf files, if with this you cant help me,
> there is no solution for me =/
>
> This is also discussed at
> http://forum.eucalyptus.com/forum/no-nclog#comment-11351
> CONFS:
>
> eucalytpus.conf - http://pastebin.com/w2BUzU2v
> eucalyptus.local.conf - http://pastebin.com/xBJSg5XS
> eucalyptus-cc.conf - CC_NAME="c3cluster1"
> eucalytpus-sc.conf - SC_NAME="c3cluster1"
> eucalytpus-ipaddr.conf - http://pastebin.com/xeAaYUZC
> httpd.conf - http://pastebin.com/8FctTYiX
> /etc/network/interfaces - http://pastebin.com/K59BWSDi
>
> LOGS:
> http-cc_error_log - http://pastebin.com/rU6ZJY9c
> axis2c.log - http://pastebin.com/8DF6s1VF
> cc.log - http://pastebin.com/K50x3aZr
> cloud-debug.log - http://pastebin.com/2jPR1X4S
> cloud-error.log - http://pastebin.com/BSQUSVZZ
> cloud-output.log - http://pastebin.com/26sudQh8
> registration.log - http://pastebin.com/UvWzs8DP
>
> If you check the cc.log, you will see that he is not updated since may
> 20, i think this is a problem right?
>
> Since now i thank you.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: euca...

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".