eucalyptus ignores VNET_INTERFACE setting when creating volumes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eucalyptus |
Won't Fix
|
Undecided
|
Unassigned | ||
| eucalyptus (Ubuntu) |
Fix Released
|
Wishlist
|
Dustin Kirkland | ||
Bug Description
Package versions this relates to: eucalyptus (cloud, cc, common, gl, walrus, java-common, sc) --> 1.6.2-0ubuntu13
I have a small trial cloud setup as follows:
HOST_A is the cloud controller, walrus and storage controller and also acts as cluster controller for CLUSTER_A
HOST_B is the cluster controller for CLUSTER_B
Two other hosts are NCs for CLUSTER_A and CLUSTER_B respectively
I can run and access instances in either cluster, so the entire infrastructure seems to be configured fine.
The only problem I have is with the SC on HOST_A as it seems to ignore the "VNET_INTERFACE" setting in /etc/eucalyptus
In HOST_A's config the VNET_INTERFACE is set to "br0", however when I issue "euca-create-volume -s 1 -z ZONE_A" the volume is created and presented on "eth0" instead of "br0":
root@host_a:~# ps -ef | fgrep vblade
root 6983 6161 0 12:30 ? 00:00:00 /usr/sbin/vblade 0 2 eth0 /dev/vg-
So far I have tried the following steps:
- de-registered the SC
- stopped and disabled all eucalyptus services
- apt-get purged the eucalyptus-sc package
- rebooted
- installed the eucalyptus-sc package
- verified VNET_INTERFACE value
- enabled all eucalyptus services
- started eucalyptus with CLEAN=1
The behaviour still persists, so I guess there is either something I have missed or there is a bug in one of the eucalyptus packages. Attached are my (anonymized a bit) cloud-debug.log and eucalyptus.conf.
| ptashek (ptashek) wrote | #1 |
| ptashek (ptashek) wrote | #2 |
| ptashek (ptashek) wrote | #3 |
| affects: | ubuntu → eucalyptus (Ubuntu) |
| Neil Soman (neilsoman) wrote | #4 |
| Changed in eucalyptus: | |
| status: | New → Won't Fix |
| Neil Soman (neilsoman) wrote | #5 |
| Mathias Gug (mathiaz) wrote | #6 |
| Changed in eucalyptus (Ubuntu): | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in eucalyptus (Ubuntu): | |
| status: | Triaged → In Progress |
| assignee: | nobody → Dustin Kirkland (kirkland) |
| status: | In Progress → Fix Committed |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in eucalyptus (Ubuntu): | |
| status: | Fix Committed → Fix Released |
I was able to reproduce this bug on the latest 10.04 packages --> eucalyptus (all of them) @ 1.6.2-0ubuntu14 and vblade @ 20-1ubuntu1. This host has not been running as an SC ever before, so this can be treated as a clean install I guess.