Closed datianshi closed 8 years ago
Thank you for reporting it. It is a known network issue. Which region are you using? You can try to use East US.
I am in Central US
Before Central US is patched, you can try it on East US. After Central US is ready, we will update you.
Thanks @AbelHu What regions currently are patched and agnostic of this issue? When you are saying patch? Is this going to happen on azure side or bosh CPI side?
same problem on West US.
Pleaee try it in east us.
Best Regards, Abel HU
? 2016?2?1??19:13?Stu Charlton notifications@github.com<mailto:notifications@github.com> ???
same problem on West US.
Reply to this email directly or view it on GitHubhttps://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/issues/84#issuecomment-177919399.
@AbelHu is this problem specific to the BOSH CPI? or is it just Azure in those regions?
@danhigham It is an issue of Azure network. It has been fixed in East US. Other regions will be soon.
@datianshi and @danhigham Any update on this issue? Please let us know if you hit any problem. Thanks
@danhigham @datianshi , This issue has been fixed so I close it.
When using bosh deploy .
I got Error 450002: Timed out pinging to c6f09e6a-2ff1-42f0-bd2e-3d98e6574d34 after 600 seconds
This errors comes with a significant chance. It is kind of more than 40% for me (Unluck!!!!), while sometimes succeed. When it happened, I looked at the azure portal. All the vnet, subnets and IPs are placed correctly, as well as no azure error logs happened. Ping this VM from the internal network (A jump host on the same subnet) does not work. Ironically, if the failed VM has a VIP, I can ssh into it through the public VIP, however the network inside of failed VM can not route through the subnet gateway. Guess subnet gateway failed on the bosh deployed VM is causing timeout.
Any thoughts whether the bosh side could cause the problem? Or it is just flaky Microsoft Azure network?
stemcell 3163, CPI release 6, bosh release 250