Upgrade pipeline-visualization-service to 0.1.31

[enriquedacostacambio]

Which issue is resolved by this Pull Request:
Resolves kubeflow/pipelines#2806

Description of your changes:
Upgrades pipeline-visualization-service from 0.1.27 to 0.1.31 to match api-server which is at 0.1.31 and is not longer compatible with the older visualization service due to the change in the parameters format introduced by kubeflow/pipelines#1951

Checklist:

• Unit tests have been rebuilt:
  1. cd manifests/tests
  2. make generate-changed-only
  3. make test

---

This change is 

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign yanniszark
You can assign the PR to them by writing /assign @yanniszark in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @enriquedacostacambio. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[enriquedacostacambio]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[ajchili]

/ok-to-test
/assign @IronPan
Hey @IronPan, there appears to be a version mismatch with the visualization server in our manifests file, this should resolve the issue. As an FYI I have not tested this yet but plan to once I get my cluster setup properly.

[ajchili]

/lgtm

[IronPan]

/lgtm

[enriquedacostacambio]

/retest

[k8s-ci-robot]

@enriquedacostacambio: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
kubeflow-manifests-presubmit	a3ced1b	link	/test kubeflow-manifests-presubmit

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[ajchili]

@IronPan are you able to access the tests logs for the failed test? Specifically gs://kubernetes-jenkins/pr-logs/pull/kubeflow_manifests/709/kubeflow-manifests-presubmit/1219725160030932992/build-log.txt as seen on line 228 in the logs.

[ajchili]

The logs only show the same error as the presubmit test.

[ajchili]

@enriquedacostacambio it looks like the make generate-changed-only and make test commands did not work if you ran them. Can you confirm that they ran successfully? If you run into issues I can submit a PR for this with the tests ran.

[ajchili]

make generate-changed-only and make test not run. Please run them so that the unit tests are updated accordingly.

[enriquedacostacambio]

sorry for the very late reply. i see you already created a new pr, should i close this pr? or do you want me to fix the tests?

[ajchili]

Hey @enriquedacostacambio, no problem. This was actually resolved by #802. You can just close this PR.

[enriquedacostacambio]

thanks! closed