Now that "snapd" snap is seeded into the base image of focal along with
core18 for "lxd" snap . That actually solves the original issue in a
different way. We no longer have to upload "snapd" snap using a charm
resource.
Bionic is still affected, but I don't think it's common for new
deployments
** Summary changed:
- snap installation with core18 fails at 'Ensure prerequisites for "etcd" are
available' in air-gapped environments as snapd always requires core(16)
+ snap installation with core18 fails at 'Ensure prerequisites for "etcd" are
available' in air-gapped environments as snapd
I'm marking the snapd task as invalid as it seems to be a problem with
the set of snaps available in offline mode.
** Changed in: snapd
Status: New => Invalid
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
I'm not sure there was a fix or anything, the original message was:
> $ sudo snap install ./etcd_230.snap
> error: cannot perform the following tasks:
> - Ensure prerequisites for "etcd" are available (cannot install system snap
> "snapd": Post https://api.snapcraft.io/v2/snaps/refresh: dial
> On top of the already existing snaps, can you also download the snapd snap
> and ack its assertion?
>
> So the command sequence looks like this:
>
> snap download snapd
> snap download core18
> snap download etcd
>
> # on the host
> snap ack ./snapd_*.assert
> snap ack ./core18_*.assert
>
On top of the already existing snaps, can you also download the snapd
snap and ack its assertion?
So the command sequence looks like this:
snap download snapd
snap download core18
snap download etcd
# on the host
snap ack ./snapd_*.assert
snap ack ./core18_*.assert
snap ack ./etcd_*.assert
sudo
** Summary changed:
- snap installation with core18 fails at 'Ensure prerequisites for "etcd" are
available' in air-gapped environments
+ snap installation with core18 fails at 'Ensure prerequisites for "etcd" are
available' in air-gapped environments as snapd always requires core(16)
--
You
Hi,
> In this environment, can you show all of the places that snapd could be
> re-execing to?
The assumption here is that the unit is deployed by Juju and based on a
cloud image instead of a standard desktop or server image. Thus, there
is no core snap available out of the box.
> What is the
apport information
** Tags added: apport-collected bionic uec-images
** Description changed:
Simpler reproducer:
$ snap version
snap2.42.1+18.04
snapd 2.42.1+18.04
series 16
ubuntu 18.04
kernel 4.15.0-91-generic
$ snap info --verbose etcd | grep base:
base:
In this environment, can you show all of the places that snapd could be
re-execing to? What is the output of
```
snap list core
snap list snapd
apt show snapd
apt show snapd 2>/dev/null | grep Version:
snap version
```
and also
```
snap list
```
** Changed in: snapd
Status: New =>
snap ack vs --dangerous doesn't make a difference in this case I
believe.
$ snap download etcd
$ snap download core18
$ sudo iptables -A OUTPUT -p tcp --destination-port 80 -j REJECT --reject-with
tcp-reset
$ sudo iptables -A OUTPUT -p tcp --destination-port 443 -j REJECT --reject-with
Dear reporter, please check if:
snap download etcd
snap download core18
snap ack *.assert
snap install ./core18_*.snap
snap install ./etcd_*.snap
fixes the problem for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think that you will find that using `snap ack...` is the right thing
to do. I didn't test this manually but the use of `--dangerous` creates
quite a different environment than without it.
** Changed in: snapd
Status: New => Incomplete
--
You received this bug notification because you
** Changed in: charm-etcd
Importance: Undecided => Medium
** Changed in: charm-etcd
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891259
Title:
snap installation
Unsubscribing ~field-high for the time being. I've been told that Air-gapped
mode of Snap Store Proxy which is in a closed internal beta currently might be
a better solution in the long term so I will try it out.
https://docs.ubuntu.com/snap-store-proxy/en/airgap
--
You received this bug
In terms of the etcd snap, the bump of the base image happened around April
according to the git history:
https://github.com/juju-solutions/etcd-snaps/commit/3fa8df6aaacb32add9fb40ac297894765f6b0746#diff-5fde7a6d86053f0e1d88c0a2a238941f
It's not a regression strictly speaking, but the bump seems
Subscribing ~field-high.
This is breaking a document behavior around the local resource upload
through the charm and it affects both OpenStack and Kubernetes
deployments with the air-gapped requirement because of Vault's
dependency.
A quick and dirty workaround is to copy the core snap into the
17 matches
Mail list logo
