| yuriys | clarkb, fungi I confirmed on our network devices that when I added two more blocks to your cloud after I added the initial three, it didn't append, but overwrote the 3. So just confirming the issue of those IP blocks not routing from the error above. Will solve today (hopefully), no action needed on your side, once it's fixed on the core switch side, it will just work as intended. | 12:19 |
|---|---|---|
| fungi | yuriys: thanks for the heads up, obviously it's no rush, nodepool will just keep trying to reach things it boots in there and won't actually hand them off to zuul for running jobs until they're actually usable | 13:00 |
| fungi | so it's not doing any harm other than heating the planet a bit more by constantly booting and deleting server instances | 13:00 |
| yuriys | fungi issues is resolved now, provisioned an instance to test with ip 173.231.255.106 which belongs to the previous network block that timed out and it now pings. | 13:31 |
| fungi | yuriys: awesome, thanks again! i'll keep an eye on the launch failures graph and see if we end up with any other issues, but that's probably done it | 13:33 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!