You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using clocker 1.2.0-SNAPSHOT (at commit 7c9346c, while testing a couple of unrelated fixes for issues #288 and #290)...
I successfully deployed a 2 host clocker+calico cluster in BlueBox. I then deployed many entities that created containers (using Brooklyn's MachineEntity) to cause the cluster to auto-scale.
It create a third host, but this hung on startup (waiting forever for post-start to finish). It is waiting for SdnAgent agent = Entities.attributeSupplierWhenReady(this, SdnAgent.SDN_AGENT).get();.
Looking at the CalicoNode for that host, its service.state is "ON_FIRE" and its service.isUp is "false". Looking in the debug log (grep -E "OKsRTXuY|10.101.1.162"), I see the following error:
Using clocker 1.2.0-SNAPSHOT (at commit 7c9346c, while testing a couple of unrelated fixes for issues #288 and #290)...
I successfully deployed a 2 host clocker+calico cluster in BlueBox. I then deployed many entities that created containers (using Brooklyn's
MachineEntity
) to cause the cluster to auto-scale.It create a third host, but this hung on startup (waiting forever for post-start to finish). It is waiting for
SdnAgent agent = Entities.attributeSupplierWhenReady(this, SdnAgent.SDN_AGENT).get();
.Looking at the CalicoNode for that host, its service.state is "ON_FIRE" and its service.isUp is "false". Looking in the debug log (
grep -E "OKsRTXuY|10.101.1.162"
), I see the following error:It then goes on to repeatedly fail the check-running for
CalicoNodeImpl{id=OKsRTXuY}
.The text was updated successfully, but these errors were encountered: