[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
** 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 in CLC+Walrus / CC+SC / NC topology To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/527648/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
** 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 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: 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 subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 $EUCA_USER to match (working) behavior with scp - use local $RSYNC_RSH variable, rather than exporting to the environment * eucalyptus-cc.templates, eucalyptus-nc.config, eucalyptus-nc.templates, eucalyptus-sc.templates: fix the default cluster name 'cluster1', as this was not getting populated in the -nc if the default cluster name was accepted on the CC, LP: #530937 [ Thierry Carrez ] * Fixed eucalyptus-nc.templates so that eucalyptus-nc postinst doesn't fail * eucalyptus-udeb.*: Preseed detected cloud for the CC installer to pick it up and set VNET_CLOUDIP in separated CC case (LP: #527648) -- Thierry Carrez thierry.car...@ubuntu.com Wed, 03 Mar 2010 14:02:24 +0100 ** Changed in: eucalyptus (Ubuntu Lucid) Status: In Progress = Fix Released -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 preseed in the target (magic that involves some logfile, see how
Colin seeded the postfix debconf value).
There is also a trick in the value cloud-address can get: when set by
the user it's an IP address, when discovered by euca_find_component
its IPaddress:port. It's all normalized before being used in the
postinst by ${cloud%:*}: you should probably do the same before
writing VNET_CLOUDIP.
--
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 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
** 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 subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 Nurmi (nurmi) ** Changed in: eucalyptus Status: Confirmed = Fix Committed -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 FORWARD ACCEPT' on both CC and CLC. Then: $ euca-run-instances --key sm-kp emi-B1E21863 $ euca-describe-instances i-3F580796 RESERVATION r-4AB408BB admin default INSTANCEi-3F580796 emi-B1E2186310.55.55.100172.19.1.2 running sm-kp 0 m1.small2010-03-01T19:18:37.335Z UEC-TEST1 eki-1E661D65eri-F91C1CD8 The instance boots and console-output shows ec2-init ran successfully (ie, metadata service could be reached from the instance). Now, on cempadek: ping 10.55.55.100 succeeds ping 172.19.1.2 fails The instance Maybe there was some user error, or misunderstanding, but it appears that from the CLC I can only reach the external address, not the internal. From santol (CC) either can be used. -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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, eucalyptus/cloud-address remains blank. So I just think we need to determine that address in a different manner. I'll take another look. ** Changed in: eucalyptus (Ubuntu Lucid) Assignee: Colin Watson (cjwatson) = Dustin Kirkland (kirkland) -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 the install chroot. Needs a little more investigation. ** Attachment added: syslog.gz http://launchpadlibrarian.net/39855525/syslog.gz -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
** 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 subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 ] * debian/eucalyptus-cc.postinst, debian/eucalyptus-udeb.finish-install, debian/eucalyptus-cc.templates, debian/eucalyptus-udeb.postinst: - Have the CLC add it's IP address to the served preseed file, such the CC can pick it up and write it to eucalyptus.local.conf as the required VNET_CLOUDIP value (on separated CC, CLC installs), LP: #527648 -- Dustin Kirkland kirkl...@ubuntu.com Fri, 26 Feb 2010 11:41:45 -0600 ** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu ** Changed in: eucalyptus (Ubuntu Lucid) Status: In Progress = Fix Released -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 euca_conf (should send this upstream) -- Dustin Kirkland kirkl...@ubuntu.com Fri, 26 Feb 2010 16:19:56 -0600 ** Changed in: eucalyptus (Ubuntu Lucid) Status: In Progress = Fix Released -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
** 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 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: 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 Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 I can ping karmic instances OK from the CLC. Adding VNET_CLOUDIP=ip.address.of.clc to the CC's eucalyptus.conf solves the second one. I can boot a karmic or lucid instance and SSH into it. More investigation is needed to see why the FORWARD chain isn't set up to accept the packets as it should... -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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, or should it only be set if the CLC is separate ? Re: euca-authorize IIUC it needs to be run only once (from anywhere) for the security group you want to use (default being the default one). You probably need to be admin to modify the default one. -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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', then you will need to run the command again to authorize the 'foobar/default' group. In a nutshell, the authorizations are tied to user/group pairs, and only need to be run once per user/group pair. Regards, -Dan -- 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527648] Re: Running instances can't be contacted from CLC in CLC+Walrus / CC+SC / NC topology
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 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 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
