Nexus crashed this morning and caused autorelease boron to fail it's build.
Since I had to restart the autorelease-release-boron job anyway I merged
this patch before kicking off the new build. It should be included in:
https://jenkins.opendaylight.org/releng/job/autorelease-release-boron/244/
Re
Hi Everyone,
I think we have a blocker issue as I've just noticed this patch was merged:
https://git.opendaylight.org/gerrit/46730
and will actually prevent us from releasing Carbon in the future since the
version of sfc-ui-module that's currently set is already been released.
The problem with
Hi Brady,
We see this all the time with all of the projects that use bower. My
understanding is this is intermittent and happens when npm or bower's
repositories are not responding. It always works again after a retry in my
experience.
In the future once we have access to Nexus 3 we plan on setti
Adding sfc-dev.
Thanh
On Thu, Mar 2, 2017 at 10:12 PM, Jenkins wrote:
> Attention OpenDaylight-devs,
>
> Autorelease beryllium failed to build sfc-openflow-utils in build
> 164. Attached is a snippet of the error message related to the
> failure that we were able to automatically parse as well
On Fri, Mar 3, 2017 at 5:30 AM, Brady Allen Johnson <
brady.allen.john...@ericsson.com> wrote:
> I just cherry-picked the change to stable/beryllium, and will merge when
> ready.
>
Thanks, would be good to not get random failures since Jenkins will now
automatically email the mailing list when a
Credit should go to Anil Belur as he did the majority of the
implementation. :)
Thanh
On Fri, Mar 3, 2017 at 3:16 PM, Luis Gomez wrote:
> This is awesome Thahn, now I see how useful is the automatic message you
> implemented.
>
> On Mar 3, 2017, at 7:51 AM, Thanh Ha wrote:
>
that need to be reviewed and OKAY'd if there is no
issue.
I've BCC'd all the projects that need to report in.
Thanks,
Thanh
On Wed, Mar 29, 2017 at 2:07 PM, Thanh Ha
wrote:
> Hi Everyone,
>
> Just an FYI regarding the delay in distribution-test job reporting.
>
> The
Hi sfc-devs,
According to the Carbon Tracking spreadsheet the SFC release review patch
should be:
https://git.opendaylight.org/gerrit/57284
However I'm not able to access it. Is the patch a DRAFT? if so can someone
publish it so that we can review it?
Thanks,
Thanh
_
Hi sfc-devs,
We're investigating a CLM violation on the node package tmp 0.0.16 [0]
which accordingto CLM SFC is pulling in. The problem with this specific
version of tmp is that it's GPL 2.0. Every version of tmp from 0.0.17 and
onwards is MIT license which is fine so we're looking to figure out
n the whole distro.
>
> I looked also into the CLM report but I could not pinpoint exactly how
> and where did it obtain this reference from. Do you know?
>
> BR
> Jaime.
>
> On vie, 2017-05-26 at 09:28 -0400, Thanh Ha wrote:
> > Hi sfc-devs,
> >
> > We're in
:(
SFC needs lispflowmapping.
At this point I feel like we are probably just pulling every project into
autorelease in order to get it building. According to dependencies.log
netvirt:controller,dlux,federation,genius,infrautils,mdsal,netconf,neutron,odlparent,openflowplugin,ovsdb,sfc,yangtools
Hi Everyone,
The projects in the TO line are all projects we have identified as of this
morning that have not migrated to odlparent 2.0.4 yet and we have submitted
patches here [0].
Currently autorelease is failing to build due to bier but we are worried
that additional projects also need to bump
Thanks for the quick turn around!
Regards,
Thanh
On Thu, Nov 2, 2017 at 7:13 AM, David Suarez Fuentes <
david.suarez.fuen...@ericsson.com> wrote:
> Hi again,
>
> Here it is the fix: https://git.opendaylight.org/gerrit/#/c/65041/
>
> Best regards,
> David.
>
> On jue, 2017-11-02 at 02:59 +,
Hi Jaime,
Sorry for taking so long to get back to you on this one. I spent sometime
tonight trying to troubleshoot this but haven't been able to get the host
-> docker connection working yet but perhaps some experts can help
troubleshoot with the information below.
The test scenario is as follows
On Mon, Jan 22, 2018 at 5:14 AM, Jaime Caamaño Ruiz
wrote:
> > - clean ip tables in Bsudo iptables -Fsudo iptables
> > -t nat -FIn my testing cleaning the iptables in this way breaks the
> > docker container's ability to route to the outside world so I would
> > not recommend clea
- CentOS 7 -
> docker - 20180109-0346
>
> I don't know what's the change between the two but maybe we should step
> this one.
>
> BR
> Jaime.
>
> -Original Message-
> From: Thanh Ha
> To: jcaam...@suse.de
> Cc: integration-...@lists.opendayligh
On Wed, Jan 24, 2018 at 12:16 PM, Jaime Caamaño Ruiz
wrote:
>
> Thanh, issue confirmed fixed!
>
> > I can confirm that at least in my test environment I had to set this
> > parameter.
>
> Confirmed on my side too.
>
> BR
> Jaime
Awesome, that's great to hear!
Cheers,
Thanh
Hi Folks,
This is now the only issue blocking us from releasing Oxygen-SR1 at this
point. What are the next steps here? do we need a respin?
Thanks,
Thanh
On Tue, Apr 24, 2018 at 2:37 PM, Jamo Luhrsen wrote:
> Thanks Jaime,
>
> I updated the jira with this question, but I'm wondering why this
On Sun, Apr 22, 2018 at 8:18 PM, Anil Belur
wrote:
> On Mon, Apr 23, 2018 at 9:26 AM, Anil Belur
> wrote:
>
>> Hi everyone,
>>
>> We have locked the branch (stable/carbon) for Carbon SR4 release and
>> started RC build #583.
>>
>> Please open blocking bugs for any issues that need to be resolved
On Wed, Apr 25, 2018 at 9:17 AM, Thanh Ha
wrote:
> On Sun, Apr 22, 2018 at 8:18 PM, Anil Belur
> wrote:
>
>> On Mon, Apr 23, 2018 at 9:26 AM, Anil Belur
>> wrote:
>>
>>> Hi everyone,
>>>
>>> We have locked the branch (stable/carbon
I agree here. It seems wrong to me to remove it from Sodium this late into
the release cycle unless we really want to delay the release some more. In
the initial email thread this list Stephen's patch
https://git.opendaylight.org/gerrit/c/netvirt/+/84369 will remove it from
netvirt but this would r
There's still Stephan's open patch
https://git.opendaylight.org/gerrit/c/netvirt/+/84369 so it hasn't been
removed from NetVirt yet. Would require a respin of Sodium if we _really_
want to remove it.
Regards,
Thanh
On Fri, 13 Sep 2019 at 01:27, JamO Luhrsen wrote:
> I think it's time to get SFC
On Thu Oct 20 15:11:23 2016, gmain...@hpe.com wrote:
> Hi All,
> I'm stepping down as an SFC project contributor/committer.
>
> I wish you all the best,
> Gal
As requested we've removed your committer permissions from your account.
Thanks for your contributions,
Thanh
_
23 matches
Mail list logo
