From 4ae63f4fd75c1851630130181dd6f23bb243c0e3 Mon Sep 17 00:00:00 2001
From: Erik Munson <emunson@netflix.com>
Date: Wed, 23 Oct 2019 16:04:58 -0700
Subject: [PATCH] fix(core/instance): use fragment on non-UP health code path
 (#7555)

Turns out that the `<OverlayTrigger>` component needs whatever you give it as children to be a single node. With the change introduced in #7520, the code path that runs when the health status is `UP` works fine, but any non-UP status hits the `<OverlayTrigger>` path and blows up/fails to render because there's two root nodes. This just wraps those two nodes in a fragment.
---
 .../instance/loadBalancer/InstanceLoadBalancerHealth.tsx    | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/app/scripts/modules/core/src/instance/loadBalancer/InstanceLoadBalancerHealth.tsx b/app/scripts/modules/core/src/instance/loadBalancer/InstanceLoadBalancerHealth.tsx
index ffabb4de9f1..39ec5d1d435 100644
--- a/app/scripts/modules/core/src/instance/loadBalancer/InstanceLoadBalancerHealth.tsx
+++ b/app/scripts/modules/core/src/instance/loadBalancer/InstanceLoadBalancerHealth.tsx
@@ -65,8 +65,10 @@ export class InstanceLoadBalancerHealth extends React.Component<IInstanceLoadBal
       const tooltip = <Tooltip id={name}>{tooltipText}</Tooltip>;
       return (
         <OverlayTrigger placement="left" overlay={tooltip}>
-          {healthDiv}
-          {ipAddress && healthCheckPath && healthCheckLinkSpan}
+          <>
+            {healthDiv}
+            {ipAddress && healthCheckPath && healthCheckLinkSpan}
+          </>
         </OverlayTrigger>
       );
     }