Open issues

Unchaught IndexOutOfBoundsException for an incoming flow state
MNA-1288
wrong "Math.abs(hash_or_random) % N" pattern
MNA-1347
Octavia on Midonet 5.4
MNA-1346
build libgtest during our build process
MNA-1345
Midonet packages don't work on Ubuntu 18.04 bionic
MNA-1344
Tailor MidoNet to kubernetes
MNA-1343
Provide external connectivity
MNA-1342
golang 1.11
MNA-1340
multi cluster support
MNA-1336
exception handler of DisruptorPacketWorker doesn't work
MNA-1331
kubernetes 1.11 support
MNA-1325
nativeMeterRegistry fm2str returns released array
MNA-1324
implement network policy
MNA-1319
kubernetes events shouldn't replace logs
MNA-1316
ip4_mac_table rest api seems broken (error handing?)
MNA-1315
python-midonetclient doesn't support IPv4-MAC Pair
MNA-1314
IPv4-MAC Pair rest api is documented poorly
MNA-1313
MacPort rest api is documented poorly
MNA-1312
python-midonetclient doesn't support MacPort
MNA-1311
robustness improvement
MNA-1310
datapath port entangler assumes periodic interface events
MNA-1308
Minions JVM heap startup size is not set
MNA-1302
mysterious error on "./gradlew debian" due to setuptools
MNA-1299
dubious code in native metering
MNA-1298
prometheus metrics
MNA-1296
ease upgrade
MNA-1295
an update of a tunnel zone can conflict with itself
MNA-1293
ease deployment
MNA-1289
midonet-cli doesn't allow to specify id when creating an object
MNA-1287
make upgrade safer
MNA-1285
multi arch suport
MNA-1284
Rules that reference non-existing ip address groups are not removed from chains
MNA-1283
Service loadbalance among endpoints
MNA-1264
Improve MidoNet-Kubernetes MVP
MNA-1262
Deploy MN using manifests
MNA-1261
Containerize MN components
MNA-1260
Design of k8s integration (MVP)
MNA-1256
API: Router Port update clears portMac
MNA-1251
API: internal error for PortLink with portID specified
MNA-1248
API: REST API Router Port portSubnet is not documented
MNA-1247
Release 5.6.1
MNA-1221
mm-ctl falls back to legacy even when unnecessary
MNA-1218
review process is not documented
MNA-1210
CI logs are not publically available
MNA-1209
midolman-prepare tries to remove unrelated interfaces
MNA-1204
wdog doesn't monitor the old agent in case of fast reboot
MNA-1203
the "backup" agent failure during fast reboot can make wdog leave the "main" agent
MNA-1202
midolman.log is less useful during fast reboot
MNA-1197
mm-reboot can send SIGUSR1 to unrelated "wdog" process
MNA-1195
reclaim_datapath=true confuses metadata proxy (at least)
MNA-1194
issue 1 of 234

Unchaught IndexOutOfBoundsException for an incoming flow state

Description

Hi,

we are using Midonet in version 5.6.0 with Ubuntu16.06 and an OpenStack Pike installation. At this early stage we have two hypervisors and two gateway nodes in addition with integrated VTEPs on Cumulus switches.

Our Midolmans on the gateway nodes get constantly restarted after a flow state update (coming from the other gateway). The gateways are configured to be the flooding proxies (forced with flooding-proxy-weight).

Noticeable things:

  • directly bevor an exception we see a new nat mapping for a hardware server connected via VTEP

  • there is always the same index (234) and capacity (204) in the exception

  • there are no exceptions if we shut down the servers behind the hardware VTEPs

  • if we force the flooding proxy to a hypervisor, the exceptions occur in the same moment on both gateways

  • the connected servers and the setup didn't change during our tests

We got the following debug logs from a midolman on a gateway:

Do you need more information or debug logs? How can we help to narrow down the problem?

Kind regards,
Achim

Assignee

Unassigned

Reporter

Fritz Enboe

Labels

None

Affects versions

Priority

Critical
Configure