generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 272
Closed
Labels
area/runtimeIssues or PRs as related to controller runtime, common reconciliation logic, etcIssues or PRs as related to controller runtime, common reconciliation logic, etckind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
Describe the bug
duplicate entries like name, namespace, generation id in the logs
2021-09-06T17:58:24.151Z DEBUG ackrt >> rm.ReadOne
{"kind": "Model", "namespace": "default", "name": "xgboost-model-7hn2mkvive31wtawu0", "generation": 1,
"account": "169544399729", "role": "", "region": "us-west-2", "is_adopted": false, "kind": "Model",
"namespace": "default", "name": "xgboost-model-7hn2mkvive31wtawu0", "generation": 1}
it gets confusing when generation id changes. See below, generation - 2 and 3 both in the same log
2021-09-06T17:58:55.474Z DEBUG ackrt < r.patchResourceStatus
{"kind": "Model", "namespace": "default", "name": "xgboost-model-7hn2mkvive31wtawu0", "generation": 2,
"account": "169544399729", "role": "", "region": "us-west-2", "kind": "Model", "namespace":
"default", "name": "xgboost-model-7hn2mkvive31wtawu0", "generation": 3}
Steps to reproduce
run test_model.py in sagemaker-controller. should be able to see this in any service controller logs
Expected outcome
correct generation-id the controller is acting on and no duplicate entry in the logs
Metadata
Metadata
Assignees
Labels
area/runtimeIssues or PRs as related to controller runtime, common reconciliation logic, etcIssues or PRs as related to controller runtime, common reconciliation logic, etckind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.