"Could not find an allocated subnet for node" による SDN Pod の CrashLoopBackOff

Issue

• スケールアップ中、または新しいクラスターのインストール中に、いくつかのノード上の SDN Pod が次のエラーでクラッシュします。

I0512 19:55:06.890709   16017 cmd.go:160] Starting node networking (v0.0.0-alpha.0-59-g6e937ad0)
I0512 19:55:06.890730   16017 node.go:378] Starting openshift-sdn network plugin
W0512 19:55:06.895709   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...
W0512 19:55:07.901192   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...
W0512 19:55:09.406959   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...
W0512 19:55:11.662406   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...
W0512 19:55:15.044086   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...
W0512 19:55:20.112497   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...
W0512 19:55:27.711840   16017 subnets.go:159] Could not find an allocated subnet for node: ip-10-0-0-1.ec2.internal, Waiting...

• ノードのネットワークが利用可能にならないため、これによって新しいノードの起動が妨げられています。