getting service error without explanation when using aggregation service about aggregation-service HOT 11 OPEN

we have downgraded to version 2.4.3 and it works for us @yuki-tsuchiya @pisutpon

from aggregation-service.

colsed

from aggregation-service.

closed by mistake
we have a new error :
when sending the request:
"result_info": {
"return_code": "PRIVACY_BUDGET_AUTHENTICATION_ERROR",
"return_message": "com.google.aggregate.adtech.worker.exceptions.AggregationJobProcessException: Aggregation service is not authenticated to call privacy budget service. This could happen due to a misconfiguration during enrollment. Please contact support for resolution. \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.consumePrivacyBudgetUnits(ConcurrentAggregationProcessor.java:465) \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.process(ConcurrentAggregationProcessor.java:342) \n com.google.aggregate.adtech.worker.WorkerPullWorkService.run(WorkerPullWorkService.java:143)\nThe root cause is: com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngine$TransactionEngineException: PRIVACY_BUDGET_CLIENT_UNAUTHENTICATED \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.createTransactionEngineException(TransactionEngineImpl.java:213) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.proceedToNextPhase(TransactionEngineImpl.java:68) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.executeDistributedPhase(TransactionEngineImpl.java:206)",
"error_summary": {
"error_counts": [],
"error_messages": []
},
- we are using 2.5.0 version (newest one)
- we are using the new ARN you have sent us during our meeting (which seems to solve the SERVICE_ERROR issue)
- we have sent you the relevant files (main.tf, release_params.auto.tfvars,{env}.auto.tfvars) via mail
- we use the new ami 2.5.0 (pre built and copied to our region with our AWS ID as our ami_owner)
i do see that you hae a record of this error here
but we are not sure what to do with this

from aggregation-service.

We got the same issue when we upgraded the aggregation service to the version 2.5. The return code was PRIVACY_BUDGET_AUTHENTICATION_ERROR

from aggregation-service.

We are experiencing the same issue when we upgraded the aggregation service to version 2.5. If anyone has a solution or workaround for this problem, we would greatly appreciate it.

from aggregation-service.

@TomerGoldstein @yuki-tsuchiya @pisutpon Thanks for making us aware of the issue. We're investigating it and will provide an update when we have one. In the meantime, please continue to use version 2.4.3.

from aggregation-service.

Hi @TomerGoldstein ,

Would you be able to provide the full getJob response or timing of the request.

from aggregation-service.

@maybellineboon hey!
this is a response that i got when using version 2.5.0:

    "result_info": {
        "return_code": "PRIVACY_BUDGET_AUTHENTICATION_ERROR",
        "return_message": "com.google.aggregate.adtech.worker.exceptions.AggregationJobProcessException: Aggregation service is not authenticated to call privacy budget service. This could happen due to a misconfiguration during enrollment. Please contact support for resolution. \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.consumePrivacyBudgetUnits(ConcurrentAggregationProcessor.java:465) \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.process(ConcurrentAggregationProcessor.java:342) \n com.google.aggregate.adtech.worker.WorkerPullWorkService.run(WorkerPullWorkService.java:143)\nThe root cause is: com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngine$TransactionEngineException: PRIVACY_BUDGET_CLIENT_UNAUTHENTICATED \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.createTransactionEngineException(TransactionEngineImpl.java:213) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.proceedToNextPhase(TransactionEngineImpl.java:68) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.executeDistributedPhase(TransactionEngineImpl.java:206)",
        "error_summary": {
            "error_counts": [],
            "error_messages": []
        },
        "finished_at": "2024-06-12T17:18:07.491437708Z"
    }

please let me know if i can do anything else to help :)

also this is a response for the same exact inputs (chang the name of directories but these are the same files):

    "result_info": {
        "return_code": "PRIVACY_BUDGET_AUTHENTICATION_ERROR",
        "return_message": "com.google.aggregate.adtech.worker.exceptions.AggregationJobProcessException: Aggregation service is not authenticated to call privacy budget service. This could happen due to a misconfiguration during enrollment. Please contact support for resolution. \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.consumePrivacyBudgetUnits(ConcurrentAggregationProcessor.java:465) \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.process(ConcurrentAggregationProcessor.java:342) \n com.google.aggregate.adtech.worker.WorkerPullWorkService.run(WorkerPullWorkService.java:143)\nThe root cause is: com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngine$TransactionEngineException: PRIVACY_BUDGET_CLIENT_UNAUTHENTICATED \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.createTransactionEngineException(TransactionEngineImpl.java:213) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.proceedToNextPhase(TransactionEngineImpl.java:68) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.executeDistributedPhase(TransactionEngineImpl.java:206)",
        "error_summary": {
            "error_counts": [],
            "error_messages": []
}

from aggregation-service.

Hi @TomerGoldstein ,

Thank you for sharing the information. We are working on the fix and will update everyone once the fix has been rolled out.

from aggregation-service.

Hi all, a fix for the issue with Aggregation Service 2.5.0 has been identified, and we expect it to be rolled out by Monday, June 24. Please refer to the Public Status Dashboard for real-time updates: https://status.privacysandbox.com/

from aggregation-service.

Hello, we have resolved the issue with Aggregation Service version 2.5.0. All users can now upgrade to 2.5.0 following the instructions for AWS or GCP. Thank you for your patience and continued support.

from aggregation-service.