OCI: Can't delete OCI recipe (internal error)

Bug #1899078 reported by Sergio Durigan Junior
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Thiago F. Pappacena

Bug Description

Take this OCI recipe as an example:

https://launchpad.net/~canonical-server/ubuntu-server-lma/+oci/telegraf/+recipe/telegraf

When I try to delete it, I receive one of those "Oops!" pages from Launchpad. Here's the Error ID:

(Error ID: OOPS-1f96455f1d2f08b0cae3164d278fadbc)

Possible useful info:

- I was not the person who created the recipe.

- The recipe is owned by a team (Canonical Server Team) which I am part of.

Let me know if you need more info and I'll be happy to help!

Tags: oci trivial

Related branches

Revision history for this message
Thiago F. Pappacena (pappacena) wrote :

From the error message, it seems that recipe removal is not deleting its push rules. It should be an easy fix.

Sergio, as a workaround, can you try to remove the push rules from that recipe and deleting it again?

Changed in launchpad:
importance: Undecided → Critical
status: New → Triaged
tags: added: oci trivial
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote : Re: [Bug 1899078] Re: OCI: Can't delete OCI recipe (internal error)

On Thursday, October 08 2020, Thiago F. Pappacena wrote:

>>From the error message, it seems that recipe removal is not deleting its
> push rules. It should be an easy fix.
>
> Sergio, as a workaround, can you try to remove the push rules from that
> recipe and deleting it again?

Hi Thiago,

Hm, I was able to modify the existing recipe and do what I needed
earlier, so now it's "in production". I can try creating a dummy
recipe, setting up a push rule for it, and then see if deleting it
works.

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

I mean, if the bug happens because there's a push rule associated with the recipe, then obviously my attempt will fail :-). What I meant to say is that I can try to see if it *fails*, and then check if it works when I delete the push rule. Would you like me to do this?

Revision history for this message
Thiago F. Pappacena (pappacena) wrote :

Hi, Sergio!

I was just trying to unblock you from doing whatever you needed to do. If you already managed to work out a way, it's fine for me.

The bug itself seems to be easily reproducible in my dev environment. I'm already proposing a fix for that.

Thanks for your help!

Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

On Friday, October 09 2020, Thiago F. Pappacena wrote:

> Hi, Sergio!
>
> I was just trying to unblock you from doing whatever you needed to do.
> If you already managed to work out a way, it's fine for me.
>
> The bug itself seems to be easily reproducible in my dev environment.
> I'm already proposing a fix for that.
>
> Thanks for your help!

Ah, great! Thanks for the quick fix! :-)

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14

Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson)
Changed in launchpad:
status: Fix Committed → Fix Released
assignee: nobody → Thiago F. Pappacena (pappacena)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.