These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal. They do NOT lock the charms
down, and don't change the testing branches to stable branches.
Change-Id: I121370811bec483cb026559cbd4b759d54f10c23
Patch out charmhelpers.osplatform.get_platform() and
charmhelpers.core.host.lsb_release() globally in the unit tests to
insulate the unit tests from the platform that the unit tests are being
run on.
Change-Id: I3dd34ddb38141ec89896b1ce2d9dc6849f4faaa8
There was a typo in actions.yaml for the resume action that was breaking
builds. This change fixes that typo. The charm will build.
Closes-Bug: 2030677
Change-Id: I8c63674a9d0af597da139abf67ba929d39614311
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: I4ab7cd110208816df38c5c70736b69930bcfc086
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
Change-Id: I73f8f0d538701779ad570bc7565982a6b7e4f7af
This charm doesn't need to support python 2.x anymore, and python-six
was dropped from the Ubuntu Archive on Kinetic (22.10)
Change-Id: Ibd7d373305b608ff0349986d17ecba7f9dfaeb3c
Closes-Bug: #1995285
This patch adds kinetic to the metadata.yaml and ensures
that a run-on base for 22.10 is added in the
charmcraft.yaml
Change-Id: I23408279d74aa33ba384e9bdff264248b1dad2ca
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: Ida68ffdab34c3136f3acf98629e4be6fda3bcea2
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
- charmhelpers sync
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/747
Change-Id: I8bd5e6f5d002fbd1118f2c7fa54e50f1b31fc722
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: Iee7fb24e06d23b3fbf35f05e7931dbdc25b37d64
The ovs-record-hostname service was introduced in the openvswitch SRU
for bug #1915829, however this service did not make the deferable
services list for the neutron-gateway charm. This causes package
upgrades to restart the openvswitch-switch service. Add the
ovs-record-hostname to the deferable services list in order to prevent
unintended restarts of openvswitch-switch.
Closes-Bug: #1955498
Change-Id: I24a32f6f5a5c51b8b8ee62f88a973a126106fcd9
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: Id4a36b0f41d2644a94d266ca1990a270e4e7452f
Recent test run(s) have shown memory exhaustion on the nova
cloud controller units. This exhibits itself as the controller
dropping messages from the compute nodes and logging messages like:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oslo_service/threadgroup.py", line 268, in _perform_action_on_threads
File "/usr/lib/python3/dist-packages/oslo_service/threadgroup.py", line 342, in <lambda>
lambda x: x.wait(),
File "/usr/lib/python3/dist-packages/oslo_service/threadgroup.py", line 61, in wait
return self.thread.wait()
File "/usr/lib/python3/dist-packages/eventlet/greenthread.py", line 180, in wait
return self._exit_event.wait()
File "/usr/lib/python3/dist-packages/eventlet/event.py", line 125, in wait
result = hub.switch()
File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 298, in switch
return self.greenlet.switch()
File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 350, in run
self.wait(sleep_time)
File "/usr/lib/python3/dist-packages/eventlet/hubs/poll.py", line 80, in wait
presult = self.do_poll(seconds)
File "/usr/lib/python3/dist-packages/eventlet/hubs/epolls.py", line 31, in do_poll
return self.poll.poll(seconds)
MemoryError
to the nova-conductor log.
It seems very likely this issue is specific to Bionic Stein so it
may be a little wasteful to have increased the memory allocation
for all the bundles but I think consistancy between the bundles is
more important.
Change-Id: I2d45acadcd221786513c49256f087114a985e74f
A patch was introduced [0] "..which sets the backup gateway
device link down by default. When the VRRP sets the master state in
one host, the L3 agent state change procedure will
do link up action for the gate$way device.".
This change causes an issue when using keepalived 2.X (focal+) which
is fixed by patch [1] which adds a new 'no_track' option to all VIPs
and routes in keepalived's config file.
Patch [1] which fixed keepalived 2.X broke keepalived 1.X (<focal).
So patch [2] was added which adds a keepalived_use_no_track config
option which is set to True control whether the 'no_track' option
is added to the keepalived config.
Finally, patchset [3] introduces automatic detection of the
keepalived version by adding a call to `keepalived --version`
but this is denied by the packages apparmor rules.
[0] https://review.opendev.org/c/openstack/neutron/+/707406
[1] https://review.opendev.org/c/openstack/neutron/+/721799
[2] https://review.opendev.org/c/openstack/neutron/+/745641
[3] https://review.opendev.org/c/openstack/neutron/+/757620
Change-Id: I3eb1ef3fe29a8c4e5e26953844f303c8e985248a
fwaas_v2 extension is added in l3_agent.ini by default from stein.
However with the newly introduced neutron-api configuration parameter
enable-fwaas, the extension have to added only when it is set to true
on neutron-api charm.
neutron-api charm adds enabled-fwaas as relation data in the commit
https://review.opendev.org/c/openstack/charm-neutron-api/+/806676.
This patch removes special handling of fwaas_v2 as l3_extension_plugins
is already updated in relation data based on neutron-api enable-fwaas
configuration.
Remove python3-neutron-fwaas in package list from stein release. The
package is already part of dependency of neutron-l3-agent until Ussuri
release and the dependency will be removed from Victoria release in
package control files.
Synced charmhelpers to get related changes
https://github.com/juju/charm-helpers/pull/635
Partial-Bug: #1934129
Change-Id: I07db7fb7c2f00eaf4c0a5bcc082c73922b87d1c0
The examples had headers that got turned into links
in the rendered HTML. This PR should fix that.
Change-Id: Id5515da9872d56308975ec197ca13f5dffe2d18a
The neutron-gateway uses the firewall driver just as other nodes
do when running neutron-openvswitch-agent. It is currently
hardcoded to the deprecated iptables_hybrid driver. This patch
allows the driver to be changed to openvswitch same as with the
neutron-openvswitch driver with a firewall-driver config option
that defaults to iptables_hybrid so as to maintain backwards
compatibility.
Change-Id: I4f5482425c91b5ad556c384abba7c27137c1948f
When uninstalling the neutron lbaasv2 package remove the policyrcd
configuration for the service first. This allows dpkg to stop
the service.
Change-Id: Ib0ae0c2c66324edf018ba2fbd10ab4f27ef7f16a
Closes-Bug: 1931655
This is a boilerplate section that will eventually
be added to the README for every charm that supports
the deferred restart feature.
Change-Id: I1226ee0039cca11dd8c341e0f511de125ae8c633
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Libraries sync.
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I26d558bc7f1847459a1d510c887a3128637a10ce
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I76232b791b7b4c64e903696dd2903d9196af5eb4