Skip to content

Hadoop S3A tests should be added to CI #9282

@guymguym

Description

@guymguym

Environment info

  • NooBaa Version: 5.18.8
  • Platform: RHEL 9.4

Actual behavior

  1. No S3A tests run in the CI

Expected behavior

  1. https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/testing.html
  2. https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/third_party_stores.html

Steps to reproduce

# install
dnf install -y maven
git clone https://github.com/apache/hadoop
cd hadoop
git checkout rel/release-3.4.2
cd hadoop-tools/hadoop-aws

# configure
cat >src/test/resources/auth-keys.xml <<EOF
<configuration>
  <property>
    <name>test.fs.s3a.name</name>
    <value>s3a://hadoop/</value>
  </property>
  <property>
    <name>fs.contract.test.fs.s3a</name>
    <value>${test.fs.s3a.name}</value>
  </property>

  <property>
    <name>fs.s3a.endpoint</name>
    <value>http://10.1.0.1:6001</value>
  </property>
  <property>
    <name>fs.s3a.endpoint.region</name>
    <value>us-east-1</value>
  </property>

  <property>
    <name>fs.s3a.connection.ssl.enabled</name>
    <value>false</value>
  </property>
  <property>
    <name>fs.s3a.path.style.access</name>
    <value>true</value>
  </property>
  <property>
    <name>test.fs.s3a.encryption.enabled</name>
    <value>false</value>
  </property>
  <property>
    <name>test.fs.s3a.create.storage.class.enabled</name>
    <value>false</value>
  </property>
  <property>
    <name>test.fs.s3a.sts.enabled</name>
    <value>false</value>
  </property>
  <property>
    <name>test.fs.s3a.create.create.acl.enabled</name>
    <value>false</value>
  </property>

  <property>
    <name>fs.s3.awsAccessKeyId</name>
    <value>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</value>
  </property>
  <property>
    <name>fs.s3.awsSecretAccessKey</name>
    <value>YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY</value>
  </property>
  <property>
    <name>fs.s3n.awsAccessKeyId</name>
    <value>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</value>
  </property>
  <property>
    <name>fs.s3n.awsSecretAccessKey</name>
    <value>YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY</value>
  </property>
  <property>
    <name>fs.s3a.access.key</name>
    <description>AWS access key ID. Omit for Role-based authentication.</description>
    <value>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</value>
  </property>
  <property>
    <name>fs.s3a.secret.key</name>
    <description>AWS secret key. Omit for Role-based authentication.</description>
    <value>YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY</value>
  </property>

</configuration>
EOF

# run
mvn clean verify -Dtest=TestS3A* -Dit.test=ITestS3A* | tee s3a-tests.log

# summary line e.g. "[ERROR] Tests run: 1152, Failures: 1, Errors: 2, Skipped: 3"
grep "Tests run" s3a-tests.log | tail -1
# failures
grep FAILURE s3a-tests.log

Metadata

Metadata

Assignees

Labels

S3-CompatibilityS3 Compatibility and Namespace over AWS

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions