Unit tests under py3.12 were generating these errors:
AttributeError: 'NeutronCCContextTest' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
AttributeError: 'called_with' is not a valid assertion
Fixed all test asserts to be valid and correct.
TrivialFix
Change-Id: Ic43731eda5e1617320cf2aa9cf413b45bf982214
Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:
- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords
These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].
I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.
[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html
Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
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: I6ac828e0784ae4466a6e5cbc85acd666c9c2f75c
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: I2cc91999ccad52c8e42797a3d5ffbf65f9cb36d2
The networking-hyperv project is no longer maintained and
has been removed from Ubuntu in Mantic.
Closes-Bug: #2036953
Change-Id: Ib8e861377c9f691f31de0f707823dbf8ac0fde52
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
[1] https://github.com/juju/charm-helpers/pull/824
Closes-Bug: #2028683
Change-Id: Ia03446f08c38057985f895fed2a5cdd78004aec8
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: Idb7ec6357e2ef7449cc77bff48d12102da72d822
* 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: I78b2e454009869b79cb27cfc15712a6b8ef8e286
This change add several configuration options to enable HTTP checks
to the HAProxy configuration, instead of the default TCP connection
checks (which continue to be the default). It also enables /healthcheck
endpoint for neutron-api.
Closes-Bug: #1880610
Change-Id: Ia820d8c2ca709d6b358b1c80d770624568d9a85b
The linked bug shows the install of the charm with openstack-origin set
to zed. This happens because configure_installation_source() causes the
openstack-release package to be installed *before* the zed cloud archive
sources are configured into /etc/apt and an apt update done. This means
that the openstack-release package says "yoga" despite the zed packages
actually being installed.
Then, on the config-changed hook, it sees that the installed version is
showing as yoga and tries to do an upgrade. This fails, as the charm
hasn't yet bootstrapped, and the charm tries to bootstrap after
upgrading the packages.
There's a few bugs here which are exposed, but the tactical fix is to
force the openstack-release to match the installed packages.
Closes-Bug: #1989538
Change-Id: Icaa2303d2dbbcfc883ea1cd44ce0a77af1ef7250
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: I84b915dd3b6896984fab40cdc93a5f0da9040491
* 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: I5b04cd5a9d1dd8d62b129592bf8ae1339e9af58b
- 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
Change-Id: I9e03f8032c4e66586feec2bbf5f07e93b89355cc
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: I0febbbf7da990026b9578a3512c99539eb03bbc0
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I25d6d26f2a4169ddc30d8eeac193d768aa345058
Use the configure_installation_source method from
ch.contrib.openstack.utils instead of add_source since it understands
the various openstack-origin permutations.
Change-Id: I3c0d8392c4b0c68687a36c9455fc7991fda215f1
Closes-Bug: 1928727
Add charm option uplink-status-propagation, which for releases >= stein
will add the ml2 plugin uplink_status_propagation, that enabled ports to
have the propagate_uplink_status attribute to allow instance VF to see the PF
link state change for SR-IOV ports.
Change-Id: I4f1ace630c74363057b0bbdbc759c482125ad015
Closes-Bug: 1949491
* 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: I97d4131670ae024b8bc84d5a13b1034e47d39445
The change [1] syncs the charmhelpers that has additional
context data to IdentityServiceContext - internal_host,
internal_port, internal_protocol.
This patch adds the internal_host, internal_port,
internal_protocol to neutron-plugin-api relation data.
Without this patch, any relations over neutron-plugin-api
will be incomplete if the charm holding the other end of
the relation has charmhelpers synced.
[1] https://review.opendev.org/c/openstack/charm-neutron-api/+/806676
Change-Id: Ic4abbd0a408949c0c752a1701db161e1cd5c4ff7
Add enable-fwaas to neutron-plugin-api relation data so
that neutron-openvswitch updates neutron-l3-agent
configuration accordingly.
Synced charmhelpers to get related changes
https://github.com/juju/charm-helpers/pull/635
Partial-Bug: #1934129
Change-Id: I5019c5ed3b8ab556d4900f1fe46dee69f5f09ee7
Commit 00e7c8b added support for disabling fwaas but
forgot to remove the firewall plugin from service_plugins
once the fwaas package has been removed. This patch fixes
that.
Change-Id: I75fdd192144138fa5bf09c278d5507ca8c5366d1
Closes-Bug: #1934129
Also adds config option enable-fwaas which defaults to
True to allow disabling fwaas for releases earlier than
Victoria.
Change-Id: Ic9251c5290f777f544a150a92702566474b264b8
Closes-Bug: 1934129
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: If5d64191925c5b568c0224c59b0c851e3c8f3e50
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: Ic682234b64c313cc09a6471f30f20dc1a7d49f37
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I4c38f3db7c7bcdbb993ffb27b8bf1473f8f0f3a6
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: I65d1d790f902d928cd0c4dc848121b1c7fd65071
* 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: Ice0f02ee3724b1cf9f59efb59ef8b33e1bf54968