chenyulin0719 commented on PR #900:
URL: https://github.com/apache/yunikorn-k8shim/pull/900#issuecomment-2321111610

   @craigcondit Thanks for the review! I just updated this PR as suggested. 
   
   1. Adjust warning message in logs:
   ```
   2024-08-30T12:22:04.272Z     WARN    shim.cache.task cache/task.go:539       
Pod has inconsistent application metadata and may be rejected in a future 
YuniKorn release.     {"appID": "application-sleep-00001-annotation", 
"podName": "pod-with-inconsistent-app-id", "error": "annotation 
yunikorn.apache.org/app-id: \"application-sleep-00001-annotation\" doesn't 
match label applicationId: \"application-sleep-00001\""}
   
   2024-08-30T12:22:04.272Z     WARN    shim.cache.task cache/task.go:548       
Pod has inconsistent queue metadata and may be rejected in a future YuniKorn 
release.   {"appID": "application-sleep-00002", "podName": 
"pod-with-inconsistent-queue", "error": "annotation yunikorn.apache.org/queue: 
\"root.sandbox-annotation\" doesn't match label queue: \"root.sandbox\""}
   ```
   2. Add warning message to Pod event: (The event type is "Warning")
   ```
   Warning  Scheduling         4s    yunikorn  Pod has inconsistent application 
metadata and may be rejected in a future YuniKorn release: annotation 
yunikorn.apache.org/app-id: "application-sleep-00001-annotation" doesn't match 
label applicationId: "application-sleep-00001"
   ```
   
   ```
   Warning  Scheduling         8m2s  yunikorn  Pod has inconsistent queue 
metadata and may be rejected in a future YuniKorn release: annotation 
yunikorn.apache.org/queue: "root.sandbox-annotation" doesn't match label queue: 
"root.sandbox"
   ```
   
   <img width="1286" alt="image" 
src="https://github.com/user-attachments/assets/bc9a5442-ec7c-40f4-af0a-ae369cea9c0d";>
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to