-
Notifications
You must be signed in to change notification settings - Fork 5.5k
quic: test fast-fail if secrets not loaded when create quic connection #18705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
0ea6649
quic: test fast-fail if secrets not loaded when create quic connection
YaoZengzeng 32a8cc2
MockQuicClientTransportFactory
YaoZengzeng b4d5695
output log if create connection failed
YaoZengzeng 22feb33
ENVOY_LOG_TO_LOGGER to ENVOY_LOG_EVERY_POW_2_TO_LOGGER
YaoZengzeng File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -68,6 +68,60 @@ class Http3ConnPoolImplTest : public Event::TestUsingSimulatedTime, public testi | |
| ConnectionPool::InstancePtr pool_; | ||
| }; | ||
|
|
||
| class MockQuicClientTransportSocketFactory : public Quic::QuicClientTransportSocketFactory { | ||
| public: | ||
| MockQuicClientTransportSocketFactory( | ||
| Ssl::ClientContextConfigPtr config, | ||
| Server::Configuration::TransportSocketFactoryContext& factory_context) | ||
| : Quic::QuicClientTransportSocketFactory(move(config), factory_context) {} | ||
|
|
||
| MOCK_METHOD(Envoy::Ssl::ClientContextSharedPtr, sslCtx, ()); | ||
| }; | ||
|
|
||
| TEST_F(Http3ConnPoolImplTest, FastFailWithoutSecretsLoaded) { | ||
| MockQuicClientTransportSocketFactory factory{ | ||
| std::unique_ptr<Envoy::Ssl::ClientContextConfig>(new NiceMock<Ssl::MockClientContextConfig>), | ||
| context_}; | ||
|
|
||
| EXPECT_CALL(factory, sslCtx()).WillRepeatedly(Return(nullptr)); | ||
|
|
||
| EXPECT_CALL(mockHost(), address()).WillRepeatedly(Return(test_address_)); | ||
| EXPECT_CALL(mockHost(), transportSocketFactory()).WillRepeatedly(testing::ReturnRef(factory)); | ||
| // The unique pointer of this object will be returned in createSchedulableCallback_ of | ||
| // dispatcher_, so there is no risk of object leak. | ||
| new Event::MockSchedulableCallback(&dispatcher_); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does this object leak, or does the dispatcher end up returning it at some point? If the latter, please add a short comment which says that. |
||
| Network::ConnectionSocket::OptionsSharedPtr options; | ||
| Network::TransportSocketOptionsConstSharedPtr transport_options; | ||
| ConnectionPool::InstancePtr pool = | ||
| allocateConnPool(dispatcher_, random_, host_, Upstream::ResourcePriority::Default, options, | ||
| transport_options, state_, simTime(), quic_stat_names_, store_); | ||
|
|
||
| EXPECT_EQ(static_cast<Http3ConnPoolImpl*>(pool.get())->instantiateActiveClient(), nullptr); | ||
| } | ||
|
|
||
| TEST_F(Http3ConnPoolImplTest, FailWithSecretsBecomeEmpty) { | ||
| MockQuicClientTransportSocketFactory factory{ | ||
| std::unique_ptr<Envoy::Ssl::ClientContextConfig>(new NiceMock<Ssl::MockClientContextConfig>), | ||
| context_}; | ||
|
|
||
| Ssl::ClientContextSharedPtr ssl_context(new Ssl::MockClientContext()); | ||
| EXPECT_CALL(factory, sslCtx()) | ||
| .WillOnce(Return(ssl_context)) | ||
| .WillOnce(Return(nullptr)) | ||
| .WillRepeatedly(Return(ssl_context)); | ||
|
|
||
| EXPECT_CALL(mockHost(), address()).WillRepeatedly(Return(test_address_)); | ||
| EXPECT_CALL(mockHost(), transportSocketFactory()).WillRepeatedly(testing::ReturnRef(factory)); | ||
| new Event::MockSchedulableCallback(&dispatcher_); | ||
| Network::ConnectionSocket::OptionsSharedPtr options; | ||
| Network::TransportSocketOptionsConstSharedPtr transport_options; | ||
| ConnectionPool::InstancePtr pool = | ||
| allocateConnPool(dispatcher_, random_, host_, Upstream::ResourcePriority::Default, options, | ||
| transport_options, state_, simTime(), quic_stat_names_, store_); | ||
|
|
||
| EXPECT_EQ(static_cast<Http3ConnPoolImpl*>(pool.get())->instantiateActiveClient(), nullptr); | ||
| } | ||
|
|
||
| TEST_F(Http3ConnPoolImplTest, CreationWithBufferLimits) { | ||
| EXPECT_CALL(mockHost().cluster_, perConnectionBufferLimitBytes); | ||
| initialize(); | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is
warngoing to be too much output in the log? I presume if this happens once, it'll probably happen for every connection attempt. Maybe useENVOY_LOG_PERIODIC_TO_LOGGERorENVOY_LOG_EVERY_POW_2_TO_LOGGER?Is there any failure metric that increases in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ggreenway updated to ENVOY_LOG_EVERY_POW_2_TO_LOGGER.
As for failure metric, there seems to be no metric to indicate the failure of quic connection creation. From my research, even for HTTP 1/2, there is only a metric bind_errors_ which is used to indicate the bind error when failed to create client network connection.