Marking this bug as fix released since the original bug
https://bugs.launchpad.net/bugs/628328 has been fixed.
@rowez: if you still see the issue please re-open.
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member
@rowez: apologies, I meant, please file a new bug since this one is
considered released now.
--
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/627963
Title:
[maverick] Inconsistent
Marking this bug as fix released since the original bug
https://bugs.launchpad.net/bugs/628328 has been fixed.
@rowez: if you still see the issue please re-open.
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member
@rowez: apologies, I meant, please file a new bug since this one is
considered released now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/627963
Title:
[maverick] Inconsistent certificates prevent
Got the problem as described above on a Intel Xeon. Did the workaround
#9 and --register-cluster without stop/start eucalyptus!
Using eucalyptus (2.0+bzr1241-0ubuntu4.1) on Maverick Meerkat (10.10).
After the reboot, again --deregister-cluster and then --register-
cluster. No error's!
But it is
Got the problem as described above on a Intel Xeon. Did the workaround
#9 and --register-cluster without stop/start eucalyptus!
Using eucalyptus (2.0+bzr1241-0ubuntu4.1) on Maverick Meerkat (10.10).
After the reboot, again --deregister-cluster and then --register-
cluster. No error's!
But it is
Dave reproduced it. Seems like running two concurrent registration
process (one for ipv4 and one for ipv6) can have bad side-effects. Bug
628025 will be marked as duplicate, since it's a symptom of the same
problem.
** Changed in: eucalyptus (Ubuntu Maverick)
Importance: Medium = High
--
** Branch linked: lp:~ubuntu-virt/ubuntu/maverick/eucalyptus/2.0
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug was fixed in the package eucalyptus - 2.0+bzr1241-0ubuntu2
---
eucalyptus (2.0+bzr1241-0ubuntu2) maverick; urgency=low
* debian/registration/uec_component_listener.c: Ignore IPv6 avahi broadcasts.
Both IPv4 and IPv6 broadcasts are dispatched from the components. A
** Branch linked: lp:ubuntu/eucalyptus
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Dave reproduced it. Seems like running two concurrent registration
process (one for ipv4 and one for ipv6) can have bad side-effects. Bug
628025 will be marked as duplicate, since it's a symptom of the same
problem.
** Changed in: eucalyptus (Ubuntu Maverick)
Importance: Medium = High
--
** Branch linked: lp:~ubuntu-virt/ubuntu/maverick/eucalyptus/2.0
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package eucalyptus - 2.0+bzr1241-0ubuntu2
---
eucalyptus (2.0+bzr1241-0ubuntu2) maverick; urgency=low
* debian/registration/uec_component_listener.c: Ignore IPv6 avahi broadcasts.
Both IPv4 and IPv6 broadcasts are dispatched from the components. A
** Branch linked: lp:ubuntu/eucalyptus
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
So this is still happening as of todays ISO. If for some reason
euca_conf doesn't say the cluster is registered, re-registering it might
apparently still duplicates keys. I did the following: install UEC
topology 1, upgrade to latest version, and I got a certificate mismatch
again. Downgrading to
So this is still happening as of todays ISO. If for some reason
euca_conf doesn't say the cluster is registered, re-registering it might
apparently still duplicates keys. I did the following: install UEC
topology 1, upgrade to latest version, and I got a certificate mismatch
again. Downgrading to
This is believed to have been fixed with bug #628328 (eucalyptus
2.0+bzr1239-0ubuntu1), if following verification it isn't - please re-
open this bug.
** Changed in: eucalyptus (Ubuntu Maverick)
Status: Confirmed = Fix Released
--
[maverick] Inconsistent certificates prevent CC to start
Marking fix released, as Dimitri has confirmed this has landed in there
branch.
** Changed in: eucalyptus
Status: New = Fix Released
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification
I think the correct status in eucalyptus upstream should be fix
committed since they didn't release with it (I think) yet.
** Changed in: eucalyptus
Status: Fix Released = Fix Committed
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
Marking fix released, as Dimitri has confirmed this has landed in there
branch.
** Changed in: eucalyptus
Status: New = Fix Released
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification
I think the correct status in eucalyptus upstream should be fix
committed since they didn't release with it (I think) yet.
** Changed in: eucalyptus
Status: Fix Released = Fix Committed
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
Theoretically the autoregistration system checks (using euca_conf
--list-clusters) if the cluster has already been registered, so it
shouldn't retry. Maybe bug 628025 causes duplicate tries, though ?
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
** Tags added: server-mrs
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: (unassigned) = Dave Walker (davewalker)
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you
Theoretically the autoregistration system checks (using euca_conf
--list-clusters) if the cluster has already been registered, so it
shouldn't retry. Maybe bug 628025 causes duplicate tries, though ?
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
** Tags added: server-mrs
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: (unassigned) = Dave Walker (davewalker)
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you
Directory /var/lib/eucalyptus/keys/Cluster Name is only relevant on
the CLC, since it needs to have keys for multiple clusters. For all
other components the keys are in /var/lib/eucalyptus/keys. Hence, if CLC
and a CC are co-located, you will see the same keys in two places.
Cloud key is created
I have just reinstalled from scratch (i.e., full Ubuntu install +
Eucalyptus all-in-one). I just installed the CLC+Walrus+CC/SC.
Upon logging in, I verified the /var/lib/eucalyptus/keys/*.pem to be the
same as /var/lib/eucalyptus/keys/UEC-TEST1/*.pem. CC was up and running
and on certificate
er. Second paragraph above: CC was up and running and *NO* certificate
errors.
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Server Team, which is
ubu...@cempedak:/var/lib/eucalyptus$ sudo ls -lR keys
keys:
total 64
-rw-r--r-- 1 eucalyptus eucalyptus 1147 2010-09-01 12:56 cloud-cert.pem
-rw-r--r-- 1 eucalyptus eucalyptus 1675 2010-09-01 12:55 cloud-pk.pem
-rw-r--r-- 1 eucalyptus eucalyptus 1151 2010-09-01 12:56 cluster-cert.pem
-rw-r--r--
After copying the keys as in comment #9, I restarted Euca -- all is
fine.
I then rebooted, and the problem is back.
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: Confirmed
** Changed in: eucalyptus (Ubuntu Maverick)
Milestone: None = ubuntu-10.10
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You
** Summary changed:
- CC doesn't start correctly, CLC struggles with certificates
+ [maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You
With three installs in top1:
1) I believe i saw this issue, but didn't keep the install long enough to be
exactly sure.
2) I reproduced this issue
3) Did not reproduce this issue, worked as expected.
Certainly seems like a race, or other inconsistency.
--
[maverick] Inconsistent certificates
^^ This was performed on amd64 of the current beta candidate.
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Directory /var/lib/eucalyptus/keys/Cluster Name is only relevant on
the CLC, since it needs to have keys for multiple clusters. For all
other components the keys are in /var/lib/eucalyptus/keys. Hence, if CLC
and a CC are co-located, you will see the same keys in two places.
Cloud key is created
I have just reinstalled from scratch (i.e., full Ubuntu install +
Eucalyptus all-in-one). I just installed the CLC+Walrus+CC/SC.
Upon logging in, I verified the /var/lib/eucalyptus/keys/*.pem to be the
same as /var/lib/eucalyptus/keys/UEC-TEST1/*.pem. CC was up and running
and on certificate
er. Second paragraph above: CC was up and running and *NO* certificate
errors.
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ubu...@cempedak:/var/lib/eucalyptus$ sudo ls -lR keys
keys:
total 64
-rw-r--r-- 1 eucalyptus eucalyptus 1147 2010-09-01 12:56 cloud-cert.pem
-rw-r--r-- 1 eucalyptus eucalyptus 1675 2010-09-01 12:55 cloud-pk.pem
-rw-r--r-- 1 eucalyptus eucalyptus 1151 2010-09-01 12:56 cluster-cert.pem
-rw-r--r--
After copying the keys as in comment #9, I restarted Euca -- all is
fine.
I then rebooted, and the problem is back.
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a
Carlos - thanks for looking into that! Cluster keys are only generated
when --register-cluster is invoked. Trying to register an already
registered cluster is supposed to be harmless, but turns out that it is
not. (I just filed https://bugs.launchpad.net/eucalyptus/+bug/628328
for that.) I
I meant: If so, avoiding the redundant registrations may be the best
solution.
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: Confirmed
** Changed in: eucalyptus (Ubuntu Maverick)
Milestone: None = ubuntu-10.10
--
[maverick] Inconsistent certificates prevent CC to start correctly (no cc.log)
https://bugs.launchpad.net/bugs/627963
You
42 matches
Mail list logo
