Does this bug manifest when the instance is connected to a network in a correctly identified tenant that is not the admin tenant, or is it only when the network is not in a correctly identified tenant (as per comment #3)?
Does this bug manifest when the instance is connected to a network in a correctly identified tenant that is not the admin tenant, or is it only when the network is not in a correctly identified tenant (as per comment #3)?