Skip to content

Conversation

@ChrsMark
Copy link
Member

What does this PR do?

This PR upgrades k8s version for the CI to a latest one (v1.23.0)

Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
@ChrsMark ChrsMark added the Team:Integrations Label for the Integrations team label Dec 22, 2021
@ChrsMark ChrsMark requested a review from mtojek December 22, 2021 10:39
@ChrsMark ChrsMark self-assigned this Dec 22, 2021
@elasticmachine
Copy link

Pinging @elastic/integrations (Team:Integrations)

Copy link
Contributor

@mtojek mtojek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please wait for the CI to finish.

@elasticmachine
Copy link

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-12-22T10:39:25.977+0000

  • Duration: 103 min 9 sec

  • Commit: 080624b

Test stats 🧪

Test Results
Failed 0
Passed 3681
Skipped 5
Total 3686

Steps errors 1

Expand to view the steps failures

Test integration: gcp
  • Took 8 min 13 sec . View more details here
  • Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@ChrsMark
Copy link
Member Author

@mtojek any ides about the CI failure? It seems to be an issue in GCP integration.

@mtojek
Copy link
Contributor

mtojek commented Dec 22, 2021

I checked internal logs for GCP in the special bucket:

�[35mgcppubsub-vpcflow_1   |�[0m {"level":"debug","ts":"2021-12-22T11:17:42.223Z","caller":"command/log.go:74","msg":"Sending log line.","address":"gcppubsub-emulator:8681","log":"/sample_logs/vpcflow.log","line_number":33}
�[35mgcppubsub-vpcflow_1   |�[0m {"level":"debug","ts":"2021-12-22T11:17:42.246Z","caller":"command/log.go:74","msg":"Sending log line.","address":"gcppubsub-emulator:8681","log":"/sample_logs/vpcflow.log","line_number":34}
�[35mgcppubsub-vpcflow_1   |�[0m {"level":"debug","ts":"2021-12-22T11:17:42.250Z","caller":"command/log.go:74","msg":"Sending log line.","address":"gcppubsub-emulator:8681","log":"/sample_logs/vpcflow.log","line_number":35}
�[35mgcppubsub-vpcflow_1   |�[0m {"level":"debug","ts":"2021-12-22T11:17:42.254Z","caller":"command/log.go:74","msg":"Sending log line.","address":"gcppubsub-emulator:8681","log":"/sample_logs/vpcflow.log","line_number":36}
�[33mgcppubsub-emulator_1  |�[0m [pubsub] Dec 22, 2021 11:17:41 AM io.gapi.emulators.netty.HttpVersionRoutingHandler channelRead
�[33mgcppubsub-emulator_1  |�[0m [pubsub] INFO: Detected HTTP/2 connection.
�[33mgcppubsub-emulator_1  |�[0m [pubsub] Dec 22, 2021 11:17:42 AM io.gapi.emulators.netty.HttpVersionRoutingHandler channelRead
�[33mgcppubsub-emulator_1  |�[0m [pubsub] INFO: Detected HTTP/2 connection.
�[33mgcppubsub-emulator_1  |�[0m [pubsub] Dec 22, 2021 11:17:42 AM io.netty.channel.DefaultChannelPipeline onUnhandledInboundException
�[33mgcppubsub-emulator_1  |�[0m [pubsub] WARNING: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
�[33mgcppubsub-emulator_1  |�[0m [pubsub] java.io.IOException: Connection reset by peer
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/sun.nio.ch.FileDispatcherImpl.read0(Native Method)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:356)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 	at java.base/java.lang.Thread.run(Thread.java:829)
�[33mgcppubsub-emulator_1  |�[0m [pubsub] 
�[35mgcppubsub-vpcflow_1   |�[0m {"level":"debug","ts":"2021-12-22T11:17:42.258Z","caller":"command/log.go:74","msg":"Sending log line.","address":"gcppubsub-emulator:8681","log":"/sample_logs/vpcflow.log","line_number":37}
�[35mgcppubsub-vpcflow_1   |�[0m {"level":"debug","ts":"2021-12-22T11:17:42.262Z","caller":"command/log.go:74","msg":"Sending log line.","address":"gcppubsub-emulator:8681","log":"/sample_logs/vpcflow.log","line_number":38}

It doesn't look like a related bug, so I would say we can safely merge this change. AFAIR kind is used by the Kubernetes integration only. Would you like me to merge this PR?

@ChrsMark
Copy link
Member Author

ChrsMark commented Dec 22, 2021

Thanks for checking, I will proceed with the merge.

update: May your admin rights are needed here cause I cannot merge without green CI.

@mtojek mtojek merged commit 8997247 into elastic:master Dec 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team:Integrations Label for the Integrations team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants