The related bug was caused because the charm did not detect when
the lxc storage had already been set up using the `lxc storage`
command which is used in the 3.x series, rather than the old way
with the 2.x series.
Also fixes issue on xenial where linux-image-extra-* has been renamed to
linux-modules-extra-* from from -4.4.0-145-generic onwards. Otherwise,
the install fails on xenial.
Change-Id: If8bdad6f5641ee21fc7860dceeb4c3facbaecc76
Closes-Bug: #1825393
The pre-install operations may fail, yet that failure is not
elevated to the user. This masks the failure and makes early
package install issues difficult to troubleshoot.
If the basic pre-install script fails, the charm should not
proceed to later hooks as the requirements may not be met.
Hashbangs for bash should specify -e (errexit) on all of the
pre-install bash scripts.
Change-Id: I6178e2cb6665b7a4bdbe66a63b29616067932352
Closes-bug: #1815243
Partial-bug: #1815231
Add a tactical change which is already merged into charm-helpers.
This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.
Reference:
4835c6c167
Change-Id: I6e3ef7a281c853a04a090b931562e8389d7b655f
This review is modified to include a patch to resolve bug #1793137
which is due to a bug in nova-lxd where the wrong pool name (lxd) is
used with zfs if lxd is new enough that the storage.zfs_pool_name key
is missing from the config. This is the case on bionic and snap
installed lxd.
Closes-Bug: #1713807
Related-Bug: #1793137
Change-Id: I1123d9882bdb00e9183424b363fc3d1ff25f2346
The criu package doesn't exist for arm64/s390x prior to artful,
causing an install hook failure. Let's not attempt to install
it when that is the case.
Change-Id: If0cc517d9e607604e427aab385fabd8a9a193fdf
Closes-Bug: #1748235
Previously this charm had relied on python-apt being installed by
the principle. As charms migrate to py3 this is no longer a safe
assumption and actually never was. This change ensures that
python-apt is installed before immediatly. This follows the same
pattern
Change-Id: I21ca95a9f2e410a52a7b64c99fad85749d52473a
We need to continue with the previous style of managing storage
until zesty or a specified -updates channel LXD
This additionally reinforces our suggested deployment with ZFS
for a deployment, rather than using LVM as the defualt in
testing.
Closes-Bug: 1676742
Related-Bug: 1573681
Depends-On: I5c38766c4be66d63ef4a07eccc780fcab5973d49
Change-Id: I3ddbd11382c34ff9200e721fa3c90fe67bdce534
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
Change-Id: I9176ea3be01146b18888266ba53a9d37439ea492
Related-Bug: #1659575
Ensure that calls to setup live migration are not made if
the charm is running from inside a LXD container, as the
calls will fail (config needs to be done on the host, not
from within the container).
Change-Id: I1633ba0ef5030b4d170bcea9d0c90a781863b168
Closes-Bug: 1633633
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
Change-Id: I3cbc8f411dc9a4cfa6187be280dc2c43be64b611
Currently, providing a list of devices in config will lead
to an exception, despite the readme calling that out as an
option. Instead, we will now log a message and continue
with the behavious documented in the readme.
Change-Id: Ib5a1d1a0257227e829e433bc61f64ad4cba8052e
Closes-Bug: 1673277
To support use of distinct subuid/subgid ranges per LXD container,
the default range for the root user must be increased to support
> 1 running container in this configuration.
Increase subuid/subgid range to support 5000 containers with distinct
ranges. Restart LXD daemon if idmap configuration changes, to ensure
that the full range of subid's are used.
Change-Id: I8b87dad736abaffdbd7afac090429790d3b03c96
Closes-Bug: 1648056
Its not possible to enable usernamespace ext4 mounting when LXD
is being run from inside a container; leverage charm-helpers
is_container function to guard writes to the /sys filesystem.
Change-Id: Ie479dcf45cb4834308a055dde22d919830c60671
Closes-Bug: 1635659
/sys is read-only when using an LXD contianer due
to lxcfs. So detect if we are running the charm inside
a container and prevent ext4 userns from being
configured.
Closes-Bug: #1635659
Change-Id: Ia0668ea473ec1e80dd8b0a1136061a430883b0ec
Signed-off-by: Chuck Short <chuck.short@canonical.com>
- Remove Precise-Icehouse Amulet test definitions if they exist.
- Add Xenial-Newton Amulet test definitions.
- Add Yakkety-Newton Amulet test definitions.
- Use the percona-cluster charm in tests instead of the mysql charm.
Change-Id: I45e7fd67a0d1eed5f5279ff45e351c513229726e
By default, LXD won't allow an unpriviledged container
to format and mount a block device, so although a block
device can be passed to a container, its not possible
to use it from inside the container.
Add a configuration flag to turn on support for use of
ext4 within user namespaces, allow unpriviledged LXD
containers to format and mount ext4 formatted block
devices from inside of the container.
Change-Id: I8eace1e7b7d4db14a3dc9f82080ac1b0ca29e892
Juju 2.0 provides support for display of the version of
an application deployed by a charm in juju status.
Insert the application_version_set function into the
existing assess_status function - this gets called after
all hook executions, and periodically after that, so any
changes in package versions due to normal system updates
will also be reflected in the status output.
This review also includes a resync of charm-helpers to
pickup hookenv support for this feature.
Change-Id: Iecfdb372e21d1e23cefaa5f972008fc34d65b143
The charm-helpers project have re-licensed to Apache 2.0
inline with the agreed licensing approach to intefaces,
layers and charms generally.
Resync helpers to bring charmhelpers inline with charm
codebase.
Change-Id: Idf85c8e79caa47182e858c6a840f714a4c371806
All contributions to this charm where made under Canonical
copyright; switch to Apache-2.0 license as agreed so we
can move forward with official project status.
Change-Id: I2ae8c26a2a486ac39ee386d2c0ff96ef186edf86
CRIU needs to load the netlink_diag kernel modules
in order for live-migration to work.
In xenial the kernel module is located in
linux-image-extra-`uname -r` debian package.
However in yakkety and newer kernels its found
in the regular linux kernel package.
So install the needed debian packages and modprobe
the module.
Change-Id: Ic2863472bb65507e4f033926b92c70a22a6724da
Signed-off-by: Chuck Short <chuck.short@canonical.com>
All OpenStack charms are now directly published to the charm store
on landing; switch Amulet helper to resolve charms using the
charm store rather than bzr branches, removing the lag between
charm changes landing and being available for other charms to
use for testing.
This is also important for new layered charms where the charm must
be build and published prior to being consumable.
Change-Id: I1bcb20ab061fa639cc1116d2fe0bbf4c5a4464bc
Signed-off-by: Chuck Short <chuck.short@canonical.com>
Avoid use of 'service --status-all' which is currently
broken on trusty for upstart managed daemons; the change
moves to detecting how the daemon is managed, and then
using upstart status XXX or the return code of service XXX
status to determine whether a process is running.
Fixes for IPv6 network address detection under Ubuntu
16.04 which changes the output format of the ip commands
slightly.
Update the version map to include 8.1.x as a Neutron
version for Mitaka.
Change-Id: I3290a1e2f3886e02f606002612c83750cfd6de20
Closes-Bug: 1581171
Closes-Bug: 1581598
Closes-Bug: 1580674
Alex Kavanagh