What happened:
Tried to provision a HANA instance onto a u-6tb1.112xlarge machine.
The autoscaler log is showing following behavious:
`
2023-02-08 00:02:49 | {"log":"Generating node template only using nodeTemplate from MachineClass shoot--hc-us10--prod-haas-hana-xxl-z1-723c0: template resources-\u003e cpu: 448,memory: 6Ti","pid":"1","severity":"INFO","source":"mcm_manager.go:673"}
2023-02-08 00:06:34 | {"log":"Pod xxx-xxx-xxx-xxx-xx can't be scheduled on shoot--hc-us10--prod-haas-hana-xxl-z1, predicate checking error: node(s) had volume node affinity conflict; predicateName=VolumeBinding; reasons: node(s) had volume node affinity conflict; debugInfo=","pid":"1","severity":"INFO","source":"scale_up.go:300"}
`
What you expected to happen:
That the autoscaler spins up a u-6tb1.112xlarge machine
How to reproduce it (as minimally and precisely as possible):
Create a pod that should be scheduled onto a u-6tb1.112xlarge machine and set the minimum of that worker group to 0
What happened: Tried to provision a HANA instance onto a u-6tb1.112xlarge machine.
The autoscaler log is showing following behavious:
` 2023-02-08 00:02:49 | {"log":"Generating node template only using nodeTemplate from MachineClass shoot--hc-us10--prod-haas-hana-xxl-z1-723c0: template resources-\u003e cpu: 448,memory: 6Ti","pid":"1","severity":"INFO","source":"mcm_manager.go:673"}
2023-02-08 00:06:34 | {"log":"Pod xxx-xxx-xxx-xxx-xx can't be scheduled on shoot--hc-us10--prod-haas-hana-xxl-z1, predicate checking error: node(s) had volume node affinity conflict; predicateName=VolumeBinding; reasons: node(s) had volume node affinity conflict; debugInfo=","pid":"1","severity":"INFO","source":"scale_up.go:300"}
` What you expected to happen: That the autoscaler spins up a u-6tb1.112xlarge machine How to reproduce it (as minimally and precisely as possible): Create a pod that should be scheduled onto a u-6tb1.112xlarge machine and set the minimum of that worker group to 0
Anything else we need to know:
Environment: