-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
5
-
False
-
-
False
-
-
I made a couple of changes to egress since September.
One was to remove the "account_config" table and add the "sku_product_tag" table. The other was to update the export script since it wasn't working (The pipenv file we were inserting into the container was no longer compatible with older versions of Python).
Somewhere along the way, this broke egress. The jobs are failing:
+ for table in $EXPORTED_TABLES+ echo 'Table '\''account_config'\'': Data collection started.'Table 'account_config': Data collection started.+ psql -h rhsm-prod.ckxxru2ayexw.us-east-1.rds.amazonaws.com -U postgres rhsm-subscriptions -c 'COPY account_config TO STDOUT CSV'++ date -I+ pipenv run aws s3 cp - s3://rhsm-subscriptions-egress-prod/production_data/account_config/historic/2024-10-07-account_config.csvERROR: relation "account_config" does not exist++ date -I+ pipenv run aws s3 cp s3://rhsm-subscriptions-egress-prod/production_data/account_config/historic/2024-10-07-account_config.csv s3://rhsm-subscriptions-egress-prod/production_data/account_config/latest/full_data.csvfatal error: An error occurred (403) when calling the HeadObject operation: Forbidden
The $EXPORTED_TABLES environment variable is
account_config account_services billable_usage_remittance events host_tally_buckets hosts instance_measurements instance_monthly_totals offering org_config sku_child_sku sku_oid subscription subscription_measurements subscription_product_ids tally_measurements tally_snapshots
"account_config" shouldn't even be there. Obviously I missed something in my update.
