WeightError(value)Values: UNDEFINED_WEIGHT_ERROR (0): A value indicating that the enum field is not set. INVALID_WEIGHT (383698400): The response to a Health Check probe had the HTTP response header field X-Load-Balancing-Endpoint-Weight, but its content was invalid (i.e., not a non-negative single-precision floating-point number in decimal string representation). MISSING_WEIGHT (384027537): The response to a Health Check probe did not have the HTTP response header field X-Load-Balancing-Endpoint-Weight. UNAVAILABLE_WEIGHT (439464295): This is the value when the accompanied health status is either TIMEOUT (i.e.,the Health Check probe was not able to get a response in time) or UNKNOWN. For the latter, it should be typically because there has not been sufficient time to parse and report the weight for a new backend (which is with 0.0.0.0 ip address). However, it can be also due to an outage case for which the health status is explicitly reset to UNKNOWN. WEIGHT_NONE (502428831): This is the default value when WeightReportMode is DISABLE, and is also the initial value when WeightReportMode has just updated to ENABLE or DRY_RUN and there has not been sufficient time to parse and report the backend weight.