-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make ansible-ee-tests-latest globally non-voting and ansible-ee-tests-stable-2.12 non voting for amazon.aws #1498
Merged
softwarefactory-project-zuul
merged 1 commit into
ansible:master
from
tremble:non_voting
Apr 20, 2022
Merged
Make ansible-ee-tests-latest globally non-voting and ansible-ee-tests-stable-2.12 non voting for amazon.aws #1498
softwarefactory-project-zuul
merged 1 commit into
ansible:master
from
tremble:non_voting
Apr 20, 2022
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
…-stable-2.12 non voting for amazon.aws
This was referenced Apr 20, 2022
Build succeeded.
|
Build succeeded (gate pipeline).
|
softwarefactory-project-zuul bot
pushed a commit
to ansible-collections/amazon.aws
that referenced
this pull request
Apr 21, 2022
…ossible) (#775) In integration tests use a common AMI rather than hard coded per test Depends-On: ansible/ansible-zuul-jobs#1498 SUMMARY Rather than hard coding the AMIs on a per-test basis, use a common AMI defined in setup_ec2_facts ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_spot_instance elb_classic_lb ADDITIONAL INFORMATION This doesn't touch the ec2_ami integration tests as this would be something of a circular dependency Reviewed-by: Alina Buzachis <None> Reviewed-by: Jill R <None>
softwarefactory-project-zuul bot
pushed a commit
to ansible-collections/amazon.aws
that referenced
this pull request
Apr 21, 2022
[PR #427 backport][stable-1.5] ec2_key : Fix tests Depends-On: ansible/ansible-zuul-jobs#1498 This is a backport of PR #427 as merged into main (963a829). SUMMARY The Zuul nodes don't have OpenSSL installed on them, this breaks the generation of the fingerprints ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_key ADDITIONAL INFORMATION https://dashboard.zuul.ansible.com/t/ansible/build/d79dcec2e3024558800bba5fd6917505/log/job-output.txt "stderr": "/bin/sh: line 1: openssl: command not found" Reviewed-by: Alina Buzachis <None>
softwarefactory-project-zuul bot
pushed a commit
to ansible-collections/amazon.aws
that referenced
this pull request
Apr 22, 2022
ec2_vpc_igw - dont user filters to paginate to fix NoneType error Depends-On: ansible/ansible-zuul-jobs#1498 SUMMARY Use gateway id when describing gateway instances as opposed to filters if possible to avoid bug of no gateways found. Fixes #647 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_igw Reviewed-by: Gonéri Le Bouder <[email protected]> Reviewed-by: Mark Chappell <None> Reviewed-by: Joseph Torcasso <None> Reviewed-by: Alina Buzachis <None>
goneri
pushed a commit
to goneri/ansible-zuul-jobs
that referenced
this pull request
Apr 25, 2022
…-stable-2.12 non voting for amazon.aws (ansible#1498) Make ansible-ee-tests-latest globally non-voting and ansible-ee-tests-stable-2.12 non voting for amazon.aws ansible-latest (ie devel) is expected to break from time to time, with things like new sanity tests landing. Such changes will likely result in new ignore file entries being needed until cleanup can be applied. While we should be reacting reasonably quickly to this, we shouldn't instantly break CI for multiple collections. ansible-ee-tests-stable-2.12 and ansible-ee-tests-latest are currently broken for amazon.aws due to ansible#1497 this is a problem with the containers, the unit and sanity tests are running fine in the 'standard' environments.
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.
ansible-latest (ie devel) is expected to break from time to time, with things like new sanity tests landing. Such changes will likely result in new ignore file entries being needed until cleanup can be applied. While we should be reacting reasonably quickly to this, we shouldn't instantly break CI for multiple collections.
ansible-ee-tests-stable-2.12 and ansible-ee-tests-latest are currently broken for amazon.aws due to #1497 this is a problem with the containers, the unit and sanity tests are running fine in the 'standard' environments.