** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
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/527648
Title:
Running instances can't be contacted from CLC
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: Dustin Kirkland (kirkland) = Thierry Carrez (ttx)
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Confirmed = Triaged
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Triaged = In Progress
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
https://bugs.launchpad.net/bugs/527648
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu7
---
eucalyptus (1.6.2-0ubuntu7) lucid; urgency=low
[ Dustin Kirkland ]
* tools/euca_conf.in: fix manual node registration with rsync, LP: #530942
- fix one stray 'rsync', replace with $RSYNC
- use sudo -u
The main issue is that eucalyptus/cloud-address was just meant to hold
the value of the user answer to the No CLC detected, enter IP address
question from the installer (in order to get an IP address to get the
CC/SC/Walrus preseed from). In order to use it for this use case, you'll
need to
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
https://bugs.launchpad.net/bugs/527648
You received this bug notification because you are a member of Ubuntu
Server Team, which is
The upstream part of this fix (add VNET_CLOUDIP and VNET_LOCALIP to
euca_conf --import-conf) is in revno 1202
-Dan
** Changed in: eucalyptus
Status: New = Confirmed
** Changed in: eucalyptus
Importance: Undecided = Low
** Changed in: eucalyptus
Assignee: (unassigned) = Daniel
I tried working around this as described above. In data center UEC at the
moment:
santol (10.55.55.7): cluster-controller (CC)
cempadek (10.55.55.2): cloud-controller (CLC)
ubu...@santol:~$ grep VNET_CLOUDIP /etc/eucalyptus/eucalyptus.local.conf
VNET_CLOUDIP=10.55.55.2
I ran 'sudo iptables -P
Aha, I think I understand why ...
During the CLC install, I think the user is prompted for eucalyptus
/cloud-address (if it exists), and if the user leaves it blank (and none
is detected on the network), then the installer suggests installing this
machine as the CLC. Hence,
Attaching /var/log/installer/syslog from my CC/SC install.
Search this file for 10.1.1.71 (the address of the CLC) and you'll see
that eucalyptus/cloud-address is set to 10.1.1.71:8773, at least for a
bit.
Maybe it's set correctly in the installer environment but that doesn't
get propagated to
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Confirmed = In Progress
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
https://bugs.launchpad.net/bugs/527648
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu5
---
eucalyptus (1.6.2-0ubuntu5) lucid; urgency=low
[ Colin Watson ]
* Preseed postfix/main_mailer_type on the cloud controller, not the
cluster controller (LP: #455746).
[ Dustin Kirkland ]
*
Reopening, not yet fixed.
VNET_CLOUDIP did not make it into the preseed file, unfortunately.
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Fix Released = In Progress
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
Running
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu6
---
eucalyptus (1.6.2-0ubuntu6) lucid; urgency=low
* debian/eucalyptus-cc.config, debian/eucalyptus-udeb.finish-install,
tools/euca_conf.in: continuation of previous fixes to LP: #527648;
must add VNET_CLOUDIP to
** Summary changed:
- Running instances can't be contacted in CLC+Walrus / CC+SC / NC topology
+ Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
Setting up the missing VNET_CLOUDIP on CC seems to be the only thing
preventing it to work.
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
https://bugs.launchpad.net/bugs/527648
You received this bug notification because you are a member of Ubuntu
Server
I mean, setting up VNET_CLOUDIP on CC makes it work :)
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
https://bugs.launchpad.net/bugs/527648
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
OK, further testing reveals there are two issues:
* The FORWARD chain is blocking connections from CLC to instance
* The CC doesn't know the way to the metadata service (missing VNET_CLOUDIP)
Defaulting to accept on the FORWARD chain works around the first issue:
sudo iptables -P FORWARD ACCEPT
Re: I found I only needed to make the VNET_CLOUDIP=... change
That's what I originally found, but then when I tried to reproduce the fix I
also needed to tweak the FORWARD rule to connect from CLC to instance. I guess
I got something wrong.
Dan, can we set VNET_CLOUDIP on the CC in all cases,
euca-authorize sets up a rule that is specific to a user/security group.
For example, if you are using admin credentials and the group you're
authorizing is 'default', then the rule will apply to all instances run
by 'admin' in the group 'default'. If you acting as different user, say
'foobar',
Dan-
Just to be clear ... The command:
euca-authorize default -P tcp -p 22 -s 0.0.0.0/0
Only needs to be run once, and only from an account with admin
privileges, correct?
In other words, this doesn't need to be run in more than one place (CLC,
and CC, or some such), right?
--
Running
Actually, I found I only needed to make the VNET_CLOUDIP=... change. I
did not do anything to my iptables.
I'll investigate where the VNET_CLOUDIP needs to be written to
eucalyptus.local.conf.
--
Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC
topology
22 matches
Mail list logo
