** Changed in: eucalyptus
Status: New = Fix Released
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
[maverick] Registration unreliable
https://bugs.launchpad.net/bugs/609112
You received this bug notification because you are a member of Ubuntu
In the case uncovered by ISO testing, it was
--register-{cluster,walrus,sc} that was regularly half-failing (returns
1). We'll test the r1220 to see if it also fixes this one.
--
[maverick] Registration unreliable
https://bugs.launchpad.net/bugs/609112
You received this bug notification because
@Thierry, A new upstream revision should be landing shortly. I'll try
and reproduce against that.
--
[maverick] Registration unreliable
https://bugs.launchpad.net/bugs/609112
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
This bug was fixed in the package eucalyptus - 2.0~bzr1224-0ubuntu1
---
eucalyptus (2.0~bzr1224-0ubuntu1) maverick; urgency=low
[ Dave Walker (Daviey) ]
* New upstream merge, r1224, should fix LP: #610259, #609112, #613033
* debian/patches/10-disable-iscsi.patch: Removed, we
** Branch linked: lp:ubuntu/eucalyptus
--
[maverick] Registration unreliable
https://bugs.launchpad.net/bugs/609112
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
I am not sure if i have understood the issue here correctly. Is it
specific to --register-nodes or does it also effect
--register-{cluster,walrus,sc}? If cluster, walrus, sc were also
causing problems, could you see if the current r1220 resolves the
problem for them (it does not address nodes).
** Tags added: iso-testing
--
[maverick] Registration unreliable
https://bugs.launchpad.net/bugs/609112
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
** Description changed:
- Eucalyptus 2.0, running topo2 (fully separated topology). After
- installing, no nodes are registered. I went into the CC, and manually
- ran a euca_conf --discover-nodes:
+ Eucalyptus 2.0, running topo1, A3 candidate
+ After installing the CLC+WC+CC+SC, sometimes (40%
