errose28 commented on PR #11074: URL: https://github.com/apache/ozone/pull/11074#issuecomment-5416935741
The last commit fixed an existing issue on the branch where artifacts from acceptance test runs would not be uploaded, so there were no logs to see why the test was failing. With that fixed, we can now see that the upgrade acceptance test fails with: ``` NOT_SUPPORTED_OPERATION Finalize rejected: the following OM peers did not confirm matching software version (expected version=ZDU (100)): om1 (unreachable: DestHost:destPort om1:9862 , LocalHost:localPort om2/10.9.0.12:0. Failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]), om3 (unreachable: DestHost:destPort om3:9862 , LocalHost:localPort om2/10.9.0.12:0. Failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]) ``` Acceptance tests are still using the old CLI. Prior to this change that means they only finalized OM by submitting the same finalize request the background service does. Now they go through the proper path, so it is the first time the peer version check RPC between OMs is tested in a secure environment. We need to send this RPC as the logged-in OM user. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
