Comment 4 for bug 1524640

Revision history for this message
Sam Stoelinga (sammiestoel) wrote :

@Aleksandr: Many people run Fuel in datacenters without internet access. So the network checker will not be able to catch the problem with the gateway if we are using Fuel as the mirror. So I don't think this should be marked as invalid
Instead we should at least make sure that the network checker will fail if the gateway is not ping-able if that would result in failed deployment. Just checking whether mirrors are accessible is not enough if we use Fuel as mirror.
Anyway I still think that the deployment shouldn't fail and the correct fix would be to continue the deployment. Where exactly do we need the public gateway working for correct VIPs?

I've changed it to Confirmed again. This is one of the most common issues that partners / customers contact me about when they are doing an offline fuel installation / deployment and it just fails. They often won't get deep enough inside the Puppet logs to understand that ping public_vip failing means that their public gateway wasn't ping-able. It's unacceptable from a usability perspective.