I'm just wondering how "The requested IP address (192.168.5.5) belongs to cnet1, but the target NIC does not."
would help the user? Wouldn't "The requested IP address (192.168.5.5) belongs to cnet1, but the target NIC is not configured for it. Did you forget a 'network=cnet1' parameter?" help more? Also, the man page of gnt-instance and gnt-network do not really explain the relationship of IP allocation and networks (i.e. you can't select an IP which lies in a network without also selecting the network, and so on). I guess some improvement there would have helped the user in question quite a bit. Thanks, Thomas On Fri, Apr 26, 2013 at 4:13 PM, Guido Trotter <[email protected]> wrote: > On Fri, Apr 26, 2013 at 4:00 PM, Thomas Thrainer <[email protected]> > wrote: > > IIRC, this patch is in response to a discussion on the ganeti list. > > > > In this particular case, the new error message wouldn't help either. > > > > To quote from the original message (from Constantinos): > > > >> Ganeti will not put the NIC into any network and will just try > >> to assign the IP (for backwards compatibility). However, > >> if this IP is included in one of your networks, Ganeti will > >> complain again (that's your case). Indeed the message > >> should be more descriptive. > > > > So in this case, the IP as well as the NIC belong to the right network, > but > > the only problem was that it was not specified in gnt-instance > add/modify. > > > > Well, no, technically the nic doesn't belong to the network. It just > has an IP from it. > It might also "accidentally" be connected to it, but this is not > guaranteed or necessary in the setup. > > Thanks, > > Guido > -- Thomas Thrainer | Software Engineer | [email protected] | Google Germany GmbH Dienerstr. 12 80331 München Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Katherine Stephens
