updateNetworkACLItem with partialupgrade=false leaves a rule broken when cidrlist or traffictype is left out, and drops an ICMP type given with tcp
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- java
- Área
- backend-api-design, cloud
Línea de trabajo
Start by reading updateNetworkACLItem, transferDataToNetworkAclRulePojo(), NetworkACLItemDaoImpl.update() and NetworkACLItemCidrsDaoImpl.updateCidrs(); trace validation alongside createNetworkACL and the default partial upgrade path. Check the existing tests for network ACL rule updates and add coverage for missing required fields, invalid traffic type, ICMP parameters with another protocol, and rollback when CIDR updates fail. Done means invalid calls fail before leaving a partial update and valid calls preserve the documented behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
problem
updateNetworkACLItem with partialupgrade=false replaces every field of the rule with what the call passes. Two cases go wrong.
1. A field left out is written as null, and the rule is left broken.
When cidrlist or traffictype is left out, transferDataToNetworkAclRulePojo() sets them to null. NetworkACLItemDaoImpl.update() then writes the rule row and only afterwards updates the CIDRs, outside a transaction:
- with
cidrlistleft out,NetworkACLItemCidrsDaoImpl.updateCidrs()fails withCannot invoke "java.util.List.size()" because "cidrs" is null. The call fails, but the row has already been committed with the null traffic type. - from then on
listNetworkACLsfor that list fails withCannot invoke "...TrafficType.toString()" because ... getTrafficType() is null, and applying the list fails the same way inSetNetworkACLCommand, until the rule is updated again with every field.
When protocol is left out, the call fails earlier with a NullPointerException in updateIcmpCodeAndTypeFullUpgrade(). Nothing is written in that case, but the error is an NPE rather than a message. (#14046 removes that NPE; the rule would then be saved without a protocol, which createNetworkACL never allows.)
action left out is already handled: it becomes Allow, as on create.
2. An ICMP type or code given with another protocol is silently dropped.
partialupgrade=false protocol=tcp icmptype=8 is accepted, and the rule is saved as tcp without the ICMP type. createNetworkACL with the same parameters, and the same update with the default partialupgrade=true, both refuse it with "Can specify icmpCode and icmpType for ICMP protocol only".
versions
4.20 and later for the dropped ICMP type; the null fields since partialupgrade was added in 4.12. Seen on 4.22 and main.
The steps to reproduce the bug
- In a VPC, create an ACL list and a rule on it:
createNetworkACL aclid=<list> protocol=tcp startport=80 endport=80 cidrlist=10.1.2.0/24 action=allow traffictype=ingress. updateNetworkACLItem id=<rule> partialupgrade=false protocol=udp startport=53 endport=53. It fails with thecidrs is nullNPE.listNetworkACLs aclid=<list>now fails with thegetTrafficType() is nullNPE.updateNetworkACLItem id=<rule> partialupgrade=false protocol=tcp cidrlist=10.1.2.0/24 action=allow traffictype=ingressrepairs it.- On an ICMP rule,
updateNetworkACLItem id=<rule> partialupgrade=false protocol=tcp icmptype=8 cidrlist=10.1.2.0/24 action=allow traffictype=ingressis accepted, and the rule is tcp with no ICMP type.
What to do about it?
- With
partialupgrade=false, refuse the call whenprotocol,cidrlistortraffictypeis missing, before anything is written. Defaulting them as create does would silently widen a rule to every address, or turn an egress rule into an ingress rule. - Refuse an invalid
traffictypeon update, as create does, instead of ignoring it. - Keep an ICMP type or code given with another protocol, so that the existing validation refuses it.
- Write the rule row and its CIDRs in one transaction, so that a failure on the CIDRs can't leave the rule half updated.
- Lenguaje dominante
- Java
- Estrellas
- 3.1k
- Forks
- 1.4k
- Merge medio
- 7 d 16 h
- PR fusionados (30 d)
- 15
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/cloudstack
-
resizeVolume of a running system VM's volume is accepted but the VM never sees the new sizePosiblemente ocupada @bhouse-nexthop la tomó hace 3 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
apache/cloudstack#14645 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
VR reports a load balancer change as applied when haproxy.cfg cannot be replacedPosiblemente ocupada @bhouse-nexthop la tomó hace 4 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/cloudstack#14633 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
restartNetwork reports a ResourceUnavailableException as an unexpected error (530), unlike restartVPC (534)Posiblemente ocupada @bhouse-nexthop la tomó hace 4 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/cloudstack#14631 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
apache/cloudstack#14625 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Remote access VPN users are disconnected on every LB, ACL, port forward or firewall change (xl2tpd restarted on every iptables pass)Posiblemente ocupada @willbennett-devops la tomó hace 12 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
apache/cloudstack#14545 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de apache/cloudstack
Issues similares
-
[FEATURE] Expose external refresh, node-level translog and warmer statsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertountriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
opensearch-project/opensearch-prometheus-exporter#680 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
-
Good First Issue
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
hiero-ledger/hiero-sdk-java#3059 ·
Los mantenedores suelen responder en 1 día