@fenar,
Does this occur when using multiple nodegroups `fuel nodegroup --env <id>`
I was only able to reproduce this when the discovered node's admin interface is not a member of the default fuelweb_admin network (network of id=1)
@fenar,
Does this occur when using multiple nodegroups `fuel nodegroup --env <id>`
I was only able to reproduce this when the discovered node's admin interface is not a member of the default fuelweb_admin network (network of id=1)