Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate katib to new test-infra #1423

Merged
merged 7 commits into from
Jan 28, 2021
Merged

Conversation

PatrickXYS
Copy link
Member

What this PR does / why we need it:
Migrate katib to new test-infra

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1422

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

NONE

/cc @andreyvelich
/hold

@PatrickXYS
Copy link
Member Author

 Failed: cannot unmarshall spec: cannot convert int64 to string

Checking

@PatrickXYS
Copy link
Member Author

Same reason, roll back all the changes and see what's going on

@PatrickXYS
Copy link
Member Author

INFO|2021-01-26T21:17:32|/src/kubeflow/testing/py/kubeflow/testing/argo_client.py|48| Parsing ApiException body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"workflows.argoproj.io \"kubeflow-katib-presubmit-e2e-v1beta1-1423-3f174af-3552-0e2b\" not found","reason":"NotFound","details":{"name":"kubeflow-katib-presubmit-e2e-v1beta1-1423-3f174af-3552-0e2b","group":"argoproj.io","kind":"workflows"},"code":404}

After applying workflow, it can't find corresponding workflow.

@PatrickXYS
Copy link
Member Author

/test kubeflow-katib-presubmit

Kick off again to see if the issue happen

@PatrickXYS
Copy link
Member Author

PatrickXYS commented Jan 26, 2021

Same issue... Dig into it to see why it can't apply generated-workflow into remote argo cluster

@PatrickXYS
Copy link
Member Author

PatrickXYS commented Jan 26, 2021

It works this time, looks like those TTL configuration causes the issue

@PatrickXYS
Copy link
Member Author

PatrickXYS commented Jan 26, 2021

Removed ttl parameters since we have already configured default workflow spec:

configmap -o yaml
apiVersion: v1
data:
  workflowDefaults: |
    metadata:
      annotations:
        argo: workflows
    spec:
      ttlStrategy:
        secondsAfterSuccess: 604800
        secondsAfterCompletion: 604800
        secondsAfterFailure: 604800
      activeDeadlineSeconds: 86400
...

https://argoproj.github.io/argo/fields/#ttlstrategy

That's being said, WG does not need to configure ad-hoc activeDeadlineSeconds and ttlStrategy parameters.

/cc @andreyvelich

@andreyvelich
Copy link
Member

https://argoproj.github.io/argo/fields/#ttlstrategy

@PatrickXYS That makes sense.
Should we merge this ?

@@ -179,7 +178,6 @@
spec: {
entrypoint: "e2e",
// Cleanup workflow after 5 days.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove this comment, please?

@PatrickXYS
Copy link
Member Author

https://argoproj.github.io/argo/fields/#ttlstrategy

@PatrickXYS That makes sense.
Should we merge this ?

It's already in, our new Argo cluster installed with v2.12.3 argo workflow

@PatrickXYS
Copy link
Member Author

/unhold

@andreyvelich Can you help approve this PR and get it merged?

Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich, PatrickXYS

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@PatrickXYS
Copy link
Member Author

Looks like you also need to lgtm @andreyvelich

@andreyvelich
Copy link
Member

/lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Test] Migrate to new test-infra
3 participants