I was thinking the same thing. Right now there's really not much logic around
it, just grab the first one.
One problem that may arise has to do with initialization order. It may be that
the time that the MAC address is read database access may not be available.
Regardless it should be det
Possibly, I would say it makes more sense to find what interface the
cluster.node.ip (I think) is using, then get the MAC address from that
interface?
Then if users add interfaces and change the order through udev it will be
persistent (to an extent).
The only problem I can think of is if it's usi
Glad that helped. Seems that we should change CloudStack to ignore mac
addresses that are 00:..:00. If you want to put in a bug you can assign it me
and I'll look into changing that.
Darren
> On Oct 26, 2013, at 5:35 AM, Marty Sweet wrote:
>
> Hi Darren, thanks for the heads up about that s
Hi Darren, thanks for the heads up about that script.
Old Networking Setup:
eth0 eth1 -> management0
management0.11 -> vlan11
management0.12 -> vlan12
Turns out in true Ubuntu Networking fashion bond0 was being created for no
reason and was appearing in ifconfig -a (so the script was pulling out
Hi Darren,
Thanks for getting back to me. I will set the networking config up again
and run the commands you sent me over the next couple of days.
Thanks,
Marty
On Tue, Oct 22, 2013 at 11:39 PM, Darren Shepherd <
darren.s.sheph...@gmail.com> wrote:
> Well that wasn't very useful message. If y
Well that wasn't very useful message. If you can find the cloud-utils
jar on your server run
java -cp /cloud-utils-4.1.1.jar com.cloud.utils.net.MacAddress
That will output what its finding for the mac address. Also run an
"ifconfig -a" from the command line. If you won't mind sending the
outp
Just noticed I didn't include the log:
http://pastebin.com/wUtCsSAb
Marty
On Tue, Oct 22, 2013 at 10:38 PM, Marty Sweet wrote:
> Hi Darren,
>
> Maybe I'm getting confused with an issue I had with the Agents around that
> time!
> The error message I got was very cryptic. Having a fresh look at
Hi Darren,
Maybe I'm getting confused with an issue I had with the Agents around that
time!
The error message I got was very cryptic. Having a fresh look at the source
code:
https://github.com/apache/cloudstack/blob/04cdd90a84f4be5ba02778fe0cd352a4b1c39a13/utils/src/org/apache/cloudstack/utils/id
Do you have a specific error from a log? I was not aware that
CloudStack would look for interfaces w/ eth*, em*. In the code it
just does "ifconfig -a" to list the devices. By creating a bond, the
mac address CloudStack finds will probably change then I could imagine
something could possibly fai
