On 3/17/19 1:15 PM, Robert Varga wrote:

On 16/03/2019 19:06, Jamo Luhrsen wrote:

I'm digging through the neon csit failures to help sign off for the
release, and came across a failure in neon csit that is not there in
fluorine.

We need to explain it or fix it so we can get the (now late) Neon
release done.

Essentially, the failure is that a GET to
/restconf/config/neutron:neutron/l2gatewayConnections
is coming back 404 after the last l2-gateway-connection is deleted
(done with the neutron CLI). So we get a 404 [1] and this:

"error-tag":"data-missing","error-message":"Request could not be completed
because the relevant data model content does not exist"


In Fluorine [2], we get a 200 and this:

    {"l2gatewayConnections":{}}


How do we want to handle it? I'll make a note on the tracking sheet [3]
and keep it as pending for now.

Empty lists are disappearing in Neon:
https://lists.opendaylight.org/pipermail/yangtools-dev/2018-September/002308.html,
so this is fully expected.

Got it. test code will need to be changed to handle this, but I marked
the tracking sheet as OKAY. Looks like we are good to release.

JamO

Regards,
Robert

On 16/03/2019 19:06, Jamo Luhrsen wrote:

I'm digging through the neon csit failures to help sign off for the
release, and came across a failure in neon csit that is not there in
fluorine.

We need to explain it or fix it so we can get the (now late) Neon
release done.

Essentially, the failure is that a GET to
/restconf/config/neutron:neutron/l2gatewayConnections
is coming back 404 after the last l2-gateway-connection is deleted
(done with the neutron CLI). So we get a 404 [1] and this:

"error-tag":"data-missing","error-message":"Request could not be completed
because the relevant data model content does not exist"


In Fluorine [2], we get a 200 and this:

    {"l2gatewayConnections":{}}


How do we want to handle it? I'll make a note on the tracking sheet [3]
and keep it as pending for now.

Empty lists are disappearing in Neon:
https://lists.opendaylight.org/pipermail/yangtools-dev/2018-September/002308.html,
so this is fully expected.

Regards,
Robert

I'm digging through the neon csit failures to help sign off for the
release, and came across a failure in neon csit that is not there in
fluorine.

We need to explain it or fix it so we can get the (now late) Neon
release done.

Essentially, the failure is that a GET to /restconf/config/neutron:neutron/l2gatewayConnections
is coming back 404 after the last l2-gateway-connection is deleted
(done with the neutron CLI). So we get a 404 [1] and this:

"error-tag":"data-missing","error-message":"Request could not be completed
because the relevant data model content does not exist"


In Fluorine [2], we get a 200 and this:

{"l2gatewayConnections":{}}


How do we want to handle it? I'll make a note on the tracking sheet [3]
and keep it as pending for now.



Thanks,
JamO

[1] https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-hwvtep-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-neon/217/robot-plugin/log_full.html.gz#s1-s1-s1-t20-k2-k5-k1-k2-k1
[2] https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-hwvtep-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-fluorine/217/robot-plugin/log_full.html.gz#s1-s1-s1-t20-k2-k5-k1-k2-k1
[3] https://docs.google.com/spreadsheets/d/1sIoApv2fFp0wJcPK7m6lQDtjbUonRANrs5upSeD_DyI/edit#gid=1352305345