Hmmm, there seems to be a bug somewhere in pcs or Ipaddr2:
I cannot CREATE a resource with a VLAN interface identifier such as eth0.030, but if I create a resource without specifying the interface, I can later update the resource with PCS adding the NIC parameter "eth.030" and then the IP is nicely assigned to trhe correct vlan interface. I tried to figure out where the error occurs, but I am running out of time so for now I will live with the workaround.
Regards, Jakob Curdes _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
