please allow pulling core20 base, when asked

Bug #1849687 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Unassigned
launchpad-buildd
Fix Released
High
Unassigned

Bug Description

https://code.launchpad.net/~canonical-foundations/+snap/pc-amd64-20

I have requested, via API, to use Focal distro series, and use edge channel for "core20".

However, the build still fails with "No such base: 'core20'."

Please allow pulling & building snaps against core20. You can limit this to API only access, when building with focal series, and core20 is specified in the auto_build_channels.

https://oops.canonical.com/?oopsid=OOPS-3f9bd0c04a76f380b18009af4755c152

Sorry for two OOPS.

Related branches

description: updated
Colin Watson (cjwatson)
tags: added: lp-snappy
Changed in launchpad-buildd:
importance: Undecided → High
status: New → Triaged
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I see launchpad UI code for "snap_names = ["core", "core18", "snapcraft"]"

And it is missing core16, and I kind of, don't want to expose core20 field there yet, until core20 is more stable.

I'm ok with keeping launchpad UI page as is. Without focal and without core20 field.

Or like maybe roll that out later?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I really don't know about timings to like expose Focal in the UI there. Or like auto select Focal, if one is trying to build "build-base: core20" or "base: core20" snaps.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Thus to fix this ticket for now, i think we only want launchpad-buildd upload & add core20 to the database table.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Ideally I want anything that is core20, to be built in Focal Fossa. But it looks like it's database entries only, rather than in the code.

Changed in launchpad-buildd:
status: Triaged → In Progress
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

So i believe launchpad-buildd bit is done.

Launchpad code is merged, but not yet deployed (last deployment is with like 23rd of October code).

I guess next steps are:
- add the database entries
- deploy launchpad

How do the database entries look like? Is there anything specific that needs doing?

Imho, when UC20 target is selected it should imply "snapcraft from snap" feature flag, install "snapcraft" and "core20" snaps from stable. And core18 will be pulled in as a dependency of snapcraft.

Changed in launchpad-buildd:
status: In Progress → Fix Released
Changed in launchpad:
status: Triaged → Fix Committed
Revision history for this message
Colin Watson (cjwatson) wrote :

A deployment is in progress at the moment.

I will deal with the new SnapBase row. However, I don't think it can currently imply installing the core20 snap from stable, since there is currently no revision of core20 in stable. For now it will probably have to imply core20 from edge, which we can change once it gets promoted.

Revision history for this message
Colin Watson (cjwatson) wrote :

Deployed now, and I've created the SnapBase row:

$ curl -s https://api.launchpad.net/devel/+snap-bases/core20 | jq -S
{
  "build_channels": {
    "core20": "edge",
    "snapcraft": "stable/launchpad-buildd"
  },
  "date_created": "2019-11-08T14:41:41.812648+00:00",
  "display_name": "core20",
  "distro_series_link": "https://api.launchpad.net/devel/ubuntu/focal",
  "http_etag": "\"7f401b6b43cb44869f0752d1d6a08d8b75800f4d-214b8fd2a1f9e0dda1da4c28400d22044d5fc54b\"",
  "is_default": false,
  "name": "core20",
  "registrant_link": "https://api.launchpad.net/devel/~cjwatson",
  "resource_type_link": "https://api.launchpad.net/devel/#snap_base",
  "self_link": "https://api.launchpad.net/devel/+snap-bases/core20",
  "web_link": "https://launchpad.net/+snap-bases/core20"
}

Changed in launchpad:
status: Fix Committed → Fix Released
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.