So the first, most basic aspect of this problem is that these components
assume that they should register as 'localhost', or the same system
running the CLC.
This assumption actually appears to be part of our problem with
automatic registration.
When I used the real, external IP address in the upstart scripts, I got
the following in my logs:
r...@cloud:/etc/init# tail -n1 /var/log/eucalyptus/*regist*
==> /var/log/eucalyptus/cc-registration.log <==
SUCCESS: new cluster 'canyonedge' on host '192.168.1.121' successfully
registered.
==> /var/log/eucalyptus/sc-registration.log <==
SUCCESS: new SC for cluster 'canyonedge' on host '192.168.1.121' successfully
registered.
==> /var/log/eucalyptus/walrus-registration.log <==
SUCCESS: new walrus on host '192.168.1.121' successfully registered.
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Status: Triaged => In Progress
** Summary changed:
- Automated registration assumes that walrus, SC and CC are running on the same
host as the CLC
+ Walrus, SC and CC registrations hardcode 'localhost'
--
Walrus, SC and CC registrations hardcode 'localhost'
https://bugs.launchpad.net/bugs/437058
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
