-
Notifications
You must be signed in to change notification settings - Fork 735
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
Example workflow does not get executed #37
Comments
Can you check the |
😞 ... The sensor logs show what the problem is. A secret called "artifacts-minio" is required. I'll create the secret and try to run this...
|
Yea, looks like that may be the problem. |
I used the correct secret and the trigger was able to run without any problems. I'll create a PR for updating the quickstart.md with slightly more detailed instructions. Will close this issue when the PR is merged. |
* Update docs/quickstart.md with more thorough instructions. Closes #37. * Update helm command to install with specific name.
* Update docs/quickstart.md with more thorough instructions. Closes argoproj#37. * Update helm command to install with specific name.
Describe the bug
I tried running the
argo-events
example wherein I expected an Argo workflow to be triggered based on a calendar event of time = 10 seconds. However, the workflow was not executed. More details below (this might just be a problem with my setup or the documentation).To Reproduce
Steps to reproduce the behavior:
3.1. Verified that the minion pod was running correctly.
3.2. Port-forwarded the port 9000 and was able to access the minio web interface.
3.3. Created a bucket called
my-test-bucket
.3.4. Installed the command line client
mc
and copied the hello_world.yaml argo example inside the bucket.4.1. Verified that the argo controller was running.
4.2. Ran a sample workflow using
argo submit
and it completed successfully.Expected behavior
The following behavior was expected after the above:
sensor-controller
will find the new sensor object that got created and run a newsensor-executor
job. This worked correctly and I could see a new Jobsensor-executor
pod do not have much information either.The text was updated successfully, but these errors were encountered: