Bug 1882397
Summary: | MCG decompression problem with snappy on s390x arch | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Venkat <vpiniset> | ||||||||||||||||
Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> | ||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> | ||||||||||||||||
Severity: | high | Docs Contact: | |||||||||||||||||
Priority: | unspecified | ||||||||||||||||||
Version: | 4.6 | CC: | ebenahar, etamir, jalbo, jthottan, kramdoss, muagarwa, nbecker, ocs-bugs, tdesala, uweigand | ||||||||||||||||
Target Milestone: | --- | Keywords: | AutomationBackLog | ||||||||||||||||
Target Release: | OCS 4.6.0 | ||||||||||||||||||
Hardware: | s390x | ||||||||||||||||||
OS: | Linux | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
Fixed In Version: | v4.6.0-128.ci | Doc Type: | If docs needed, set a value | ||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2020-12-17 06:24:38 UTC | Type: | Bug | ||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
Embargoed: | |||||||||||||||||||
Attachments: |
|
Description
Venkat
2020-09-24 13:18:52 UTC
Please attach logs Created attachment 1719291 [details]
Noobaa-Operator-Log
Created attachment 1719292 [details]
Noobaa-DB-Log
Created attachment 1719293 [details]
Noobaa-Core-Log
Created attachment 1719294 [details]
Testcase-Log
Created attachment 1719295 [details]
Testcase-Flow
Created attachment 1719296 [details]
Noobaa-Endpoint-Log
Created attachment 1719404 [details]
Investigation log
Followed below steps as part of investigation with @Jacky,Albo Steps: 1. Created a local file(sample1.txt) 2. Uploaded file to bucket(first.bucket) successfully 3. Tried to download file from bucket to locally(sample2.txt). However it was failed with below error. Next Steps: Jacky will into the logs which I'm attaching now Logs: /aws # aws s3 cp --endpoint=https://s3.openshift-storage.svc:443 --no-verify-ssl sample1.txt s3://first.bucket/sample1.txt /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( upload: ./sample1.txt to s3://first.bucket/sample1.txt /aws # /aws # aws s3 cp --no-verify-ssl --endpoint=https://s3.openshift-storage.svc:443 s3://first.bucket/sample1.txt sample2.txt /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( ... ... /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( /usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:979: InsecureRequestWarning: Unverified HTTPS request is being made to host 's3.openshift-storage.svc'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings warnings.warn( download failed: s3://first.bucket/sample1.txt to ./sample2.txt Connection was closed before we received a valid response from endpoint URL: "https://s3.openshift-storage.svc:443/first.bucket/sample1.txt". /aws # ls sample1.txt /aws # Ref for noobaa endpoint logs : https://bugzilla.redhat.com/attachment.cgi?id=1719404 So with help of Venkat, we disabled the compression of a second bucket and then it works - So it is looking like an issue with the snappy compression on top of Z arch (In reply to Jacky Albo from comment #12) > So with help of Venkat, we disabled the compression of a second bucket and > then it works - So it is looking like an issue with the snappy compression > on top of Z arch Hi Jacky, is this something we can reproduce stand-along just using snappy or do we need to run all of noobaa? If there's a platform-specific problem with snappy we'll be happy to help investigate. (In reply to Ulrich Weigand from comment #13) > (In reply to Jacky Albo from comment #12) > > So with help of Venkat, we disabled the compression of a second bucket and > > then it works - So it is looking like an issue with the snappy compression > > on top of Z arch > > Hi Jacky, is this something we can reproduce stand-along just using snappy > or do we need to run all of noobaa? If there's a platform-specific problem > with snappy we'll be happy to help investigate. Hey Ulrich, we are suspecting snappy on top of IBM Z. we were using an old version 1.1.7 which seems to fail(we want to verify) but we also want to check 1.1.8 as it maybe fixes the issues. So if you can help us with the following: run the snappy tests on top of 1.1.7 and check if it fails https://github.com/google/snappy#tests-and-benchmarks and then run it again on top of latest 1.1.8 and see if it fixes the issues. please also mind this: Snappy assumes little-endian throughout, and needs to byte-swap data in several places if running on a big-endian platform. I've built snappy-1.1.7 on IBM Z and ran the unit tests without issues: [uweigand@oc3748833570 snappy-1.1.7]$ ./build/snappy_unittest Running microbenchmarks. WARNING: Compiled with assertions enabled, will be slow. WARNING: Compiled without optimization, will be slow. Benchmark Time(ns) CPU(ns) Iterations --------------------------------------------------- BM_UFlat/0 273100 264288 743 369.5MB/s html BM_UFlat/1 2563600 2553640 100 262.2MB/s urls BM_UFlat/2 6305 6305 26143 18.2GB/s jpg BM_UFlat/3 623 623 307692 305.7MB/s jpg_200 BM_UFlat/4 35004 35004 5259 2.7GB/s pdf BM_UFlat/5 1056087 1056087 183 369.9MB/s html4 BM_UFlat/6 967948 967958 215 149.8MB/s txt1 BM_UFlat/7 832586 832590 237 143.4MB/s txt2 BM_UFlat/8 2545910 2545930 100 159.9MB/s txt3 BM_UFlat/9 3507970 3500290 100 131.3MB/s txt4 BM_UFlat/10 250565 250568 821 451.4MB/s pb BM_UFlat/11 1013203 1013213 192 173.5MB/s gaviota BM_UIOVec/0 580520 580420 340 168.3MB/s html BM_UIOVec/1 4899380 4899150 100 136.7MB/s urls BM_UIOVec/2 7294 7294 23228 15.7GB/s jpg BM_UIOVec/3 1202 1202 155038 158.6MB/s jpg_200 BM_UIOVec/4 78722 75328 2719 1.3GB/s pdf BM_UValidate/0 121744 117602 1740 830.4MB/s html BM_UValidate/1 1367925 1328721 147 503.9MB/s urls BM_UValidate/2 554 554 215053 206.9GB/s jpg BM_UValidate/3 372 372 555555 511.7MB/s jpg_200 BM_UValidate/4 10952 10952 17953 8.7GB/s pdf BM_ZFlat/0 696946 696957 281 140.1MB/s html (22.31 %) BM_ZFlat/1 9398280 9397410 100 71.2MB/s urls (47.78 %) BM_ZFlat/2 23858 23858 5748 4.8GB/s jpg (99.95 %) BM_ZFlat/3 2880 2880 74349 66.2MB/s jpg_200 (73.00 %) BM_ZFlat/4 77167 77168 2760 1.2GB/s pdf (83.30 %) BM_ZFlat/5 2670450 2670470 100 146.3MB/s html4 (22.52 %) BM_ZFlat/6 2606160 2606190 100 55.7MB/s txt1 (57.88 %) BM_ZFlat/7 2225400 2225420 100 53.6MB/s txt2 (61.91 %) BM_ZFlat/8 6785170 6785220 100 60.0MB/s txt3 (54.99 %) BM_ZFlat/9 9139910 9139950 100 50.3MB/s txt4 (66.26 %) BM_ZFlat/10 610166 610175 336 185.3MB/s pb (19.68 %) BM_ZFlat/11 2150550 2150580 100 81.7MB/s gaviota (37.72 %) Running correctness tests. Crazy decompression lengths not checked on 64-bit build All tests passed. Is there anything else I should be testing? I build snappy-1.1.8 on Z and didn't observe any issues in unit tests [root@ocsvm2 snappy]# ./build/snappy_unittest Running microbenchmarks. WARNING: Compiled with assertions enabled, will be slow. WARNING: Compiled without optimization, will be slow. Benchmark Time(ns) CPU(ns) Iterations --------------------------------------------------- BM_UFlat/0 322510 285070 699 342.6MB/s html BM_UFlat/1 2899060 2877930 100 232.7MB/s urls BM_UFlat/2 5723 5685 34722 20.2GB/s jpg BM_UFlat/3 735 698 270270 273.2MB/s jpg_200 BM_UFlat/4 30219 30008 6633 3.2GB/s pdf BM_UFlat/5 1151541 1111145 179 351.6MB/s html4 BM_UFlat/6 1300909 1266677 155 114.5MB/s txt1 BM_UFlat/7 1070079 1071375 176 111.4MB/s txt2 BM_UFlat/8 3298810 3279140 100 124.1MB/s txt3 BM_UFlat/9 4390680 4379370 100 104.9MB/s txt4 BM_UFlat/10 238867 237990 829 475.2MB/s pb BM_UFlat/11 1346576 1373402 144 128.0MB/s gaviota BM_UIOVec/0 313127 304832 673 320.4MB/s html BM_UIOVec/1 2763230 2778320 100 241.0MB/s urls BM_UIOVec/2 6173 5817 25348 19.7GB/s jpg BM_UIOVec/3 1283 1289 153846 147.9MB/s jpg_200 BM_UIOVec/4 34935 33998 5851 2.8GB/s pdf BM_UValidate/0 136162 138365 1499 705.8MB/s html BM_UValidate/1 1478303 1505015 132 444.9MB/s urls BM_UValidate/2 679 674 235294 169.8GB/s jpg BM_UValidate/3 433 424 465116 449.4MB/s jpg_200 BM_UValidate/4 13209 12990 15232 7.3GB/s pdf BM_ZFlat/0 809714 797008 249 122.5MB/s html (22.31 %) BM_ZFlat/1 10190700 10109470 100 66.2MB/s urls (47.78 %) BM_ZFlat/2 26991 27401 7601 4.2GB/s jpg (99.95 %) BM_ZFlat/3 3713 3638 51813 52.4MB/s jpg_200 (73.00 %) BM_ZFlat/4 100196 99559 2001 980.9MB/s pdf (83.30 %) BM_ZFlat/5 3227490 3268850 100 119.5MB/s html4 (22.52 %) BM_ZFlat/6 2908660 2874960 100 50.5MB/s txt1 (57.88 %) BM_ZFlat/7 2449890 2386580 100 50.0MB/s txt2 (61.91 %) BM_ZFlat/8 8021930 7817580 100 52.1MB/s txt3 (54.99 %) BM_ZFlat/9 10034460 9834090 100 46.7MB/s txt4 (66.26 %) BM_ZFlat/10 767171 754140 263 150.0MB/s pb (19.68 %) BM_ZFlat/11 2585760 2578570 100 68.2MB/s gaviota (37.72 %) BM_ZFlatAll/0 42188290 41585160 100 67.2MB/s 12 files BM_ZFlatIncreasingTableSize/0 450571 456592 434 67.9MB/s 7 tables Running correctness tests. Crazy decompression lengths not checked on 64-bit build All tests passed. [root@ocsvm2 snappy]# Please suggest next steps. OK, quick update. I just built mainline noobaa-core from github (running "npm install" and "rpm run build"), and then executed the following command which appears to reproduce the error we've seen in the ocs-ci test case: uweigand@m8345019:~/noobaa-core$ node src/tools/coding_speed.js --size 1000 --decode --md5 --sha256 --compare OpenSSL 1.1.1c 28 May 2019 setting up init_rand_seed: starting ... read_rand_seed: opening /dev/random ... NO LOCAL CONFIG Arguments: { "size": 1000, "decode": true, "md5": true, "sha256": true, "compare": true, "forks": 1, "encode": true, "erase": true, "ec": false, "verbose": false, "sse_c": false } (node:53580) [DEP0091] DeprecationWarning: crypto.DEFAULT_ENCODING is deprecated. (node:53580) [DEP0010] DeprecationWarning: crypto.createCredentials is deprecated. Use tls.createSecureContext instead. (node:53580) [DEP0011] DeprecationWarning: crypto.Credentials is deprecated. Use tls.SecureContext instead. read_rand_seed: reading 32 bytes from /dev/random ... read_rand_seed: got 32 bytes from /dev/random, total 32 ... init_rand_seed: seeding with 32 bytes rand_seed: OpenSSL 1.1.1c 28 May 2019 seeding randomness Unhandled rejection Error: had chunk errors Unhandled rejection Error: had chunk errors CHUNK ERRORS: nb_snappy_uncompress: invalid data at p.promise.then.catch.err (/home/uweigand/noobaa-core/src/tools/coding_speed.js:146:19) at tryCatcher (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/promise.js:547:31) at Promise._settlePromise (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/promise.js:604:18) at Promise._settlePromise0 (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/promise.js:649:10) at Promise._settlePromises (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/promise.js:725:18) at _drainQueueStep (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/async.js:93:12) at _drainQueue (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/async.js:86:9) at Async._drainQueues (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/async.js:102:5) at Immediate.Async.drainQueues [as _onImmediate] (/home/uweigand/noobaa-core/node_modules/bluebird/js/release/async.js:15:14) at runCallback (timers.js:705:18) at tryOnImmediate (timers.js:676:5) at processImmediate (timers.js:658:5) generate_entropy: entropy_avail 2977 init_rand_seed: done Will continue to investigate. Found the problem. As you suggested, it has to do with whether snappy is build using cmake or not. When building with cmake, the infrastructure will predefine a variable SNAPPY_IS_BIG_ENDIAN on big endian platforms, causing the snappy code to perform all appropriate byte swaps. But when built without cmake, that test isn't run and the variable is never defined, which means the code assumes little endian always. The following quick hack gets it to work correctly on IBM Z: diff --git a/src/native/common.gypi b/src/native/common.gypi index 1a8374904..555fe85f8 100644 --- a/src/native/common.gypi +++ b/src/native/common.gypi @@ -82,7 +82,7 @@ 'defines!': ['DEBUG', '_DEBUG'], 'cflags!': ['-Os', '-O0', '-O1', '-O2'], 'cflags_cc!': ['-Os', '-O0', '-O1', '-O2'], - 'cflags': ['-O3'], + 'cflags': ['-O3', '-DSNAPPY_IS_BIG_ENDIAN'], 'xcode_settings': { 'GCC_GENERATE_DEBUGGING_SYMBOLS': 'NO', 'GCC_INLINES_ARE_PRIVATE_EXTERN': 'YES', Of course this is not a correct fix, but I'm not really familiar with the node-gyp infrastructure here. Is there some place where predefines that would have otherwise been set by a cmake-time check are now set instead? That variable should be added there. With this patch I now see the following output instead: uweigand@m8345019:~/noobaa-core$ node src/tools/coding_speed.js --size 1000 --decode --md5 --sha256 --compare OpenSSL 1.1.1c 28 May 2019 setting up init_rand_seed: starting ... read_rand_seed: opening /dev/random ... NO LOCAL CONFIG Arguments: { "size": 1000, "decode": true, "md5": true, "sha256": true, "compare": true, "forks": 1, "encode": true, "erase": true, "ec": false, "verbose": false, "sse_c": false } (node:477) [DEP0091] DeprecationWarning: crypto.DEFAULT_ENCODING is deprecated. (node:477) [DEP0010] DeprecationWarning: crypto.createCredentials is deprecated. Use tls.createSecureContext instead. (node:477) [DEP0011] DeprecationWarning: crypto.Credentials is deprecated. Use tls.SecureContext instead. read_rand_seed: reading 32 bytes from /dev/random ... read_rand_seed: got 32 bytes from /dev/random, total 32 ... init_rand_seed: seeding with 32 bytes rand_seed: OpenSSL 1.1.1c 28 May 2019 seeding randomness generate_entropy: entropy_avail 3071 init_rand_seed: done Chunk Coder Speed: 222.8 MB/sec (average 222.8) Chunk Coder Speed: 263.9 MB/sec (average 242.9) Chunk Coder Speed: 272.2 MB/sec (average 252.6) AVERAGE CHUNK SIZE 4032985 MD5 = GSi8JUxoJgTmxU5e9CASPw== SHA256 = KnAqG31ltDQqRkoSRLHfAN5M+pMGidUzn6TdL/7nJgY= I've verified this issue on latest OCS builds and it is working as expected. [root@ocplnx31 ~]# oc get csv NAME DISPLAY VERSION REPLACES PHASE ocs-operator.v4.6.0-607.ci OpenShift Container Storage 4.6.0-607.ci Succeeded [root@ocplnx31 ~]# oc version Client Version: 4.5.16 Server Version: 4.5.15 Kubernetes Version: v1.18.3+2fbd7c7 [root@ocplnx31 ~]# 13:47:48 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod ls -A1 /original 13:47:49 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Downloaded objects: ['airbus.jpg', 'apple.mp4', 'bolder.jpg', 'book.txt', 'canada.jpg', 'danny.webm', 'danny2.webm', 'danny3.webm', ' enwik8', 'goldman.webm', 'random1.txt', 'random10.txt', 'random2.txt', 'random3.txt', 'random4.txt', 'random5.txt', 'random6.txt', 'random7.txt', 'random8.txt', 'random9.txt', 'rome.jpg', 's teve.webm'] 13:47:49 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Syncing all objects and directories from /original to s3://s3-bucket-d817b354a1d1446ca203169b09df140f 13:47:49 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod sh -c "AWS_CA_BUNDLE=/cert/ser vice-ca.crt AWS_ACCESS_KEY_ID=***** AWS_SECRET_ACCESS_KEY=***** AWS_DEFAULT_REGION=us-east-2 aws s3 --endpoint=***** sync /original s3://s3-bucket-d817b354a1d1446ca203169b09df140f" 13:47:59 - MainThread - tests.manage.mcg.test_object_integrity - INFO - Downloading all objects from MCG bucket to awscli pod 13:47:59 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Syncing all objects and directories from s3://s3-bucket-d817b354a1d1446ca203169b09df140f to /result 13:47:59 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod sh -c "AWS_CA_BUNDLE=/cert/ser vice-ca.crt AWS_ACCESS_KEY_ID=***** AWS_SECRET_ACCESS_KEY=***** AWS_DEFAULT_REGION=us-east-2 aws s3 --endpoint=***** sync s3://s3-bucket-d817b354a1d1446ca203169b09df140f /result" 13:48:07 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/airbus.jpg /r esult/airbus.jpg 13:48:09 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/airbus.jpg and /result/airbus.jpg 13:48:09 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/apple.mp4 /re sult/apple.mp4 13:48:11 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/apple.mp4 and /result/apple.mp4 13:48:11 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/bolder.jpg /r esult/bolder.jpg 13:48:13 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/bolder.jpg and /result/bolder.jpg 13:48:13 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/book.txt /res ult/book.txt 13:48:15 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/book.txt and /result/book.txt 13:48:15 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/canada.jpg /r esult/canada.jpg 13:48:16 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/canada.jpg and /result/canada.jpg 13:48:16 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/danny.webm /r esult/danny.webm 13:48:18 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/danny.webm and /result/danny.webm 13:48:18 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/danny2.webm / result/danny2.webm 13:48:20 - MainThread - ocs_ci.ocs.bucket_utils - INFO - Passed: MD5 comparison for /original/danny2.webm and /result/danny2.webm 13:48:20 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n default --kubeconfig /root/ocp4-workdir-tb4/auth/kubeconfig rsh awscli-relay-pod md5sum /original/danny3.webm / result/danny3.webm Thank you Venkat. Moving this BZ to Verified state based on Comment22. Nimrod, do we need doc_text here. Flag was set automatically because the severity was high. We don't it's part of the multiarch effort. When OCS will be released on Z the will be docs enough :) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat OpenShift Container Storage 4.6.0 security, bug fix, enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5605 |