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.
** Changed in: eucalyptus (Ubuntu Lucid)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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.
** Changed in: eucalyptus (Ubuntu Lucid)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: eucalyptus
Assignee: Mitch Garnaat (mitch-garnaat) = (unassigned)
** Changed in: eucalyptus
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus
Assignee: Mitch Garnaat (mitch-garnaat) = (unassigned)
** Changed in: eucalyptus
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
No problem, if i get a error like this again i let you know.
On 22 December 2011 06:16, graziano obertelli
grazi...@eucalyptus.comwrote:
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
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585108
Title:
No problem, if i get a error like this again i let you know.
On 22 December 2011 06:16, graziano obertelli
grazi...@eucalyptus.comwrote:
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
I reinstalled the servers and this bug does not appear again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/585108
Title:
euca_conf --register-nodes returns 0 but the node is
I reinstalled the servers and this bug does not appear again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585108
Title:
euca_conf --register-nodes returns 0 but the node is not registered
To
Can we get confirmation this is still present?
** Changed in: eucalyptus
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/585108
Title:
euca_conf
Can we get confirmation this is still present?
** Changed in: eucalyptus
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585108
Title:
euca_conf --register-nodes
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!
--
You received this bug notification because you are a member of Ubuntu
Server Team,
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!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
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
** Changed in: eucalyptus
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
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 member of Ubuntu
Server Team, which is
** Changed in: eucalyptus
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
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 member of Ubuntu
Bugs, which is subscribed to
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,
This might just be a consequence of bug 627963.
--
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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
When i executed the register node command, im sure the cc was running.
On 1 September 2010 11:36, Thierry Carrez thierry.car...@ubuntu.com
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
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,
23 matches
Mail list logo
