[NETVIRT-1672] arbitrator-reconcile:get-active-bundle needs to be implemented in Aluminium Created: 04/Jun/20  Updated: 24/Jul/20  Resolved: 24/Jul/20

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: Aluminium
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Srinivas Rachakonda Assignee: Srinivas Rachakonda
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2020-06-04-09-27-15-555.png    

 Description   

Upgrade scripts are failing with the below errors:

 

POST Response : url=http://10.30.170.113:8181/restconf/operations/arbitrator-reconcile:get-active-bundle status=501, reason=Not Implemented

https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-upgrade-snat-conntrack-aluminium/88/

 

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-upgrade-snat-conntrack-aluminium/88/robot-plugin/log_full.html.gz

 

 

 



 Comments   
Comment by dheenadayalan b [ 05/Jun/20 ]

Unlike in magnesium branch, northbound interface addition leads to time delay of more than one minute, leads to upgrade csit failure (get active bundles failed),
Openflowplugin module was listening to port 6653/6633 , however connection establishment request between ovs and plugin made with a delay of one minute via northbound.

logs as below:
Openflowplugin startup completed as below:

Karaf.log:

020-06-04T02:28:15,339 | INFO | SystemReadyService-0 | OpenFlowPluginProviderImpl | 382 - org.opendaylight.openflowplugin.impl - 0.11.0.SNAPSHOT | onSystemBootReady() received, starting the switch connections
2020-06-04T02:28:15,547 | INFO | OFP-SwitchConnectionProvider-Udp/TcpHandler_6653-0 | TcpHandler | 392 - org.opendaylight.openflowplugin.openflowjava.openflow-protocol-impl - 0.11.0.SNAPSHOT | Switch listener started and ready to accept incoming tcp/tls connections on port: 6653
2020-06-04T02:28:15,550 | INFO | OFP-SwitchConnectionProvider-Udp/TcpHandler_6653-0 | OpenflowDiagStatusProviderImpl | 392 - org.opendaylight.openflowplugin.openflowjava.openflow-protocol-impl - 0.11.0.SNAPSHOT | The report status is OPERATIONAL for OPENFLOW_SERVER_6653
2020-06-04T02:28:15,559 | INFO | SystemReadyService-0 | SouthboundProvider | 401 - org.opendaylight.ovsdb.southbound-impl - 1.11.0.SNAPSHOT | Started OVSDB Manager (in system ready listener)
2020-06-04T02:28:15,561 | INFO | OFP-SwitchConnectionProvider-Udp/TcpHandler_6633-0 | OpenFlowPluginProviderImpl | 382 - org.opendaylight.openflowplugin.impl - 0.11.0.SNAPSHOT | All switchConnectionProviders are up and running (2).
2020-06-04T02:28:15,561 | INFO | OFP-SwitchConnectionProvider-Udp/TcpHandler_6633-0 | OpenflowDiagStatusProviderImpl | 392 - org.opendaylight.openflowplugin.openflowjava.openflow-protocol-impl - 0.11.0.SNAPSHOT | The report status is OPERATIONAL for OPENFLOW

Script for northbound setup executed @20200604 07:58:43.060 (UTC+05:30) (2020-06-04T02:28:43)

sudo ovs-vsctl set-manager tcp:10.30.170.113:6640 ptcp:6641:127.0.0.1

karaf.log:

2020-06-04T02:28:43,942 | DEBUG | jobcoordinator-main-task-6 | InterfaceTopologyStateListener | 248 - org.opendaylight.genius.interfacemanager-impl - 0.9.0.SNAPSHOT | adding bridge references for bridge: OvsdbBridgeAugmentation{getBridgeExternalIds={BridgeExternalIdsKey{_bridgeExternalIdKey=created_by}=BridgeExternalIds

{getBridgeExternalIdKey=created_by, getBridgeExternalIdValue=odl, augmentation=[]}

, BridgeExternalIdsKey{_bridgeExternalIdKey=opendaylight-iid}=BridgeExternalIds{getBridgeExternalIdKey=opendaylight-iid, getBridgeExternalIdValue=/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://uuid/758da02d-7c35-43b6-99aa-c9c57108210f/bridge/br-int'], augmentation=[]}}, getBridgeName=OvsdbBridgeName{_value=br-int}, getBridgeOtherConfigs={BridgeOtherConfigsKey{_bridgeOtherConfigKey=hwaddr}=BridgeOtherConfigs

{getBridgeOtherConfigKey=hwaddr, getBridgeOtherConfigValue=ec:47:56:1c:b1:9b, augmentation=[]}

, BridgeOtherConfigsKey{_bridgeOtherConfigKey=disable-in-band}=BridgeOtherConfigs{getBridgeOtherConfigKey=disable-in-band, getBridgeOtherConfigValue=true, augmentation=[]}}, getBridgeUuid=Uuid{_value=935221ad-40ad-4aaa-939c-a8654e883bd8}, getDatapathId=DatapathId{_value=00:00:ec:47:56:1c:b1:9b}, getDatapathType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.DatapathTypeSystem, getFailMode=interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.OvsdbFailModeSecure, getManagedBy=OvsdbNodeRef{_value=KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.topology.Node, path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey{_topologyId=Uri{_value=ovsdb:1}}], org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.topology.Node[key=NodeKey{_nodeId=Uri{_value=ovsdb://uuid/758da02d-7c35-43b6-99aa-c9c57108210f}}]]}}, getProtocolEntry={ProtocolEntryKey{_protocol=interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.OvsdbBridgeProtocolOpenflow13}=ProtocolEntry{getProtocol=interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.OvsdbBridgeProtocolOpenflow13, augmentation=[]}}, isStpEnable=false}, dpn: 259791131554203

Openflowplugin and ovs communication time:
Karaf.log:

2020-06-04T02:29:56,797 | INFO | epollEventLoopGroup-7-3 | ContextChainHolderImpl | 382 - org.opendaylight.openflowplugin.impl - 0.11.0.SNAPSHOT | Device openflow:259791131554203 connected.

Ovs-vswitchd.log:
2020-06-04T02:29:56.768Z|01001|rconn|INFO|br-int<->tcp:10.30.170.113:6653: connected

Generated at Wed Feb 07 20:24:40 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.