Re: TSC agenda: quick update on tpce issues
Hi all and thanks a lot for proposing help
The first 2 issues are easy to understand and quite simple to reproduce.
Since oxygen, we do not see anymore the “controller-config” node automatically connected at netconf connector start-up.
Has this feature abandoned ? We had a basic tests its connection, currently commented out. Can we remove it ?
The second one is the impossibility since Oxygen to use the netconf CLI until a netconf node has been connected with the REST API.
I wonder if this issues is not somehow linked to the previous one…
The third issue is more tricky, but hopefully fixed now even if it is not clear why.
Here is how to reproduce it.
We are using python –nose + tox to run our functests. All is in the tests folder. You can look at our tox.ini file for details.
In change 74468, we used to mock our openroadm devices with a patched version of netconf-testtool 1.3.1
(the patch merges config and operational datastore and is solely for read-only tests)
This mock is notably used by the portmapping functests (cd tests && tox –e portmapping)
Tox runs the script build.sh or buildTesttool.sh to download, compile, patch and configure testtool in our tests folder.
With the bump to Fluorine, the old testtool configuration does not work anymore with the controller.
We’ve commented the issue in change 74296 PS 5
Martial’s first feeling was a capability / get-schema problem.
But when I looked at the log and snooped the netconf session, it appeared the problem is deeper.
We had a java exception and EXI malformed message errors.
My feeling is that the netconf southbound connector requires now more features support from netconf devices that it used to in Nitrogen or Oxygen.
We upgraded testtool to the 1.5.0-SNAPSHOT in change 74508 https://git.opendaylight.org/gerrit/74508 and this fixed the issue.
But we haven’t fully understood why we got those errors with testtool 1.3.1
The last issue is not yet fixed.
We are now in the process of switching to honeycomb because testtool have a limited support of operational datastore and write operations.
This has already been done successfully in Nitrogen with changes 74182 and 6801
However, cherry-picks in Oxygen and master reports some unexpected functests failures.
We have also observed sometimes unstabilities in the old testtool tox tests suite when bumping to oxygen.
Karaf 4 boot process related issues ?
I am still trying to characterize that more clearly.
Any idea or help is welcome.
From: Tom Pantelis [mailto:tompantelis@...]
On Tue, Jul 31, 2018 at 12:09 PM, Ariel Adam <aadam@...> wrote:
Guilaume, that is great news :-).
Adding the Netconf team (Jakub, Jakub and Tom who I see are listed).
Guys, how can we help Guilaume and his team to git this through (1 week go to go)?
I'm trying to follow everything here.... Guilaume, so what is the remaining issue(s) re: netconf southbound connector dependencies? Can you provide steps on how to reproduce it?
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.