Update of chroots of Copr Project owned by Packit rises an error

[lachmanfrantisek]

If someone creates the PR with a set of chroots and change it later on, there is a permission problem.

See this example: RedHat-SP-Security/keylime-tests#13 (comment)

[mfocko]

It's not, the issue you cannot update targets while there is a running build (for that target you want to remove? ← might not be true)

[lachmanfrantisek]

@mfocko what can we do here?

• Check for the real cause (Copr update can fail not only because of the permission error #1118 ) and provide a better comment.
• Retrigger or suggest to retrigger once the build is finished. Or, can we cancel the build?

[mfocko]

• Retrigger or suggest to retrigger once the build is finished. Or, can we cancel the build?

that's probably related to an even older issue #5

anyways, canceling build sounds like the most ideal solution, but we can only fix it on our side, if user specifies Copr repository, they can build from multiple repos / branches there

[lachmanfrantisek]

So, let's start with getting a better comment. The situation is not so common and asking for some human interaction looks ok to me in this case.

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[TomasTomecek]

We now produce a better error message: #1397

Since this is a limitation of Copr, I'm not sure if there is anything we can do our side. We could possibly cancel the build or work with Copr to implement this on their side.

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[TomasTomecek]

Is this still a problem?