On successful uploads to a Nexus 3 repo, users received the following feedback:
ERROR: Failed to upload to Nexus with status code 200. Aborting...
The artifacts are uploading successfully, but the client does not recognize the 200 response from Nexus. Further logs below show the command attempting to push multiple artifacts, with some failing due to 413 errors (too large), and others succeeded but giving failure feedback.
12:35:48 + lftools deploy nexus
https://nexus3.akraino.org/repository/rpm.snapshots
/w/workspace/ta-caas-logging-master-merge/work/nexus/rpm.snapshots*12:35:51* Deploying Maven artifacts...12:35:51 /w/workspace/ta-caas-logging-master-merge/work/nexus/rpm.snapshots /w/workspace/ta-caas-logging-master-merge*12:35:52* Uploading TA/release-1/rpms/x86_64/caas-elasticsearch-6.7.0-1.el7.centos.ta.x86_64.rpm*12:35:52* ERROR: Failed to upload to Nexus with status code 413. Aborting...12:35:52 HTTP Response: <html>12:35:52 Uploading TA/release-1/rpms/x86_64/caas-fluentd-1.4.1-1.el7.centos.ta.x86_64.rpm*12:35:52* ERROR: Failed to upload to Nexus with status code 413. Aborting...12:35:52 HTTP Response: <html>12:35:52 Uploading TA/release-1/rpms/x86_64/caas-elasticsearch-debuginfo-6.7.0-1.el7.centos.ta.x86_64.rpm*12:35:52* ERROR: Failed to upload to Nexus with status code 200. Aborting...12:35:52 HTTP Response: 12:35:52 Uploading TA/release-1/rpms/x86_64/caas-fluentd-debuginfo-1.4.1-1.el7.centos.ta.x86_64.rpm*12:35:52* ERROR: Failed to upload to Nexus with status code 200. Aborting...12:35:52 HTTP Response: 12:35:52 Uploading TA/release-1/rpms/Sources/caas-elasticsearch-6.7.0-1.el7.centos.ta.src.rpm*12:35:52* ERROR: Failed to upload to Nexus with status code 200. Aborting...12:35:52 HTTP Response: 12:35:52 Uploading TA/release-1/rpms/Sources/caas-fluentd-1.4.1-1.el7.centos.ta.src.rpm*12:35:52* ERROR: Failed to upload to Nexus with status code 200. Aborting...12:35:52 HTTP Response: