You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #457, the e2e tests using the removed .Items field have been migrated to using the .GenericItems field.
That has surfaced an issue for the test that covers the creation of an AppWrapper with a Pod generic resource, and uses .spec.schedulingSpec.minAvailable = 2, described as:
Create AppWrapper - PodTemplate Only - 2 Pods
The other tests, with Pod as generic resource, also fail when .spec.schedulingSpec.minAvailable > 1.
It may be an issue in the way Pod generic resource are handled.
The text was updated successfully, but these errors were encountered:
@astefanutti Thanks for creating the issue, I am trying to understand this issue better. changes to move to GenericItems should not be impacting schedulingSpec field. can you please describe a bit more about the issue that you are facing please?
In #457, the e2e tests using the removed
.Items
field have been migrated to using the.GenericItems
field.That has surfaced an issue for the test that covers the creation of an AppWrapper with a Pod generic resource, and uses
.spec.schedulingSpec.minAvailable = 2
, described as:The other tests, with Pod as generic resource, also fail when
.spec.schedulingSpec.minAvailable > 1
.It may be an issue in the way Pod generic resource are handled.
The text was updated successfully, but these errors were encountered: