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

Tag release failing to build for workflow-helpers but no logs available #57

Closed
pacospace opened this issue Sep 3, 2020 · 5 comments
Closed
Assignees
Labels
human_intervention_required kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@pacospace
Copy link

Describe the bug
I would like to know why build failed

To Reproduce
Steps to reproduce the behavior:

  1. Create git tag in repo and look at Tekton Pipeline Run
  2. Go to logs for build Task

Expected behavior
Build is successful and new image is available on Quay

Screenshots

Additional context

@goern
Copy link
Member

goern commented Sep 3, 2020

/kind bug
/priority critical-urgent

@sesheta sesheta added kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Sep 3, 2020
@goern
Copy link
Member

goern commented Sep 3, 2020

/assign @harshad16

@harshad16
Copy link
Member

harshad16 commented Sep 8, 2020

The issue pipeline failed to build tag for workflow-helper is due to the mis-match of python version, the pipeline was not able to build the python 3.6(stated in Pipfile) based application in python 3.8 image (stated in aicoe-ci.yaml ).
checked in new deployment of ocp cluster: https://console-openshift-console.apps.ocp.prod.psi.redhat.com/k8s/ns/aicoe-infra-prod/tekton.dev~v1alpha1~PipelineRun/tag-release-24hbr/logs
fix for this would be sent in.

Apart from this, I will open a feature, such that when a build fails , an issue is opened. so that it can be investigated and worked upon in future.

@goern
Copy link
Member

goern commented Sep 10, 2020

can we close this @pacospace

@pacospace
Copy link
Author

can we close this @pacospace

Yes thanks!! @harshad16 solved it already! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
human_intervention_required kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

4 participants