[DNM] test EE tests #432
Closed
[DNM] test EE tests #432
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
ansibullbot
added
bug
|
recheck |
1 similar comment
|
recheck |
|
@Akasurde Please can we rename these jobs "network-ee" is misleading. Something like "ansible-ee-" would be better. |
|
@tremble This is an already written job and shared by multiple teams. So I think @pabelanger is the right person to answer this. |
pabelanger
suggested changes
Aug 14, 2021
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
|
recheck |
|
Sorry, I caused a bug in the docker jobs over the weekend this is now fixed by: ansible/ansible-zuul-jobs#1062 |
|
Added ansible/ansible-zuul-jobs#1046 too |
|
recheck |
|
failure looks to be network related |
|
recheck |
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this pull request
Sep 18, 2023
New Module: Amazon MQ SUMMARY replicates ansible-collections#266 as suggested This PR contains some basic support for Amazon MQ. It covers Managing Amazon MQ brokers Managing Amazon MQ configurations Managing Amazon MQ (local) users ISSUE TYPE New Module Pull Request COMPONENT NAME Amazon MQ ADDITIONAL INFORMATION We use those modules to manage our MQ Brokers. The context of usage is brokers are created by different means (e.g. terraform) - but the module is capable of doing that as well we've developed a custom role around those modules to manage MQ user credentials we use another local extension of amazon.aws collection (will come as separate PR) that interfaces with AWS SecretsManager that role uses the reboot broker feature (part of this PR) to implement a custom handler that reboots a broker whenever a configuration run sees any changes in configuration and/or users The functionality of the added modules is illustrated in the added test suite (tests/integration/targets/mq) some of them still require a running MQ broker to be usable. Missing functionality/limitations: requires a recent version of boto3 library (older versions don't support all Amazon MQ features used here) API results are returned "as is", i.e. there's no conversion from camel case yaml to snake yaml mq_broker.py no support for LDAP connection (external user management) update configuration only supported through mq_broker_config.py known to work only with EngineType=ACTIVEMQ (proper support for RABBITMQ still missing) mq_broker_config.py needs proper XML comparison between current and desired configuration (current one is too simplistic) only tested with ActiveMQ configurations Reviewed-by: Mark Chappell Reviewed-by: Alina Buzachis
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this pull request
Sep 18, 2023
New Module: Amazon MQ SUMMARY replicates ansible-collections#266 as suggested This PR contains some basic support for Amazon MQ. It covers Managing Amazon MQ brokers Managing Amazon MQ configurations Managing Amazon MQ (local) users ISSUE TYPE New Module Pull Request COMPONENT NAME Amazon MQ ADDITIONAL INFORMATION We use those modules to manage our MQ Brokers. The context of usage is brokers are created by different means (e.g. terraform) - but the module is capable of doing that as well we've developed a custom role around those modules to manage MQ user credentials we use another local extension of amazon.aws collection (will come as separate PR) that interfaces with AWS SecretsManager that role uses the reboot broker feature (part of this PR) to implement a custom handler that reboots a broker whenever a configuration run sees any changes in configuration and/or users The functionality of the added modules is illustrated in the added test suite (tests/integration/targets/mq) some of them still require a running MQ broker to be usable. Missing functionality/limitations: requires a recent version of boto3 library (older versions don't support all Amazon MQ features used here) API results are returned "as is", i.e. there's no conversion from camel case yaml to snake yaml mq_broker.py no support for LDAP connection (external user management) update configuration only supported through mq_broker_config.py known to work only with EngineType=ACTIVEMQ (proper support for RABBITMQ still missing) mq_broker_config.py needs proper XML comparison between current and desired configuration (current one is too simplistic) only tested with ActiveMQ configurations Reviewed-by: Mark Chappell Reviewed-by: Alina Buzachis
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this pull request
Oct 24, 2023
New Module: Amazon MQ SUMMARY replicates ansible-collections#266 as suggested This PR contains some basic support for Amazon MQ. It covers Managing Amazon MQ brokers Managing Amazon MQ configurations Managing Amazon MQ (local) users ISSUE TYPE New Module Pull Request COMPONENT NAME Amazon MQ ADDITIONAL INFORMATION We use those modules to manage our MQ Brokers. The context of usage is brokers are created by different means (e.g. terraform) - but the module is capable of doing that as well we've developed a custom role around those modules to manage MQ user credentials we use another local extension of amazon.aws collection (will come as separate PR) that interfaces with AWS SecretsManager that role uses the reboot broker feature (part of this PR) to implement a custom handler that reboots a broker whenever a configuration run sees any changes in configuration and/or users The functionality of the added modules is illustrated in the added test suite (tests/integration/targets/mq) some of them still require a running MQ broker to be usable. Missing functionality/limitations: requires a recent version of boto3 library (older versions don't support all Amazon MQ features used here) API results are returned "as is", i.e. there's no conversion from camel case yaml to snake yaml mq_broker.py no support for LDAP connection (external user management) update configuration only supported through mq_broker_config.py known to work only with EngineType=ACTIVEMQ (proper support for RABBITMQ still missing) mq_broker_config.py needs proper XML comparison between current and desired configuration (current one is too simplistic) only tested with ActiveMQ configurations Reviewed-by: Mark Chappell Reviewed-by: Alina Buzachis
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.
SUMMARY
Signed-off-by: Abhijeet Kasurde akasurde@redhat.com
ISSUE TYPE
COMPONENT NAME
zuul.yaml
Depends-On: ansible/ansible-zuul-jobs#1062
Depends-On: ansible/ansible-zuul-jobs#1046