Offline installation method needs core18 resource endpoint
Bug #2012217 reported by
DUFOUR Olivier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL InnoDB Cluster Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
The charm mysql-innodb-
However the snap itself has a base dependency with core18.
As it is right now, there is no way to install core18 snap through the charm and the installation will automatically fail on offline deployments.
The current workaround is to install manually core18 snap on the units and wait for the charm to re-attempt the installation hook.
Revision history for this message
| Billy Olsen (billy-olsen) wrote | #1 |
| Changed in charm-mysql-innodb-cluster: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
Probably should be using the snap proxy. Attaching core resources would be complicated and I don't think this is the right direction to go in. Juju needs to grow the capability of using snaps as resources the same as containers. Even then, the official way to do this will likely to be using the snap proxy (https:/
Note, I’m marking triaged/wishlist for now, but this very likely will become won’t fix.