You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bigtop.apache.org by Masatake Iwasaki <iw...@oss.nttdata.co.jp> on 2021/09/01 05:04:11 UTC
Re: V1.5.0 Logstash RPM Build failure
BIGTOP-3582 was committed to master and branch-3.0.
I cherry-picked BIGTOP-3499 and BIGTOP-3562 too to branch-1.5 based on the report of Nathan.
Thanks,
Masatake Iwasaki
On 2021/08/30 21:41, nathan.english@bt.com wrote:
> That's Brilliant. Thanks for looking at it so quickly, Masatake!
> -----Original Message-----
> From: Masatake Iwasaki [mailto:iwasakims@oss.nttdata.co.jp]
> Sent: 30 August 2021 13:28
> To: user@bigtop.apache.org; English,N,Nathan,VIR R <na...@bt.com>
> Subject: Re: V1.5.0 Logstash RPM Build failure
>
> Thanks for filing the BIGTOP-3582, Nathan.
>
> I submitted the PR #815 as a quick fix.
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Fpull%2F815&data=04%7C01%7Cnathan.english%40bt.com%7C506ab18ad2914912e53c08d96ba0f7c4%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637659161365857903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yQkFBmmebSy6FVDlR8jpKZv%2BCZDesGq3dFe7X%2F23YCI%3D&reserved=0
>
> On 2021/08/30 16:40, nathan.english@bt.com wrote:
>> Hi Jun,
>>
>> BIGTOP-3582[1] has been created.
>>
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FBIGTOP-3582&data=04%7C01%7Cnathan.english%40bt.com%7C506ab18ad2914912e53c08d96ba0f7c4%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637659161365857903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zl9mghN9rvteu4yaN7EpvY1Ux18fii6Cp8TDQZw%2F2e8%3D&reserved=0 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FBIGTOP-3582&data=04%7C01%7Cnathan.english%40bt.com%7C506ab18ad2914912e53c08d96ba0f7c4%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637659161365857903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zl9mghN9rvteu4yaN7EpvY1Ux18fii6Cp8TDQZw%2F2e8%3D&reserved=0>
>>
>> Kind Regards,
>>
>> Nathan
>>
>> *From:*Jun HE [mailto:junhe@apache.org]
>> *Sent:* 30 August 2021 10:29
>> *To:* user@bigtop.apache.org
>> *Cc:* Masatake Iwasaki <iw...@oss.nttdata.co.jp>
>> *Subject:* Re: V1.5.0 Logstash RPM Build failure
>>
>>
>>
>> You don't often get email from junhe@apache.org <ma...@apache.org>. Learn why this is important <http://aka.ms/LearnAboutSenderIdentification>
>>
>>
>>
>> Hi Nathan,
>>
>> Thanks for letting us know it. Pls create a bug, so we will not lose track of this.
>>
>> Will check how to fix it.
>>
>> Regards,
>>
>> Jun
>>
>> <nathan.english@bt.com <ma...@bt.com>> 于2021年8月30日周一 下午3:02写道：
>>
>> I did think the same when I saw the error. It's not pinned as you say in the release gemfile [1].
>>
>> Unfortunately, I haven't had a chance to look at it any further as it's not something I need for my deployment. Should I create a bug on Jira?
>>
>> [1] https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Felastic%2Flogstash%2Fblob%2Fv5.4.1%2FGemfile&data=04%7C01%7Cnathan.english%40bt.com%7C506ab18ad2914912e53c08d96ba0f7c4%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637659161365857903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=O3CMAMFp9GD%2Bo9XUzNWLaWpqDAxdSYlYHFXrAl1bNiw%3D&reserved=0 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Felastic%2Flogstash%2Fblob%2Fv5.4.1%2FGemfile&data=04%7C01%7Cnathan.english%40bt.com%7C506ab18ad2914912e53c08d96ba0f7c4%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637659161365857903%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=O3CMAMFp9GD%2Bo9XUzNWLaWpqDAxdSYlYHFXrAl1bNiw%3D&reserved=0>
>>
>> -----Original Message-----
>> From: Masatake Iwasaki [mailto:iwasakims@oss.nttdata.co.jp <ma...@oss.nttdata.co.jp>]
>> Sent: 30 August 2021 05:09
>> To: user@bigtop.apache.org <ma...@bigtop.apache.org>; English,N,Nathan,VIR R <nathan.english@bt.com <ma...@bt.com>>
>> Subject: Re: V1.5.0 Logstash RPM Build failure
>>
>> [You don't often get email from iwasakims@oss.nttdata.co.jp <ma...@oss.nttdata.co.jp>. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification <http://aka.ms/LearnAboutSenderIdentification>.]
>>
>> > I'm having issues building the Logstash rpm. It looks to be failing on the command 'rake artifact-tar'. With a missing file 'vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-11.0.4-java/lib/logstash/outputs/templates/ecs-v1/elasticsearch-8x.json'. It looks to be a broken symlink to 'lib/logstash/outputs/elasticsearch/templates/ecs-v1/User/yaauie/src/elastic/logstash/plugins/logsta' Which that directory structure beyond lib doesn't even exist.
>>
>> This can be reproduced even in master branch on CentOS 8.
>> It looks like the versions of logstash plugins are not pinned and the latest logstash-output-elasticsearch-11.0.4-java have issue (against logstash-5.4.1??).::
>>
>> [artifact:tar] building build/logstash-5.4.1.tar.gz
>> rake aborted!
>> Errno::ENOENT: No such file or directory - vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-11.0.4-java/lib/logstash/outputs/elasticsearch/templates/ecs-v1/elasticsearch-8x.json
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:239:in `block in write_to_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/vendor/bundle/jruby/2.3.0/gems/minitar-0.5.4/lib/archive/tar/minitar.rb:344:in `add_file_simple'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:238:in `write_to_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:215:in `block in build_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:214:in `build_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:82:in `block in (root)'
>> Tasks: TOP => artifact:tar
>> (See full trace by running task with --trace)
>> error: Bad exit status from /var/tmp/rpm-tmp.cn5QyU (%build)
>>
>>
>> On 2021/08/29 20:38, nathan.english@bt.com <ma...@bt.com> wrote:
>> > Hi All,
>> >
>> > I'm having issues building the Logstash rpm. It looks to be failing on the command 'rake artifact-tar'. With a missing file 'vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-11.0.4-java/lib/logstash/outputs/templates/ecs-v1/elasticsearch-8x.json'. It looks to be a broken symlink to 'lib/logstash/outputs/elasticsearch/templates/ecs-v1/User/yaauie/src/elastic/logstash/plugins/logsta' Which that directory structure beyond lib doesn't even exist.
>> >
>> > I did apply the changes from BIGTOP-3562 to get this stage, as previously, it would fail as the website no longer existed, along with BIGTOP-3499 for the gem issue.
>> >
>> > I haven't tried building this with the master branch.
>> >
>> > I was wondering if there was anything else I am missing or should try?
>> >
>> > Kind Regards,
>> >
>> > Nathan
>> >
>>
RE: V1.5.0 Logstash RPM Build failure
Posted by na...@bt.com.
Hi Masatake,
I tried the rpm build yesterday evening with your changes cherry-picked on top, and it all seemed to work on Centos 7.
Many thanks!
Nathan
-----Original Message-----
From: Masatake Iwasaki [mailto:iwasakims@oss.nttdata.co.jp]
Sent: 01 September 2021 08:04
To: user@bigtop.apache.org; English,N,Nathan,VIR R <na...@bt.com>
Subject: Re: V1.5.0 Logstash RPM Build failure
BIGTOP-3582 was committed to master and branch-3.0.
I cherry-picked BIGTOP-3499 and BIGTOP-3562 too to branch-1.5 based on the report of Nathan.
Thanks,
Masatake Iwasaki
On 2021/08/30 21:41, nathan.english@bt.com wrote:
> That's Brilliant. Thanks for looking at it so quickly, Masatake!
> -----Original Message-----
> From: Masatake Iwasaki [mailto:iwasakims@oss.nttdata.co.jp]
> Sent: 30 August 2021 13:28
> To: user@bigtop.apache.org; English,N,Nathan,VIR R <na...@bt.com>
> Subject: Re: V1.5.0 Logstash RPM Build failure
>
> Thanks for filing the BIGTOP-3582, Nathan.
>
> I submitted the PR #815 as a quick fix.
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Fpull%2F815&data=04%7C01%7Cnathan.english%40bt.com%7Ce4f8f34be9734dec402f08d96d05facc%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637660695434161670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TKdekuoTm5xAMf3sCze3q01ph6IoMf2c4fwlA5Gk2OI%3D&reserved=0
>
> On 2021/08/30 16:40, nathan.english@bt.com wrote:
>> Hi Jun,
>>
>> BIGTOP-3582[1] has been created.
>>
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FBIGTOP-3582&data=04%7C01%7Cnathan.english%40bt.com%7Ce4f8f34be9734dec402f08d96d05facc%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637660695434161670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DLJw%2F80sOJXODqcCAw1EeM18Z0f4yGcb5Vqq4TGR%2FZA%3D&reserved=0 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FBIGTOP-3582&data=04%7C01%7Cnathan.english%40bt.com%7Ce4f8f34be9734dec402f08d96d05facc%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637660695434161670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DLJw%2F80sOJXODqcCAw1EeM18Z0f4yGcb5Vqq4TGR%2FZA%3D&reserved=0>
>>
>> Kind Regards,
>>
>> Nathan
>>
>> *From:*Jun HE [mailto:junhe@apache.org]
>> *Sent:* 30 August 2021 10:29
>> *To:* user@bigtop.apache.org
>> *Cc:* Masatake Iwasaki <iw...@oss.nttdata.co.jp>
>> *Subject:* Re: V1.5.0 Logstash RPM Build failure
>>
>>
>>
>> You don't often get email from junhe@apache.org <ma...@apache.org>. Learn why this is important <http://aka.ms/LearnAboutSenderIdentification>
>>
>>
>>
>> Hi Nathan,
>>
>> Thanks for letting us know it. Pls create a bug, so we will not lose track of this.
>>
>> Will check how to fix it.
>>
>> Regards,
>>
>> Jun
>>
>> <nathan.english@bt.com <ma...@bt.com>> 于2021年8月30日周一 下午3:02写道：
>>
>> I did think the same when I saw the error. It's not pinned as you say in the release gemfile [1].
>>
>> Unfortunately, I haven't had a chance to look at it any further as it's not something I need for my deployment. Should I create a bug on Jira?
>>
>> [1] https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Felastic%2Flogstash%2Fblob%2Fv5.4.1%2FGemfile&data=04%7C01%7Cnathan.english%40bt.com%7Ce4f8f34be9734dec402f08d96d05facc%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637660695434161670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=BoZ5HmQsMvta6Myj0AP%2BQieZ40Sqg0NHL62g%2BEzeVsY%3D&reserved=0 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Felastic%2Flogstash%2Fblob%2Fv5.4.1%2FGemfile&data=04%7C01%7Cnathan.english%40bt.com%7Ce4f8f34be9734dec402f08d96d05facc%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637660695434161670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=BoZ5HmQsMvta6Myj0AP%2BQieZ40Sqg0NHL62g%2BEzeVsY%3D&reserved=0>
>>
>> -----Original Message-----
>> From: Masatake Iwasaki [mailto:iwasakims@oss.nttdata.co.jp <ma...@oss.nttdata.co.jp>]
>> Sent: 30 August 2021 05:09
>> To: user@bigtop.apache.org <ma...@bigtop.apache.org>; English,N,Nathan,VIR R <nathan.english@bt.com <ma...@bt.com>>
>> Subject: Re: V1.5.0 Logstash RPM Build failure
>>
>> [You don't often get email from iwasakims@oss.nttdata.co.jp <ma...@oss.nttdata.co.jp>. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification <http://aka.ms/LearnAboutSenderIdentification>.]
>>
>> > I'm having issues building the Logstash rpm. It looks to be failing on the command 'rake artifact-tar'. With a missing file 'vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-11.0.4-java/lib/logstash/outputs/templates/ecs-v1/elasticsearch-8x.json'. It looks to be a broken symlink to 'lib/logstash/outputs/elasticsearch/templates/ecs-v1/User/yaauie/src/elastic/logstash/plugins/logsta' Which that directory structure beyond lib doesn't even exist.
>>
>> This can be reproduced even in master branch on CentOS 8.
>> It looks like the versions of logstash plugins are not pinned and the latest logstash-output-elasticsearch-11.0.4-java have issue (against logstash-5.4.1??).::
>>
>> [artifact:tar] building build/logstash-5.4.1.tar.gz
>> rake aborted!
>> Errno::ENOENT: No such file or directory - vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-11.0.4-java/lib/logstash/outputs/elasticsearch/templates/ecs-v1/elasticsearch-8x.json
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:239:in `block in write_to_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/vendor/bundle/jruby/2.3.0/gems/minitar-0.5.4/lib/archive/tar/minitar.rb:344:in `add_file_simple'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:238:in `write_to_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:215:in `block in build_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:214:in `build_tar'
>> /home/centos/srcs/bigtop/build/logstash/rpm/BUILD/logstash-5.4.1/rakelib/artifacts.rake:82:in `block in (root)'
>> Tasks: TOP => artifact:tar
>> (See full trace by running task with --trace)
>> error: Bad exit status from /var/tmp/rpm-tmp.cn5QyU (%build)
>>
>>
>> On 2021/08/29 20:38, nathan.english@bt.com <ma...@bt.com> wrote:
>> > Hi All,
>> >
>> > I'm having issues building the Logstash rpm. It looks to be failing on the command 'rake artifact-tar'. With a missing file 'vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-11.0.4-java/lib/logstash/outputs/templates/ecs-v1/elasticsearch-8x.json'. It looks to be a broken symlink to 'lib/logstash/outputs/elasticsearch/templates/ecs-v1/User/yaauie/src/elastic/logstash/plugins/logsta' Which that directory structure beyond lib doesn't even exist.
>> >
>> > I did apply the changes from BIGTOP-3562 to get this stage, as previously, it would fail as the website no longer existed, along with BIGTOP-3499 for the gem issue.
>> >
>> > I haven't tried building this with the master branch.
>> >
>> > I was wondering if there was anything else I am missing or should try?
>> >
>> > Kind Regards,
>> >
>> > Nathan
>> >
>>