An unnecessary podgroup has been created

[zhouzhifeisdcn]

I install lws with parameter：
VERSION=v0.7.0
helm install lws https://github.com/kubernetes-sigs/lws/releases/download/$VERSION/lws-chart-$VERSION.tgz
--namespace lws-system
--create-namespace \
--set gangSchedulingManagement.schedulerProvider=volcano
--wait --timeout 300s

I create a lws.yaml but did not specify the scheduler as Volcano；

kind: LeaderWorkerSet
metadata:
  name: leaderworkerset-multi-template
spec:
  replicas: 1
  leaderWorkerTemplate:
    leaderTemplate:
      spec:
        containers:
        - name: nginx2
          image: nginxinc/nginx-unprivileged:1.27
          resources:
            limits:
              cpu: "100m"
            requests:
              cpu: "50m"
          ports:
          - containerPort: 8080
    size: 4
    workerTemplate:
      spec:
        containers:
        - name: nginx
          image: nginxinc/nginx-unprivileged:1.27
          resources:
            limits:
              cpu: "100m"
            requests:
              cpu: "50m"
          ports:
          - containerPort: 8080

LWS created a podgroup, but the status of the podgroup remains Inqueue; This means that it has never been scheduled by Volcano

[ahg-g]

Has this been released? if so, we should fix this and patch previous releases that included pod group support

[ardaguclu]

Does this happen if you don't set --set gangSchedulingManagement.schedulerProvider=volcano in your helm chart?

[yankay]

I'm trying to reproduce this issue. The PodGroup was also created successfully.

Hi @JesseStutler,

Could you please clarify:

When gangSchedulingManagement.schedulerProvider=volcano is set but schedulerName: volcano is not specified, is it expected behavior for the PodGroup to be created or not?

Is this a bug or an intentional design?

[JesseStutler]

I'm trying to reproduce this issue. The PodGroup was also created successfully.

Hi @JesseStutler,

Could you please clarify:

When gangSchedulingManagement.schedulerProvider=volcano is set but schedulerName: volcano is not specified, is it expected behavior for the PodGroup to be created or not?

Is this a bug or an intentional design?

@zhouzhifeisdcn You should also specify schedulerName in leaderTemplate and workerTemplate
@yankay At first, I didn't pay attention to this aspect and still manually specified the schedulerName. But I think from the perspective of usability, users shouldn't need to specify schedulerName in leaderTemplate and workerTemplate? Just specifying gangSchedulingManagement.schedulerProvider=volcano is enough, WDYT?