Status Update
No update yet.
Comments
ba...@google.com
ma...@google.com
Chrome Diagnostics Report of following results:
The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is
Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?
em...@desjardins.com
what m126 bugs could this report be a duplicate of ?
Not anything off the top of my head now (maybe Jason knows other). Since the device is not enterprise-enrolled according to the information in #1, I assume it should not hit the diagnostic DNS issue in
But I assume the reporter also encountered the issue of "no connection to gateway" in the diagnostic app, which is partially fixed on M128 in
Re #1,
Thanks for reporting the issue and sorry for the late reply here. A few questions to help us understanding the issue bettter:
- Are you still experiencing this issue? If so, could you file a feedback report (alt-shift-i, and put "
b/360530624 - Does it only happen on a certain WiFi network? If it's the case, do you by chance have other devices (not Chromebook) to see if they work on the same network?
Thanks!
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Cannot attach an AKS cluster with taints on all worker nodes
What you expected to happen:
The customer wants to know if there is a planned in the product roadmap in a
near future to allow customizing the tolerations on the agent
Steps to reproduce:
Your AKS nodes have taints that prevent the agent pods from being scheduled, and you can't modify those taints. Since you also can't modify the agent pod tolerations, you need to find a way to make the nodes more tolerant of the agent pods, without impacting your existing workloads. Adding more taints won't solve this, as it will only make scheduling harder.
Other information (workarounds you have tried, documentation consulted, etc):