* Update charm-neutron-gateway from branch 'master'
to 6647baa5e616c35400e8445e1a116470fa48f5b3
- Updates for caracal tox.ini
Update the tox.ini file(s) to use the constraints file from
zaza-openstack-tests.
Change-Id: Ifac3b28fd2773e802a83135e7ff32ca4e8befeaf
* Update charm-neutron-gateway from branch 'master'
to cc421e97194d56fa8881bb9cc8ded9876db1a7a7
- Updates for caracal testing support
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
* Update charm-neutron-gateway from branch 'master'
to 80dab0abd30e49953f5d34fc3779d86806c39076
- Improve platform mocking
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
* Update charm-neutron-gateway from branch 'master'
to 500a8bd029be78558b84fa3a7d1552e82e8970eb
- Fix typo in actions.yaml
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
* Update charm-neutron-gateway from branch 'master'
to dd640651e3c5d7d3fc133ba6bfd3fb6752282a7f
- Add 2023.2 Bobcat support
* sync charm-helpers to classic charms
* change openstack-origin/source default to bobcat
* add mantic to metadata series
* align testing with bobcat
* add new bobcat bundles
* add bobcat bundles to tests.yaml
* add bobcat tests to osci.yaml
* update build-on and run-on bases
* drop kinetic
* update charmcraft_channel to 2.x/stable
Change-Id: I449a35e6ba7783e53fd21231dfa4236fbb31b7ef
* Update charm-neutron-gateway from branch 'master'
to 44f6190ee042f1a8382026750ec9d0c61431de2a
- Add docs key and point at Discourse
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
* Update charm-neutron-gateway from branch 'master'
to 38dabad5c8f462f726fa3d0f782189d872213767
- Merge "Enable jammy-antelope voting and drop kinetic-zed tests"
- Enable jammy-antelope voting and drop kinetic-zed tests
* 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
* Update charm-neutron-gateway from branch 'master'
to b5193940b253092770dce0bf642407fd7422f092
- Fix comparison for Antelope wrap
Use CompareOpenStackReleases to ensure 'antelope' is greater
than 'zed', for example.
Change-Id: I3cf34dbf596c63484ada442c91aa51adab5a7fad
* Update charm-neutron-gateway from branch 'master'
to fabaa8aa22c2aa18f48e2cd6ff5972babf1f21e6
- Drop python-six
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
* Update charm-neutron-gateway from branch 'master'
to f41c45ead51efbe267af319566ad71ce878e2032
- Drop 'source' from mysql-innodb-cluster and rabbitmq-server
Change-Id: Ib468fb79ec5e00102a1a9fc43ab66078e37c1593
* Update charm-neutron-gateway from branch 'master'
to 9e71e6f7323f4ef111b8bc9c7b1766516cc7470c
- Ensure that kinetic/22.10 is enabled
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
* Update charm-neutron-gateway from branch 'master'
to 260449901026fb793b7e9caa91c3fbeead45666c
- Add Kinetic and Zed support
* 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
* Update charm-neutron-gateway from branch 'master'
to c1bfec91b9856d94bdd5e0cb9f5c0a1067f82f82
- Add *.charm to gitignore
This patch adds *.charm to the .gitignore to ensure that any built
artifacts are ignored.
Change-Id: Iaa75568a5d928f62839e130416357caebfcf0747
* Update charm-neutron-gateway from branch 'master'
to 08c823a9b4b522fe5c014a3132fc736d54b67b1c
- Updates to enable jammy and finalise charmcraft builds
- 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
* Update charm-neutron-gateway from branch 'master'
to d373c464501874fdb8eed98d4a9883bfb316019a
- Merge "Update to classic charms to build using charmcraft in CI"
- Update to classic charms to build using charmcraft in CI
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
* Update charm-neutron-gateway from branch 'master'
to f970260fb37936de33b967831f888d5501f28ae8
- Merge "Add ovs-record-hostname to deferable service list"
- Add ovs-record-hostname to deferable service list
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
* Update charm-neutron-gateway from branch 'master'
to cdc744ee2107483c3530a3617933da1c0ba85bcf
- Re-enable gate voting
The yaml.safe_load() fix has landed in zaza-openstack-tests:
https://github.com/openstack-charmers/zaza-openstack-tests/pull/669
Closes-Bug: #1951650
Change-Id: Ibcee29b6644f3b92213b97705b8afdbdb15603b9
* Update charm-neutron-gateway from branch 'master'
to 3b3c0ee32b728fcd853e851c26592dbe6eba7f36
- Add yoga bundles and release-tool syncs
* 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
* Update charm-neutron-gateway from branch 'master'
to d066f337bc52d295552fd193284d26a2fad9e1a8
- Merge "Fix link formatting in README"
- Fix link formatting in README
The examples had headers that got turned into links
in the rendered HTML. This PR should fix that.
Change-Id: Id5515da9872d56308975ec197ca13f5dffe2d18a
* Update charm-neutron-gateway from branch 'master'
to 0f4c7e7aeee82a7c333a9776865450a3b374f2af
- Increase nova-cloud-controller RAM in func tests
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
* Update charm-neutron-gateway from branch 'master'
to 115c34fadd5e640158dc1d7d80bf3de36ccd00f5
- Add AppArmor Rule for keepalived
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
* Update charm-neutron-gateway from branch 'master'
to e69435903213968d2471aca1533e837f7525de40
- Merge "Add extension fwaas_v2 based on neutron-api relation data"
- Add extension fwaas_v2 based on neutron-api relation data
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
* Update charm-neutron-gateway from branch 'master'
to 443ffbde880ee3c29c952dd3dec57310ec11cdf9
- Merge "Replace reference to 'juju set' with 'juju config'."
- Replace reference to 'juju set' with 'juju config'.
Change-Id: I220748339160984ce9b271c0ca9b7789acacba86
* Update charm-neutron-gateway from branch 'master'
to 655860f3c3db74af3b6a64cc46be5f1adc02659f
- Merge "Make fw driver configurable"
- Make fw driver configurable
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
* Update charm-neutron-gateway from branch 'master'
to d29d295c32a0667323a2869a9a0871c6be7c847a
- Add impish to metadata.yaml
Change-Id: I9c3deef7a7cbc1085e72c2b7a25b32c964df6d5c
* Update charm-neutron-gateway from branch 'master'
to 77aa4b6326bf84732b05a717e39e9ee44b71f43a
- Merge "Mention deferred service events in README"
- Mention deferred service events in README
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
* Update charm-neutron-gateway from branch 'master'
to 10707801e6ed3fc8f94ec479f5d8919b768a74ed
- Remove deferred-restart config for lbaasv2
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
* Update charm-neutron-gateway from branch 'master'
to 2e816efe01f6b92cbe51e88735d85282f07e2951
- Merge "Disable vrrp healthchecks by default"
- Disable vrrp healthchecks by default
VRRP healthchecks were enabled by default starting in the 19.07 charm
release for network deployments which utilize l3ha or dvr+snat. The VRRP
healthchecks have specific expectations that may not be satisfied in
various data centers. This leads to problems with networks as failed
healthchecks lead to router failovers.
This change alters the default config option to disable the vrrp
healthchecks by default and require users to opt in to using them. The
description around the option has been updated to indicate that doing so
may lead to routers failing over if ICMP pings are missed.
Closes-Bug: #192101
Change-Id: Ie0ebb8072fa802dc8c2478a0b3ca38202d49c85f
* Update charm-neutron-gateway from branch 'master'
to aff94fe2ed6dd924086eca6a8157b9b570993ebd
- Merge "setup.cfg: Replace dashes with underscores"
- setup.cfg: Replace dashes with underscores
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
* Update charm-neutron-gateway from branch 'master'
to 3394e7178095770546c1c70d84fe4830a17db042
- Test bundles for focal-wallaby and hirsute-wallaby
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
* Update charm-neutron-gateway from branch 'master'
to 2ee597c08fa2d7632a1f1fdda8fc18fa8a2e2848
- Updates to flip all libraries back to master
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I72e3c460571f3e7a64ebb74d1535fb046e4a883f
* Update charm-neutron-gateway from branch 'master'
to 5f33d68f49d92f3bf96082d9dabdd372bbe29b57
- 21.04 sync - add 'hirsute' in UBUNTU_RELEASES
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: I3798a8dc52cd80464481692d821590d367a9bf29
* Update charm-neutron-gateway from branch 'master'
to 9b4888db16570925241e16c6840aacb6f268510b
- Merge "21.04 libraries freeze for charms on master branch"
- 21.04 libraries freeze for charms on master branch
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: I78d24b0e2f4218abaa6c7fd5854319ab9fa6f01a
* Update charm-neutron-gateway from branch 'master'
to 069aa202b9b5e6a07083f189ea0e8aa59537134c
- Update worker-multiplier config description
Based on the change in charm-helpers:
https://github.com/juju/charm-helpers/pull/553
Related-Bug: #1843011
Change-Id: Ia9c6c6787c9798e3a3d4b98f316cc7f2b38af711
* Update charm-neutron-gateway from branch 'master'
to e0a7188b4a7bff843e7a3758e15d08ed85725540
- Improve documentation on data-port functionality
Update docs to clarify that manual removing of previous
values are required if the config changes.
Change-Id: Ia13b5e2a9b38a8a9e4e2d6cb38d308a114c3cbc2
Related-bug: #1915967
* Update charm-neutron-gateway from branch 'master'
to 6c33162da8d9e8f265d92b3580c8e13c9526a86f
- Merge "Add hirsute and remove trusty from metadata.yaml"
- Add hirsute and remove trusty from metadata.yaml
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ice9aa780b2127660decbab8c008ffdc99ae631ba
* Update charm-neutron-gateway from branch 'master'
to 17112e1639db2088f62b308c1cff5345b074f195
- Merge "Add new osci.yaml"
- Add new osci.yaml
This change is preparatory to migration Ubuntu OpenStack CI
from Jenkins to Zuul
Change-Id: I996496c12e189257a27fdb39dd094ccb0a6df929
* Update charm-neutron-gateway from branch 'master'
to b679984b1fec8dce16a3435465e5cfab907906ff
- Add new functional test case for ext-port config option deprecation
Add reference to to the new test case that valdiates whether the charm
goes in blocked state when data-port and ext-port are specified at the
same time.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/523
Signed-off-by: Przemysław Lal <przemyslaw.lal@canonical.com>
Change-Id: I2e1ba8ac4c09ea77c39e0337114f67690de6829c
* Update charm-neutron-gateway from branch 'master'
to 68154a3a9a9ef778195eee537033f22fd8ae5858
- Move _ovs_additional_ids() and sequence_functions() to charmhelpers
Sync charmhelpers.
Replace _ovs_additional_ids() calls with generate_external_ids() from
charmhelpers.
Replace sequence_functions() with sequence_status_check_functions()
from charmhelpers.
This allows to share helper functions between charm-neutron-gateway
and charm-neutron-openvswitch.
Change-Id: I8fc3b5c9e33e539b8b9c1d188acb8c79e8758244
Signed-off-by: Przemysław Lal <przemyslaw.lal@canonical.com>
Alex Kavanagh