The 'stable' branch has disappeared on of the upstream tox deps: https://github.com/psf/black/branches.

There are tox failure with the upstream dependencies, and nothing todo with the Infra. I'll need to dig deeps and get back. 05:07:38 expected return code: 005:07:38 stdout: (none)05:07:38

Also per TSC discussion, the Silicon distribution release version will be: 14.0.0, we will use minor version (2nd digit) for Service Releases and the patch version (3rd digit) for any last minute

Anil, Can you please check what is going wrong with this job: https://jenkins.opendaylight.org/releng/job/builder-tox-verify-master/ I am unable to verify the change for adding the missing jobs to

Sorry I meant 0.14.1

OK guys, I just realized we just released the wrong branch for the common distribution (master vs stable/silicon). Basically because distribution jobs were not updated when we branched off

OK here is the Silicon release: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.14.0/ We can proceed with the rest of the stuff

Hello Correct, I just released TransportPCE artifacts version 3.0.0 for Silicon. Release job logs are available at this

Greetings all: OpenDaylight Silicon is released which makes Magnesium support EOL official. The below CR removes all the Magnesium jobs from ODL releng/builder repo and

Thanks Anil. I believe that @LAMBERT Guillaume TGI/OLN is already working on the Transport PCE Silicon release. Also I believe that the release notes are being done automatically but

Hello All, OpenDaylight Silicon version bump is complete and the staging repository has been promoted. The 'stable/silicon' branch is unlocked and ready for development. Pending activities required to

I've built new images with OVS 2.8 on Ubuntu18.04. "ZZCI - Ubuntu 18.04 - mininet-ovs-28 - x86_64 - 20210329-150700.140" (label: ubuntu1804-mininet-ovs-28-1c-4g) Please review the change, needs to be

Well, I do not think ODL OpenStack projects are active anymore, so a single version OVS VM should be sufficient. Anyway, what are the labels for the new images? BR/Luis

If I remember correctly as discussed in the integration team meetings, OVS version was dependent on the OpenStack dev version (Rocky, Queens) as tested with the CSIT jobs. It's up to the $project to

These CR's should fix the build failures on Ubuntu 18.04, and installing broken dependencies with ovs 2.6.

+1, if UB18 packages bring a newer OVS version, we can very well use that. I remember the main reason for overwriting the OVS version was to get newer version of OVS.

Well, at the end of the day, there is another question: why are we even building these from sources? Regards, Robert

This is building ovs-2.8.1, while it should really be upgraded to 2.8.11. These are very simple build errors and should take just a few minutes to resolve to anyone familiar with building

Similar build issues with mininet-ovs-26: https://jenkins.opendaylight.org/releng/view/packer/job/builder-packer-merge-ubuntu-18.04-mininet-ovs-2.6/38/console 03:22:12 openstack: /bin/bash

Hello Luis: That was cut and paste typo, the correct label should have been. "ZZCI - Ubuntu 18.04 - mininet-ovs-25 - x86_64 - 20200813-035525.790" (Label: ubuntu1804-mininet-ovs-25-1c-4g) We only