System test fixes #1565
Open
System test fixes #1565
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding deleting unknown resources feature.
The agent list contains the old "UPGRADED"/"STOPPED" agent, and a new "STARTED" agent. Only assert on the new one.
Co-authored-by: glukhman <[email protected]>
Co-authored-by: glukhman <[email protected]>
Co-authored-by: glukhman <[email protected]>
Co-authored-by: glukhman <[email protected]>
Currently, separate external certs are only supported when public_ip is a domain name, not an ip, and these tests always provide ips. This is because both internal and external listen on 443, and SNI only works for domain names, not ips.
* Update most of the blueprints to DSL 1.5 * Update AWS infrastructure blueprints: use cloudify/types/types.yaml
* RND-895 Proxy 443 port along 53333 in test_agent_via_proxy * Revert "Upgrade blueprints to DSL version 1.5 (#1549)" This reverts commit e60703c. This is a temporary solution before we decide what to do about incompatibility of the Cloudify Manager used in system tests: https://cloudifysource.atlassian.net/browse/RND-896
* RD-6678 Add external db upgrade test
Co-authored-by: glukhman <[email protected]>
* RND-901 Download new rest cert: re-establish the http session Close the session after fetching the cert, so that next request re-loads the cert, instead of using the old cert and throwing an error. Alternatively, we could just send a dummy request, that would fail with a SSLError - that also causes a reload, so the next request would pass. But that would be silly :) * delete_deployment: exit fast if already done If there's no deployments at all, we're done, we don't need to do the 40 iterations then :P
Fixes at least one test: cosmo_tester/test_suites/auth/test_saml.py::test_saml_auth
Co-authored-by: glukhman <[email protected]>
This solves the issue of teardown process not being able to restore rsync-ed backups in environment with less lax umask settings.
Co-authored-by: glukhman <[email protected]>
Co-authored-by: glukhman <[email protected]>
Co-authored-by: glukhman <[email protected]>
glukhman
force-pushed
the
System-test-fixes
branch
from
f13b69b to
a0476a3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Small error fixes towards the 7.0.2 release