How Do I Handle "Invalid Input for Rules" That Occurs with a LoadBalancer Ingress?

Symptom

An alarm is generated when a LoadBalancer ingress is created or updated and information similar to the following is displayed:

Update elb(*****) listener(*****)error: status_code: 400, resp_body:{"error_msg":"Invalid input for rules. Reason: the number of condition for per policy must be no larger than 10.","error_code":"ELB.8902"."request_id": *****"}

Solution

The error code ELB.8902 in this alarm indicates that there is an issue with the request parameter. For details, see Error Codes You will need to adjust the parameter settings based on the cause of the error.

Symptom	Possible Cause	Solution
The alarm contains the following information: Reason: the number of condition for per policy must be no larger than 10.	Because of the limitations imposed by the ELB API, there are certain restrictions when using advanced forwarding rules. In each forwarding policy, including the domain name, path, HTTP request method, HTTP request header, query string, CIDR block, and cookie forwarding rules, a maximum of 10 conditions can be configured for all types of forwarding rules. Each parameter value in a rule is considered as one condition. For example, if you have one domain name forwarding rule and one path forwarding rule in a forwarding policy, you can add up to eight character strings if you include the query string forwarding rules. For details about the advanced forwarding rules, see Configuring Advanced Forwarding Actions for a LoadBalancer Ingress.	Modify the ingress configuration and make sure that the number of rules in the forwarding policy does not exceed the maximum limit.

Symptom

Possible Cause

Solution

The alarm contains the following information:

Reason: the number of condition for per policy must be no larger than 10.

Because of the limitations imposed by the ELB API, there are certain restrictions when using advanced forwarding rules. In each forwarding policy, including the domain name, path, HTTP request method, HTTP request header, query string, CIDR block, and cookie forwarding rules, a maximum of 10 conditions can be configured for all types of forwarding rules. Each parameter value in a rule is considered as one condition.

For example, if you have one domain name forwarding rule and one path forwarding rule in a forwarding policy, you can add up to eight character strings if you include the query string forwarding rules.

For details about the advanced forwarding rules, see Configuring Advanced Forwarding Actions for a LoadBalancer Ingress.

Modify the ingress configuration and make sure that the number of rules in the forwarding policy does not exceed the maximum limit.

Parent Topic: Network Exception Troubleshooting