Fix paramiko.ssh_exception.BadAuthenticationType when SSHing to a new Ubuntu instance.
Note that paramiko still has a few issues around authentication:
https://github.com/paramiko/paramiko/pull/1106/files
This paramiko PR also shows that password='' isn't the same as
password=None
On a recent mosci run the guest used for a restart test had a
pending power task which stopped the restart test working properly.
This PR adds an assertion that the guest is ready.
wait_for_cacert will wait for keystone to recieve and install
a cacert. This is particularly useful when the certificate
issuer is in a different model.
When vault is in its own model with no clients then vault needs
to be initialised without waiting for clients to start executing
and without validating a client has recieved the cert. To achieve
this, this PR adds auto_initialize_no_validation_no_wait.
Ensure that the CA cert for the deployment is passed to
requests when retrieving stream data from swift.
Refresh the product catalog entry on each attempt to retrieve
stream data as the URL will update once data was been written
to the swift endpoint in the deployment.
Retry on KeyError and drop number of retry attempts
Add a log message to detail URL being used for product-stream data
Log return data from streams endpoint
Fixup endpoint resolution
Since commit c98aa001f9, there are some
missing changes.
This stops the API check on Ocata when gnocchi is in play. Gnocchi must
be in play for Ocata but heretofore has not been.
This is the 3rd change in the effort to deprecate
zaza.openstack.utilities.juju in favour of zaza.utilities.juju.
All functions now just wrap their equivalents in
zaza.utilities.juju and a decorator has been added which logs a
warning if the function is used.
charm-cinder supports units with a limited number of services running
(api/scheduler on a unit, volume service on another one). Functional
tests wait for all services to be restarted when a subset of them should
be observed.
Partial-Bug: #1779310
At present the overcloud CACERT is copied to /tmp and as such it
is not possbile to run multiple tests at once without them
stepping on each other.
Store the copy in a path relative to where the test is executed,
in line with how the SSH keys are stored etc.
Fixes#331
During some runs of functional testing, swift global replication would
only have 2 copies rather than 3 of the object that was just written.
This patch attempts to resolve the race condition and also adds ordering
to more recently added tests.
Closes-Bug: #1882247
David Ames
Aurelien Lourot
Liam Young
Chris MacNaughton
Frode Nordahl
James Page
Alex Kavanagh
Camille Rodriguez
Alvaro Uria
Drew Freiberger
coreycb