Description of problem: When trying to run Metering on an IPV6 AWS cluster, using an existing S3 bucket as storage, Hive metastore/server cannot connect to the specified S3 bucket endpoint. Version-Release number of selected component (if applicable): 4.4 How reproducible: Always Steps to Reproduce: 1. ./bin/deploy-metering install 2. Use hive.s3 as a storage configuration with an existing S3 bucket 3. Actual results: Expected results: Additional info:
verified with a meteringconfig that uses a s3 bucket and able to create a report successfully pruan@MacBook-Pro ~/workspace/gocode/src/github.com/operator-framework/operator-metering (master●)$ oc get pods NAME READY STATUS RESTARTS AGE hive-metastore-0 2/2 Running 0 3m17s hive-server-0 3/3 Running 0 3m17s metering-operator-7b96748b96-96njb 2/2 Running 0 5m54s presto-coordinator-0 2/2 Running 0 2m43s reporting-operator-6fc7fc5c4c-nl2pl 2/2 Running 0 2m8s pruan@MacBook-Pro ~/workspace/v3-testfiles/metering/rollup_reports (master●)$ oc get reports NAME QUERY SCHEDULE RUNNING FAILED LAST REPORT TIME AGE persistentvolumeclaim-usage-now persistentvolumeclaim-usage Finished 2020-12-30T23:59:59Z 7s
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, 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/RHBA-2020:0581