[release] Autorelease oxygen failed to build vbd-api from honeycomb
Hi,
Seems some models were missing imports for ietf-interfaces. I prepared a patch [0]. It should fix the problem, but still I need to wait for the verify job to finish. When it is done it can be merged.
[0] https://git.opendaylight.org/gerrit/#/c/74754/
Michal
Sent: Thursday, August 2, 2018 7:16 AM
To: Michal Čmarada <michal.cmarada@...>
Cc: honeycomb-dev@...; Release <release@...>
Subject: Re: [release] Autorelease oxygen failed to build vbd-api from honeycomb
Hi Michal.
Any idea what this failure is about?
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:2.0.6.1:generate-sources (binding) on project vbd-api: Failed to process reactor ProcessorModuleReactor{sources=[RevisionSourceIdentifier [name=adjacencies-identification-context@2016-08-01], RevisionSourceIdentifier [name=dhcp@2017-03-15], RevisionSourceIdentifier [name=dot1q-types@2015-06-26], RevisionSourceIdentifier [name=eid-mapping-context@2016-08-01], RevisionSourceIdentifier [name=gpe@2017-08-01], RevisionSourceIdentifier [name=hc2vpp-ietf-ipv4-unicast-routing@2017-09-17], RevisionSourceIdentifier [name=hc2vpp-ietf-ipv6-unicast-routing@2017-09-17], RevisionSourceIdentifier [name=hc2vpp-ietf-routing@2014-05-24], RevisionSourceIdentifier [name=ietf-access-control-list@2016-07-08], RevisionSourceIdentifier [name=ietf-ip@2014-06-16], RevisionSourceIdentifier [name=ietf-nat@2015-09-08], RevisionSourceIdentifier [name=ietf-packet-fields@2016-07-08], RevisionSourceIdentifier [name=interface-acl@2016-12-14], RevisionSourceIdentifier [name=interface-nat@2017-08-16], RevisionSourceIdentifier [name=interface-policer@2017-03-15], RevisionSourceIdentifier [name=interface-role@2017-06-15], RevisionSourceIdentifier [name=lisp@2017-10-13], RevisionSourceIdentifier [name=naming-context@2016-05-13], RevisionSourceIdentifier [name=nat-context@2016-12-14], RevisionSourceIdentifier [name=nd-proxy@2017-03-15], RevisionSourceIdentifier [name=odl-external-reference@2016-01-29], RevisionSourceIdentifier [name=pbb-types@2016-12-14], RevisionSourceIdentifier [name=policer@2017-03-15], RevisionSourceIdentifier [name=proxy-arp@2017-03-15], RevisionSourceIdentifier [name=subinterface-nat@2017-06-15], RevisionSourceIdentifier [name=subinterface-span@2017-06-07], RevisionSourceIdentifier [name=unnumbered-interfaces@2017-05-10], RevisionSourceIdentifier [name=v3po-context@2016-09-09], RevisionSourceIdentifier [name=v3po@2017-06-07], RevisionSourceIdentifier [name=vbridge-status@2017-03-27], RevisionSourceIdentifier [name=vbridge-topology@2016-01-29], RevisionSourceIdentifier [name=vlan-tunnel@2017-03-27], RevisionSourceIdentifier [name=vpp-acl@2017-06-15], RevisionSourceIdentifier [name=vpp-classifier-acl@2017-05-03], RevisionSourceIdentifier [name=vpp-classifier-context@2017-05-02], RevisionSourceIdentifier [name=vpp-classifier@2017-03-27], RevisionSourceIdentifier [name=vpp-interface-acl@2017-03-15], RevisionSourceIdentifier [name=vpp-nat@2017-08-04], RevisionSourceIdentifier [name=vpp-pbb@2016-12-14], RevisionSourceIdentifier [name=vpp-routing-ra@2017-05-02], RevisionSourceIdentifier [name=vpp-routing-table-lookup@2017-09-17], RevisionSourceIdentifier [name=vpp-routing@2017-09-17], RevisionSourceIdentifier [name=vpp-subinterface-acl@2017-03-15], RevisionSourceIdentifier [name=vpp-vlan@2018-03-19], RevisionSourceIdentifier [name=vxlan-tunnel@2017-03-27]], parser=org.opendaylight.yangtools.yang.parser.impl.YangParserImpl@37be307c}: Failed to assemble sources: Some of FULL_DECLARATION modifiers for statements were not resolved. Failed to parse node 'if:interfaces' in path '/if:interfaces/if:interface/vpp-vlan:sub-interfaces/vpp-vlan:sub-interface' [at /w/workspace/autorelease-release-oxygen/honeycomb/vbd/api/src/main/yang/subinterface-span@...:30:2]: Cannot resolve QNameModule for 'if:interfaces' [at /w/workspace/autorelease-release-oxygen/honeycomb/vbd/api/src/main/yang/subinterface-span@...:30:2] -> [Help 1]
Thanks.
On Thu, Aug 2, 2018 at 5:19 AM Jenkins <jenkins-dontreply@...> wrote:
Attention honeycomb-devs,
Autorelease oxygen failed to build vbd-api from honeycomb in build
374. Attached is a snippet of the error message related to the
failure that we were able to automatically parse as well as console logs.
Console Logs:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-oxygen/374
Jenkins Build:
https://jenkins.opendaylight.org/releng/job/autorelease-release-oxygen/374/
Please review and provide an ETA on when a fix will be available.
Thanks,
ODL releng/autorelease team
_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release
Hi,
Verify job passed and I put +2 on the patch, but I think we need approval to submit the patch since I cannot see the submit button.
Michal
Sent: Thursday, August 2, 2018 9:38 AM
To: 'Ariel Adam' <aadam@...>
Cc: honeycomb-dev@...; Release <release@...>; vbd-dev@...
Subject: RE: [release] Autorelease oxygen failed to build vbd-api from honeycomb
Hi,
Seems some models were missing imports for ietf-interfaces. I prepared a patch [0]. It should fix the problem, but still I need to wait for the verify job to finish. When it is done it can be merged.
[0] https://git.opendaylight.org/gerrit/#/c/74754/
Michal
From: Ariel Adam <aadam@...>
Sent: Thursday, August 2, 2018 7:16 AM
To: Michal Čmarada <michal.cmarada@...>
Cc: honeycomb-dev@...; Release <release@...>
Subject: Re: [release] Autorelease oxygen failed to build vbd-api from honeycomb
Hi Michal.
Any idea what this failure is about?
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:2.0.6.1:generate-sources (binding) on project vbd-api: Failed to process reactor ProcessorModuleReactor{sources=[RevisionSourceIdentifier [name=adjacencies-identification-context@2016-08-01], RevisionSourceIdentifier [name=dhcp@2017-03-15], RevisionSourceIdentifier [name=dot1q-types@2015-06-26], RevisionSourceIdentifier [name=eid-mapping-context@2016-08-01], RevisionSourceIdentifier [name=gpe@2017-08-01], RevisionSourceIdentifier [name=hc2vpp-ietf-ipv4-unicast-routing@2017-09-17], RevisionSourceIdentifier [name=hc2vpp-ietf-ipv6-unicast-routing@2017-09-17], RevisionSourceIdentifier [name=hc2vpp-ietf-routing@2014-05-24], RevisionSourceIdentifier [name=ietf-access-control-list@2016-07-08], RevisionSourceIdentifier [name=ietf-ip@2014-06-16], RevisionSourceIdentifier [name=ietf-nat@2015-09-08], RevisionSourceIdentifier [name=ietf-packet-fields@2016-07-08], RevisionSourceIdentifier [name=interface-acl@2016-12-14], RevisionSourceIdentifier [name=interface-nat@2017-08-16], RevisionSourceIdentifier [name=interface-policer@2017-03-15], RevisionSourceIdentifier [name=interface-role@2017-06-15], RevisionSourceIdentifier [name=lisp@2017-10-13], RevisionSourceIdentifier [name=naming-context@2016-05-13], RevisionSourceIdentifier [name=nat-context@2016-12-14], RevisionSourceIdentifier [name=nd-proxy@2017-03-15], RevisionSourceIdentifier [name=odl-external-reference@2016-01-29], RevisionSourceIdentifier [name=pbb-types@2016-12-14], RevisionSourceIdentifier [name=policer@2017-03-15], RevisionSourceIdentifier [name=proxy-arp@2017-03-15], RevisionSourceIdentifier [name=subinterface-nat@2017-06-15], RevisionSourceIdentifier [name=subinterface-span@2017-06-07], RevisionSourceIdentifier [name=unnumbered-interfaces@2017-05-10], RevisionSourceIdentifier [name=v3po-context@2016-09-09], RevisionSourceIdentifier [name=v3po@2017-06-07], RevisionSourceIdentifier [name=vbridge-status@2017-03-27], RevisionSourceIdentifier [name=vbridge-topology@2016-01-29], RevisionSourceIdentifier [name=vlan-tunnel@2017-03-27], RevisionSourceIdentifier [name=vpp-acl@2017-06-15], RevisionSourceIdentifier [name=vpp-classifier-acl@2017-05-03], RevisionSourceIdentifier [name=vpp-classifier-context@2017-05-02], RevisionSourceIdentifier [name=vpp-classifier@2017-03-27], RevisionSourceIdentifier [name=vpp-interface-acl@2017-03-15], RevisionSourceIdentifier [name=vpp-nat@2017-08-04], RevisionSourceIdentifier [name=vpp-pbb@2016-12-14], RevisionSourceIdentifier [name=vpp-routing-ra@2017-05-02], RevisionSourceIdentifier [name=vpp-routing-table-lookup@2017-09-17], RevisionSourceIdentifier [name=vpp-routing@2017-09-17], RevisionSourceIdentifier [name=vpp-subinterface-acl@2017-03-15], RevisionSourceIdentifier [name=vpp-vlan@2018-03-19], RevisionSourceIdentifier [name=vxlan-tunnel@2017-03-27]], parser=org.opendaylight.yangtools.yang.parser.impl.YangParserImpl@37be307c}: Failed to assemble sources: Some of FULL_DECLARATION modifiers for statements were not resolved. Failed to parse node 'if:interfaces' in path '/if:interfaces/if:interface/vpp-vlan:sub-interfaces/vpp-vlan:sub-interface' [at /w/workspace/autorelease-release-oxygen/honeycomb/vbd/api/src/main/yang/subinterface-span@...:30:2]: Cannot resolve QNameModule for 'if:interfaces' [at /w/workspace/autorelease-release-oxygen/honeycomb/vbd/api/src/main/yang/subinterface-span@...:30:2] -> [Help 1]
Thanks.
On Thu, Aug 2, 2018 at 5:19 AM Jenkins <jenkins-dontreply@...> wrote:
Attention honeycomb-devs,
Autorelease oxygen failed to build vbd-api from honeycomb in build
374. Attached is a snippet of the error message related to the
failure that we were able to automatically parse as well as console logs.
Console Logs:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-oxygen/374
Jenkins Build:
https://jenkins.opendaylight.org/releng/job/autorelease-release-oxygen/374/
Please review and provide an ETA on when a fix will be available.
Thanks,
ODL releng/autorelease team
_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release
_______________________________________________Hi,
Verify job passed and I put +2 on the patch, but I think we need approval to submit the patch since I cannot see the submit button.
Michal
From: Michal Čmarada
Sent: Thursday, August 2, 2018 9:38 AM
To: 'Ariel Adam' <aadam@...>
Cc: honeycomb-dev@...; Release <release@...>; vbd-dev@...
Subject: RE: [release] Autorelease oxygen failed to build vbd-api from honeycomb
Hi,
Seems some models were missing imports for ietf-interfaces. I prepared a patch [0]. It should fix the problem, but still I need to wait for the verify job to finish. When it is done it can be merged.
[0] https://git.opendaylight.org/gerrit/#/c/74754/
Michal
From: Ariel Adam <aadam@...>
Sent: Thursday, August 2, 2018 7:16 AM
To: Michal Čmarada <michal.cmarada@...>
Cc: honeycomb-dev@...; Release <release@...>
Subject: Re: [release] Autorelease oxygen failed to build vbd-api from honeycomb
Hi Michal.
Any idea what this failure is about?
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:2.0.6.1:generate-sources (binding) on project vbd-api: Failed to process reactor ProcessorModuleReactor{sources=[RevisionSourceIdentifier [name=adjacencies-identification-context@2016-08-01], RevisionSourceIdentifier [name=dhcp@2017-03-15], RevisionSourceIdentifier [name=dot1q-types@2015-06-26], RevisionSourceIdentifier [name=eid-mapping-context@2016-08-01], RevisionSourceIdentifier [name=gpe@2017-08-01], RevisionSourceIdentifier [name=hc2vpp-ietf-ipv4-unicast-routing@2017-09-17], RevisionSourceIdentifier [name=hc2vpp-ietf-ipv6-unicast-routing@2017-09-17], RevisionSourceIdentifier [name=hc2vpp-ietf-routing@2014-05-24], RevisionSourceIdentifier [name=ietf-access-control-list@2016-07-08], RevisionSourceIdentifier [name=ietf-ip@2014-06-16], RevisionSourceIdentifier [name=ietf-nat@2015-09-08], RevisionSourceIdentifier [name=ietf-packet-fields@2016-07-08], RevisionSourceIdentifier [name=interface-acl@2016-12-14], RevisionSourceIdentifier [name=interface-nat@2017-08-16], RevisionSourceIdentifier [name=interface-policer@2017-03-15], RevisionSourceIdentifier [name=interface-role@2017-06-15], RevisionSourceIdentifier [name=lisp@2017-10-13], RevisionSourceIdentifier [name=naming-context@2016-05-13], RevisionSourceIdentifier [name=nat-context@2016-12-14], RevisionSourceIdentifier [name=nd-proxy@2017-03-15], RevisionSourceIdentifier [name=odl-external-reference@2016-01-29], RevisionSourceIdentifier [name=pbb-types@2016-12-14], RevisionSourceIdentifier [name=policer@2017-03-15], RevisionSourceIdentifier [name=proxy-arp@2017-03-15], RevisionSourceIdentifier [name=subinterface-nat@2017-06-15], RevisionSourceIdentifier [name=subinterface-span@2017-06-07], RevisionSourceIdentifier [name=unnumbered-interfaces@2017-05-10], RevisionSourceIdentifier [name=v3po-context@2016-09-09], RevisionSourceIdentifier [name=v3po@2017-06-07], RevisionSourceIdentifier [name=vbridge-status@2017-03-27], RevisionSourceIdentifier [name=vbridge-topology@2016-01-29], RevisionSourceIdentifier [name=vlan-tunnel@2017-03-27], RevisionSourceIdentifier [name=vpp-acl@2017-06-15], RevisionSourceIdentifier [name=vpp-classifier-acl@2017-05-03], RevisionSourceIdentifier [name=vpp-classifier-context@2017-05-02], RevisionSourceIdentifier [name=vpp-classifier@2017-03-27], RevisionSourceIdentifier [name=vpp-interface-acl@2017-03-15], RevisionSourceIdentifier [name=vpp-nat@2017-08-04], RevisionSourceIdentifier [name=vpp-pbb@2016-12-14], RevisionSourceIdentifier [name=vpp-routing-ra@2017-05-02], RevisionSourceIdentifier [name=vpp-routing-table-lookup@2017-09-17], RevisionSourceIdentifier [name=vpp-routing@2017-09-17], RevisionSourceIdentifier [name=vpp-subinterface-acl@2017-03-15], RevisionSourceIdentifier [name=vpp-vlan@2018-03-19], RevisionSourceIdentifier [name=vxlan-tunnel@2017-03-27]], parser=org.opendaylight.yangtools.yang.parser.impl.YangParserImpl@37be307c}: Failed to assemble sources: Some of FULL_DECLARATION modifiers for statements were not resolved. Failed to parse node 'if:interfaces' in path '/if:interfaces/if:interface/vpp-vlan:sub-interfaces/vpp-vlan:sub-interface' [at /w/workspace/autorelease-release-oxygen/honeycomb/vbd/api/src/main/yang/subinterface-span@...:30:2]: Cannot resolve QNameModule for 'if:interfaces' [at /w/workspace/autorelease-release-oxygen/honeycomb/vbd/api/src/main/yang/subinterface-span@...:30:2] -> [Help 1]
Thanks.
On Thu, Aug 2, 2018 at 5:19 AM Jenkins <jenkins-dontreply@...> wrote:
Attention honeycomb-devs,
Autorelease oxygen failed to build vbd-api from honeycomb in build
374. Attached is a snippet of the error message related to the
failure that we were able to automatically parse as well as console logs.
Console Logs:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-oxygen/374
Jenkins Build:
https://jenkins.opendaylight.org/releng/job/autorelease-release-oxygen/374/
Please review and provide an ETA on when a fix will be available.
Thanks,
ODL releng/autorelease team
_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release
That's right. stable/oxygen is currently blocked. The releaseThis one, https://git.opendaylight.org/gerrit/#/c/74754/, is.
engineering team needs to be notified by the Release Manager if a patch
is approved to merge.
Regards,
Robert