By including pre and pos-application functions, charm
series upgrades can be handled in a more generic way,
even when they require running additional actions
before a unit is upgraded, or after the whole application
is upgraded.
Updating each machine in a fully self-contained way makes
it easy to add per-machine and (possibly) per-application
post-upgrade function calls. This still performs the actual
series upgrades fully in parallel but will, for example,
start the do-release-upgrade on one unit while another is
still performing the initial dist-upgrade
As the cinder charm now has Juju storage support, the cinder
tests needs their timeouts extended as Juju storage on serverstack
is MUCH, MUCH slower than ephemeral storage (which is local to the
host).
Add Python 3.8 env in Travis CI test matrix.
At present the pinning of flake8 disallows running of lint on
Python 3.8 systems.
Update flake8 ignore-list to ignore W504 instead of W503, the PEP
guidance is that either is ok, but there must be local consistency.
There are more occurences of binary operator before line-break
than after in this repository, and we have also chosen to ignore
W504 in most of our other repositories.
* kerberos authentication tests
* kerberos authentication setup and test
* kerberos authentication setup and test
* kerberos authentication setup and test
* pep8 corrections
* pep8 corrections
* remove hardcoded code
* add logging
* fix keytab location
* add logging
* add logging and custom exception for kerberos test server errors
* syntax list
* adding empty keytab in setup
* pep8
* Kerberos custom exception
* date
* fix creation of empty file
* logging
* wait until workload is active
* wait until workload is active
* Edit tests for optimal configuration and logging
* remove empty lines
* add logging to tests
* add logging to tests, import subprocess
* tests.py need setup.py get_unit_full_hostname function
* token retrieval test
* add dns to test host as well as keystone
* test keystone token
* user needs to be the one created in the kerberos system (i.e admin)
* openstack token issue to confirm authentication
* openstack token issue to confirm authentication
* pep8
* cmd has to be formatted differently for subprocess call
* fix error
* piping password to the kinit prompt
* add a verification for the cached kerberos token file
* add a verification for the cached kerberos token file
* must wait for subprocess to go through to check result
* change config to run the kerberos client tests on a ubuntu vm
* change config to run the kerberos client tests on a ubuntu vm
* change config to run the kerberos client tests on a ubuntu vm
* install krb5-client on ubuntu test host
* install krb5-client on ubuntu test host
* retrieve openstack token
* stderr is a dict
* adding python-pip and keystoneauth1[kerberos]
* adding python-pip and keystoneauth1[kerberos]
* adding python-pip and keystoneauth1[kerberos]
* add other mandatory packages to test host
* pep8
* unused exception, removing
* revert change
* rename run_all_tests for run_all_configuration_tests
* install the python3 packages
Ubuntu focal ships with rabbitmq server 3.8.2 which has changed the text
output format for the cli commands that the tests rely on. Fortunately,
3.8.2 also adds a --formatter=json option. This patch takes advantage
of that.
When testing with TLS there is a chance the deployment will appear
done and idle prior to ceph-radosgw and Keystone have updated the
service catalog. Retry the test in this circumstance.
A side effect of migrating to bootstrapping Keystone as opposed
to using the admin_token is that the charm credentials is now
subject to the Keystone policy.
At present the ``list_services`` policy is used as a test of the
Policy Override feature, however revoking access to said call
will make the charm go into an error state as it attempts to use
it as part of managing the Keystone CRUD.
Change the test to use the ``list_credentials`` policy for test
instead.
