| << Back to previous view |
|
[QB-3321] Kubernetes cloud profile not working
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 8.0.28 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | AlSt | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
We added a kubernetes cloud profile. The node test launch works fine.
We also added a attribute and a resource which is matching the attribute. Testing a configuration where we require that resource only shows WAITING_NODE. Output is just when I activate trace logging: 2019-01-15 11:18:41,907 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - Allocating step resource (configuration: root/test-config, build: not assigned, step: master)... 2019-01-15 11:18:41,907 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - No candiate nodes found, checking cloud profiles... 2019-01-15 11:18:41,907 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - Constructing cloud profile virtual nodes... 2019-01-15 11:18:41,907 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - Calculating resource count... 2019-01-15 11:18:41,908 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - Calculating virtual node candidicates... 2019-01-15 11:18:41,908 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - No matching cloud profile found 2019-01-15 11:18:41,908 [Thread-74] TRACE com.pmease.quickbuild.DefaultBuildEngine - Cloud profile checking completed So trace logging does not show anything why it would not match the cloud profile although I would expect trace logging to really add trace information. In my opinion this is just debug logging not trace logging. Also tried just setting the node selection on the master step directly to look for a node where the attribute is set without using a resource. No luck either. |
| Comments |
| Comment by AlSt [ 15/Jan/19 12:30 PM ] |
|
We found the reason now by accident. But as I said some real trace logging would help in that case most likely.
Like why a cloud profile does not match. |