Details
-
Bug
-
Status: Verified
-
Highest
-
Resolution: Done
-
Sulfur, Chlorine, Argon
-
None
Description
Sulfur-SR3 and Clorine-SR1 are respectively using karaf-4.3.8 and karaf-4.4.2
In these versions of karaf, when we try to launch the client (./karaf/target/assembly/bin/client), it fails with the following message:
Logging in as karaf
DefaultOpenFuture[ChannelShell[id=0, recipient=-1]-ClientSessionImpl[karaf@localhost/127.0.0.1:8101]]: Failed (IllegalArgumentException) to execute: Invalid UINT32 value: -1
This feature is used in transportpce tapi functional tests to install the odl-transportpce-tapi optional feature.
Since the tapi feature can no longer be installed, all tapi functional tests are failing on the gate (https://jenkins.opendaylight.org/releng/job/transportpce-tox-verify-sulfur/1372/consoleFull)
Karaf client is still failing with karaf-4.4.2, even if the exception is better managed:
Logging in as karaf
Required control character VDSUSP is not available
Attachments
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 103302,2 | Downgrade sshd | master | odlparent | Status: ABANDONED | 0 | -1 |
| 103326,4 | Use lighty build for all functional tests | stable/sulfur | transportpce | Status: MERGED | +2 | +1 |
| 104138,3 | Workaround to install tapi feature in func tests | master | transportpce | Status: MERGED | +2 | +1 |
| 104178,3 | Use karaf client batch mode | master | transportpce | Status: MERGED | +2 | +1 |
| 104185,1 | Restore TAPI feat install w/ Karaf client in tests | master | transportpce | Status: MERGED | +2 | +1 |