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

[Configuration help]: artifact not available when running pipelines using a contributor profile #1145

Open
doubleimp opened this issue Nov 12, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@doubleimp
Copy link

Bug Description

Dear All,

I deployed charmed kubeflow (microk8s=1.29/stable, bundle charmed kubeflow, juju 3.4 ) on a local cluster.
I created a few users and a shared namespace using "automatic profile creation" and added all the other users as contributors .
When running pipelines using a contributor profile, I'm getting an error when trying to access the artifact link provided by the dashboard "Failed to get object in bucket: S3Error: The request signature we calculated does not match the signature you provided. Check your key and signing method."
image
Whereas the same operation works when running the pipeline using profile owner.

Thanks for the support

To Reproduce

  1. create two users in kubeflow ("my-user1", "my-user2") "automatic profile creation"
  2. add the "my-user1" as contributor to "my-user2"
  3. From the dashboard select the "my-user2" namespace
  4. In a notebook run

from kfp.dsl import Output,Artifact,Markdown

@dsl.component
def publishartifact(mk_artifact: Output[Markdown]):
markdown='Hello word'
with open(mk_artifact.path, 'w') as f:
f.write(markdown)
from kfp import dsl
from kfp import compiler

@dsl.pipeline
def test_pipeline():
publishartifact()

import kfp
client = kfp.Client()
run = client.create_run_from_pipeline_func(test_pipeline, enable_caching=False)

verify that even if the pipeline is successfully completed the link to download the artifact is not providing the error "Failed to get object in bucket: S3Error: The request signature we calculated does not match the signature you provided. Check your key and signing method".

Environment

juju run locally

Relevant Log Output

no log available for this issue

Additional Context

No response

@doubleimp doubleimp added the bug Something isn't working label Nov 12, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6538.

This message was autogenerated

@doubleimp doubleimp changed the title [Configuration help]: Configure properly shared namespace [Configuration help]: artifact not available when running pipelines using a contributor profile Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant