bgpd: do not update default bgp instance as bgp evpn at creation

When creating a default BGP instance, the configuration of a VRF BGP
instance used as EVPN backbone is not possible because of the config
message:

Actually, at default BGP creation, the EVPN backbone is set, whereas
this instance can be used for something else. Fix this by not setting
too early the EVPN setup.

Fixes: ("e2f3a930c54c") bgpd: Allow non-default instance to be EVPN one

Signed-off-by: Philippe Guibert <[email protected]>

Author: pguibert6WIND

bgpd/bgpd.c

@@ -3464,12 +3464,6 @@ static struct bgp *bgp_create(as_t *as, const char *name,
 				   name, bgp->as_pretty);
 	}
 
-	/* Default the EVPN VRF to the default one */
-	if (inst_type == BGP_INSTANCE_TYPE_DEFAULT && !bgp_master.bgp_evpn) {
-		bgp_lock(bgp);
-		bm->bgp_evpn = bgp;
-	}
-
 	bgp_lock(bgp);
 
 	bgp->allow_martian = false;