Builds stuck / restarted on Preparing build node

[Michał Sochoń]

Hey.

Looks like I can not get builds to be executed forabout 2 days now, the logs say:

 Preparing build node

 Unpacking build package

 Preparing build node

 Unpacking build package

 Preparing build node

 Unpacking build package

... and it is in 'building' phase for 14h now.

Example build:
https://quay.io/repository/kaszpir/python-json-via-jinja2-render/build/50ddace6-3caa-457b-ba28-730b5f9ba0d3

If someone could look into this, thanks in advance!

[William Dettelback]

Hi Michal- thanks for reporting- we’ll take a look at it this morning!

Bill Dettelback

He/Him

Sr. Engineering Manager, Quay / OpenShift Registry

Red Hat 

--
You received this message because you are subscribed to the Google Groups "quay-sig" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quay-sig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quay-sig/e63dc04c-253b-4097-98dd-0d5aa7463b83n%40googlegroups.com.

[Sunanda Dadi]

Hi Michal,

Can you try triggering the build manually? You should be able to do that on the repository page and under the Builds tab.

[Michał Sochoń]

Unfortunately multiple tries to trigger always ends with 'Unable to start build trigger' - with an already existing old build running, also I stopped running build and tried again, to different branches, and the issue persists.

What's interesting the run trigger when allows to specify branch, then drop-down menu shows only 'master' branch, which is nonexistent in the repo.

But build is triggered if  new branch is created in remote origin - https://quay.io/repository/kaszpir/python-json-via-jinja2-render/build/86822019-3fa8-4272-8873-80d03bfa504c

You received this message because you are subscribed to a topic in the Google Groups "quay-sig" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/quay-sig/Fa0eIZjFkP8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to quay-sig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quay-sig/fb8f6c4e-74c4-4409-bc5b-3470bd3c3f85n%40googlegroups.com.

--

Michal Sochoń
alias _KaszpiR_ kas...@gmail.com

[Sunanda Dadi]

How did you set up the build trigger?
Can you stop any of your existing builds and create a new build trigger using the GitHub Repository Push option?

[Michał Sochoń]

Build trigger was set up something about 2 years ago using quay.io web ui (manually adding repo to build from).
After looking at some repos and github repo configs looks like lot of deployment keys were removed, thus it causes quay.io builds to fail.

I believe there should be a better message why build fails (because of incorrect deployment key) - while right now there is nothing in the UI that shows that issue, the job is just retried and sometimes triggers are disabled if they fail too often.

I've disabled old trigger and added new trigger (which also added new deployment key to github repo), and looks like it works now.
Thanks for help.

[Sunanda Dadi]

Hi Michal,

Glad to hear that creating a new trigger worked. We’ll re-visit propagating error messages on builds.