On Thu, Apr 15, 2010 at 05:50:35PM -, Etienne Goyer wrote:
> Good news, but can we clarify the addressing part nonetheless? Ie, can
> VNET_PUBLICIPS and the IP of VNET_PUBINTERFACE on the CC be on the same
> subnet?
>
Yes they can.
--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com
--
Good news, but can we clarify the addressing part nonetheless? Ie, can
VNET_PUBLICIPS and the IP of VNET_PUBINTERFACE on the CC be on the same
subnet?
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received this bug notification becaus
The issue was that the uec-testing-scripts were not starting the
instances in the correct group. euca-run-instances wasn't using the -g
option so that instances were started in the default group. If the
default group had already been updated to authorize ssh traffic the test
would succeed.
I've pu
About comment 12, I suspect this is because those are the CLC config
files, not the CC ones.
Getting eucalyptus.[local.]conf for the CC would give some additional
insight on VNET_PUBLICIPS and the network configuration.
--
multi-machine topology, cannot reach an instance from the CLC
https://bug
Dan,
Can you confirm/explain/enhance Etienne's suspicions?
:-Dustin
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hmm, in my setup here, I have a 255.255.255.0 network, 10.1.1.X.
My CC is on 10.1.1.72, and my PUBLIC_IPS are 10.1.1.100-10.1.1.199.
This is working for me.
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received this bug notification
Just to explain a bit further. The reason I am suspecting
VNET_PUBLICIPS to be wrong is that eth0 on the CC has two IP in the
10.55.55.0/24 range (see comment #11). I presume 10.55.55.8 is the CC
actual IP, and comment #7 indicate that 10.55.55.100 is the IP of the
instance. In this case, VNET_P
Looking at the comment history, I think it might be that the
VNET_PUBLICIPS range and the address of VNET_PUBINTERFACE are in the
same subnet, which cannot possibly work. Which is a known limitation
related to netfilter; ask Dan about it.
But without knowing what the value of VNET_PUBLICIPS on th
from a NC (Sapodilla):
ubu...@sapodilla:~$ ip address show
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdi
Just a question: why is VNET_PUBLICIPS commented in eucalyptus.conf?
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
IP addresses and forward status on Marula:
ubu...@marula:~$ ip address show
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: et
Some more information about the network configuration on the CC and the
NC could help to compare our working systems with the failing one:
ip address show
sysctl -n net.ipv4.ip_forward
Could it be linked to the metadata service vs. vlan issue that mathiaz
reported ?
--
multi-machine topology, c
Re-assigning to Mathias. I'm fairly certain that this is an issue
either particular to the lab setup or to the test automation, as I
haven't been able to reproduce it here, and Carlos seems to have triaged
it down to a networking issue (traceroute failing from the CLC to the
guest).
Carlos has re
** Attachment added: "single test log"
http://launchpadlibrarian.net/44097815/single_test.log.2010-04-13_193218
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received this bug notification because you are a member of Ubuntu
Bugs, w
traceroute output:
ubu...@cempedak:~/uec-testing-scripts$ sudo traceroute -n -p 22 -P tcp
10.55.55.100
[sudo] password for ubuntu:
traceroute to 10.55.55.100 (10.55.55.100), 30 hops max, 60 byte packets
1 10.55.55.100 12.337 ms 0.062 ms 0.057 ms
2 * * *
3 * * *
4 *^C
ubu...@cempedak:~
I tested it again thie evening, with Dustin monitoring. We again used
lucid-amd64-topo2, and based the installs on the daily server/UEC images
(releases.ubuntu.com is not accessible from tamarind, so I could not use
Beta2).
Installation was uneventful.
I then ran the config_single.yaml test. No p
I definitely can't reproduce on my local topology2 install. Lowering
priority until we can reproduce outside the test automation (which still
needs to be fixed/stabilized for Lucid).
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: High => Medium
** Changed in: eucalyptus (Ubuntu Lucid)
I'm setting up a 5-machine topology right now to confirm it's a testrig
automation artifact, in which case I'll lower the priority.
You mentioned running with several different users. Could it be that the
"euca-authorize" call was not issued for all users (but just for the
first one) resulting in
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: High
Assignee: Dustin Kirkland (kirkland)
Status: Incomplete
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received this bug notification because you are a member of
Marking High, as this needs to be resolved before Lucid's release. I'm
going to to target it at 10.04 GA.
Marking Incomplete, as we don't yet have enough information to debug
this yet.
I ran instances without a problem in the same setup (manually
installed). I'm hoping there's just a problem wi
According to http://iso.qa.ubuntu.com/qatracker/result/3918/496 this
works on a manual setup, so maybe it's a test artifact from the
testrig... Would be good to confirm though.
--
multi-machine topology, cannot reach an instance from the CLC
https://bugs.launchpad.net/bugs/559230
You received thi
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43545405/Dependencies.txt
** Attachment added: "EucalyptusCloudDebugLog.gz"
http://launchpadlibrarian.net/43545406/EucalyptusCloudDebugLog.gz
** Attachment added: "EucalyptusCloudOutputLog.gz"
http://launchpadlibraria
22 matches
Mail list logo
