SUMMARY

It would be good to be able to manage balancer windows through the mongodb_balancer module.

See here: https://docs.mongodb.com/manual/tutorial/manage-sharded-cluster-balancer/#schedule-the-balancing-window

ISSUE TYPE

• Feature Idea

COMPONENT NAME

mongodb_balancer

SUMMARY

codecov is broken for some reason. Probably need to regenerate the base report

ISSUE TYPE

• Bug Report

SUMMARY

Module documentation is generated directly from the source files using a GitHub workflow... .github/workflows/documentation.yml

1. Fix url... http://ansible-collections.github.io/mongodb/
2. FIx doc formatting... it's messy - Can ansible-doc generate md format?

ISSUE TYPE

• Documentation Report

We could collectively benefit from forming a Working Group related to MongoDB integration. We have quite some contributors and users that are interested in improving this integration.

So this issue is a call to potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:

• test, review and add shipits to existing MongoDB PRs
• work collectively on a MongoDB roadmap
• provide a single-point-of-contact for interested MongoDB contributors
• collaborate on a MongoDB-specific Wiki
• have a $team_mongodb in BOTMETA.yml for auto-notifying team members
• implement auto-labeling MongoDB issues and PRs

SUMMARY

- name: Ensure replicaset rs0 exists
  mongodb_replicaset:
    login_host: localhost
    login_user: admin
    login_password: admin
    replica_set: rs0
    members:
    - "mongodb1:27017":
          priority: 1
    - "mongodb2:27017":
          priority: 0
    - "mongodb3:27017":
          priority: 0
  when: groups.mongod.index(inventory_hostname) == 0
```

The members list of dictionaries would be transformed into the following...

```
members: [
    { "_id": 0, "host": "mongodb1:27017", "priority": 1 },
    { "_id": 1, "host": "mongodb2:27017", "priority": 0 },
    { "_id": 1, "host": "mongodb3:27017", "priority": 0 },
]
```

We could allow any keys in the dictionary to future-proof it. "_id" value should be positional.

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME

mongodb_replicaset

SUMMARY

Hi,
To be more consistent with the other repos https://github.com/ansible-collections/ I'd like to rename this GitHub Repo to be community.mongodb

• Old URLs for issues and PRs will still work
• Old git URLs will work, though it will be good to update them locally
• We will need to update the URLs in galaxy.yml

Are you happy with this?

ISSUE TYPE

• Bug Report

SUMMARY

Replica Set Members not validated or configured.

ISSUE TYPE

• Bug Report

COMPONENT NAME

My best guess is that community.mongodb/plugins/modules/mongodb_replicaset.py is not using the members data to validate the config or to reconfigure the replica.

ANSIBLE VERSION

ansible 2.9.6
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/goferito/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0]

CONFIGURATION

OS / ENVIRONMENT

Ubuntu 20.04.1 LTS

STEPS TO REPRODUCE

Running the next task over a one-member initialized replica set, does not report any error, nor re-configures the replica.

    - name: Ensure replicaset rs0 exists
      mongodb_replicaset:
        login_host: localhost
        login_port: 10000
        replica_set: rs0
        members:
          - mongo1INT:10000
          - mongo2INT:10000
          - mongo3INT:10000
      validate: yes/no

EXPECTED RESULTS

If validate: yes, and the replica's config doesn't match, it should throw an error. If validate: no, it should reconfigure the replica?

ACTUAL RESULTS

Nothing happens. The task completes as [ok]. Nothing is changed. On the mongo server rs.config() or rs.status() still report just one member.

SUMMARY

See if we can avoid the occasional failures we see in the travis CI with the travis_retry function detailed here...

https://docs.travis-ci.com/user/common-build-problems/

ISSUE TYPE

• Feature Idea

COMPONENT NAME

travis_run.sh

SUMMARY

Implement the following...

https://docs.mongodb.com/manual/administration/production-notes/#configuring-numa-on-linux

In the roles...

mongodb_mongod
mongodb_config
mongodb_mongos

ISSUE TYPE

• Feature Idea

SUMMARY

check_compatibility function needs updating in most modules and is different in the mongodb_info module.

COMPONENT NAME

All mongodb modules

SUMMARY

Options common to all mongodb modules should be placed into the shared code struture.

See example here of how someone has done this...

https://github.com/ansible-collection-migration/ansible.ironware/blob/5d0226f13b1c1ee05f7d6d1915d2b6d5be74f5a1/plugins/modules/ironware_command.py

ISSUE TYPE

• Feature Idea

SUMMARY

Add ability to manage auto split through mongodb_shard. Simple disable / enable functionality.

https://docs.mongodb.com/manual/reference/method/sh.enableAutoSplit/

ISSUE TYPE

• Feature Idea

COMPONENT NAME

mongodb_shard

SUMMARY

There were a few commits to the mongodb.py lookup plugin and tests recently. Check these have been included here.

• Bug Report

COMPONENT NAME

mongodb.py

SUMMARY

The following work...

ansible/ansible#55639

Should be implemented in all MongoDB modules.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

All MongoDB modules

SUMMARY

For setting up a mongodb, being able to authenticate using the x509 Membership Authentication would be quite useful, as it would allow secure authentication before any user is configured.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

mongodb_common

ADDITIONAL INFORMATION

This feature could be used to configure a cluster from the first second with little preparation, in addition to that, the cluster could be set up without restarting any node, as authentication could be enabled at the first boot.

When implemented, the plugins could be used for doing something like this:

- name: create admin user
  command: |
    /usr/bin/mongo mongodb-host.test \
          --tls \
          --tlsCAFile /tmp/ca.crt \
          --tlsCertificateKeyFile=/tmp/tls.key \
          --authenticationMechanism MONGODB-X509 \
          --authenticationDatabase '$external' \
          --eval \
          '{{ lookup('template', 'templates/create-admin-user.js') }}'
  register: mongoout
  changed_when: "'{ \0ok\0 : 1 }' in mongoout.stdout"

Mongopy seems to support this.
The mongodb doc for x509 membership authentication.

SUMMARY

Implement ability to use SSL certs in all MongoDB modules. This has been discussed here...

ansible/ansible#66865

and there are also a couple of code contributions here...

ansible/ansible#52200 - Feb 2019
ansible/ansible#56911 - May 2019

If this is implemented it should be implemented in all modules

ISSUE TYPE

• Feature Idea

COMPONENT NAME

All MongoDB Modules

SUMMARY

Ansible spits out the following warning when we use the mongodb_user module...

[WARNING]: Module did not set no_log for update_password

Let's add no_log to this parameter. Not super important but prevents the unneeded nag.

ISSUE TYPE

• Bug Report

COMPONENT NAME

mongodb_user

SUMMARY

Bulk remove ANSIBLE_METADATA from all modules. The why is here... ansible-collections/overview#45 (comment)

Reference this in the PR: ansible-collections/overview#45

ISSUE TYPE

• Bug Report

COMPONENT NAME

All modules

This collection will be included in Ansible 2.10 because it contains modules and/or plugins that were included in Ansible 2.9. Please review:

• The list of requirements for inclusion in Ansible: https://github.com/ansible-collections/overview/blob/master/collection_requirements.rst
• The roadmap with all important dates for Ansible 2.10: https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/roadmap/COLLECTIONS_2_10.rst

DEADLINE: 2020-08-18

The latest version of the collection available on August 18 will be included in Ansible 2.10.0, except possibly newer versions which differ only in the patch level. (For details, see the roadmap). Please release version 1.0.0 of your collection by this date! If 1.0.0 does not exist, the same 0.x.y version will be used in all of Ansible 2.10 without updates, and your 1.x.y release will not be included until Ansible 2.11 (unless you request an exception at a community working group meeting and go through a demanding manual process to vouch for backwards compatibility . . . you want to avoid this!).

Follow semantic versioning rules

Your collection versioning must follow all semver rules. This means:

• Patch level releases can only contain bugfixes;
• Minor releases can contain new features, new modules and plugins, and bugfixes, but must not break backwards compatibility;
• Major releases can break backwards compatibility.

Changelogs and Porting Guide

Your collection should provide data for the Ansible 2.10 changelog and porting guide. The changelog and porting guide are automatically generated from ansible-base, and from the changelogs of the included collections. All changes from the breaking_changes, major_changes, removed_features and deprecated_features sections will appear in both the changelog and the porting guide. You have two options for providing changelog fragments to include:

1. If possible, use the antsibull-changelog tool, which uses the same changelog fragment as the ansible/ansible repository (see the documentation).
2. If you cannot use antsibull-changelog, you can provide the changelog in a machine-readable format as changelogs/changelog.yaml inside your collection (see the documentation of changelogs/changelog.yaml format).

If you cannot contribute to the integrated Ansible changelog using one of these methods, please provide a link to your collection's changelog by creating an issue in https://github.com/ansible-community/ansible-build-data/. If you do not provide changelogs/changelog.yml or a link, users will not be able to find out what changed in your collection from the Ansible changelog and porting guide.

Make sure your collection passes the sanity tests

Run ansible-test sanity --docker -v in the collection with the latest ansible-base or stable-2.10 ansible/ansible checkout.

Keep informed

Be sure you're subscribed to:

• Changes impacting Collections to track changes that Collection maintainers should be aware of;
• The Bullhorn, a newsletter for the Ansible developer community, back issues and how to add content.

Questions and Feedback

If you have questions or want to provide feedback, please see the Feedback section in the collection requirements.

(Internal link to keep track of issues: ansible-collections/overview#102)

SUMMARY

Add a Testinfra tests where we reboot the node and check that the mongod/s service comes back up after reboot

ISSUE TYPE

• Feature Idea

COMPONENT NAME

roles/clusters

SUMMARY

If we can pass ansible variables into ansible-test we can override the version and run the tests using multiple versions of MongoDB. The last two releases should suffice.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

ansible-test / github workflow

SUMMARY

documentation.yml workflow broken. Modules pages are empty. Perhaps due to the introduction of fragments?

ISSUE TYPE

• Bug Report

SUMMARY

There is a bogus git tag that makes pushing to a fork difficult. I was trying to bring my fork's master up-to-date. When I push, I get:

error: dst refspec refs/heads/master matches more than one
error: failed to push some refs to '[email protected]:cognifloyd/community.mongodb.git'

I've deleted the refs/heads/master tag (yes, tag, not a branch) from my fork, but every time I git fetch --all from my upstream remote (this repo) to get any new release tags, it also re-adds the bad tag.

ISSUE TYPE

• Bug Report

COMPONENT NAME

git

HOW TO FIX

Someone with commit access to this repo, please (1) delete the tag locally, and then (2) delete the tag on github.

git tag -d refs/heads/master
git push origin :refs/tags/refs/heads/master

Tested with my fork.

SUMMARY

Script failed when there are no role modification in the script. We should handle this...

/home/travis/build/ansible-collections/mongodb
There are 32 files in this commit.
./travis_run.sh: line 37: role_list[@]: unbound variable
The command "./travis_run.sh" exited with 1.
```

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME

travis_run.sh

SUMMARY

lookup_mongodb int tests only run on Ubuntu. Update these to run on all OS's.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

lookup_mongodb int tests

ADDITIONAL INFORMATION

Restriction is in tasks/main.yml

SUMMARY

The apt module auto-installs python-apt automatically if needed. Could/Should we do this in the MongoDB modules?

• Should be implemented in all modules if taken on.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

All MongoDB modules

SUMMARY

These tests should probably use the standard setup_mongodb process like the others.

ISSUE TYPE

• Feature Idea

SUMMARY

It sould be possible to create a workflow that can build and deploy a collection to Ansible Galaxy. This could perhaps be triggered by a keyword in the commit message.

ISSUE TYPE

• Feature Idea

SUMMARY

ERROR: Found 1 pylint issue(s) which need to be resolved:
ERROR: plugins/cache/mongodb.py:74:12: collection-invalid-deprecated-version: Invalid deprecated version ('2.12') found in call to Display.deprecated or AnsibleModule.deprecate
See documentation for help: https://docs.ansible.com/ansible/devel/dev_guide/testing/sanity/pylint.html

ISSUE TYPE

• Bug Report

COMPONENT NAME

plugins/cache/mongodb.py

SUMMARY

ISSUE TYPE

• Bug Report

COMPONENT NAME

mongodb_replicaset

ANSIBLE VERSION

rick@beryl /nvme/rick/dev/ansible/ansible $ ansible --version
ansible 2.9.12.post0
  config file = None
  configured module search path = ['/nvme/gentoo/rick/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /nvme/rick/dev/ansible/ansible/lib/ansible
  executable location = /nvme/rick/dev/ansible/ansible/bin/ansible
  python version = 3.7.8 (default, Jul 25 2020, 16:21:40) [GCC 9.3.0]

CONFIGURATION

N/A

OS / ENVIRONMENT

RHEL-ish

STEPS TO REPRODUCE

RHEL tests are currently failing in ansible/ansible because mongodb released 4.0.20 in their yum repo which has a change that breaks mongodb_replicaset.

Test result:
https://app.shippable.com/github/ansible/ansible/runs/172750/53/console

I dug into this a bit:

The mongodb_replicaset module runs a listDatabases query to determine if it needs to auth or not.

Basically, in 4.0.19, this query works:

> db.adminCommand({ listDatabases: 1.0, $readPreference: { mode: "primaryPreferred" }})
{
	"databases" : [
		{
			"name" : "local",
			"sizeOnDisk" : 180224,
			"empty" : false
		}
	],
	"totalSize" : 180224,
	"ok" : 1,
	"operationTime" : Timestamp(0, 0),
	"$clusterTime" : {
		"clusterTime" : Timestamp(0, 0),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

In 4.0.20, it fails:

> db.adminCommand({ listDatabases: 1.0, $readPreference: { mode: "primaryPreferred" }})
{
	"operationTime" : Timestamp(0, 0),
	"ok" : 0,
	"errmsg" : "node is not in primary or recovering state",
	"code" : 13436,
	"codeName" : "NotMasterOrSecondary",
	"$clusterTime" : {
		"clusterTime" : Timestamp(0, 0),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

It fails in both without $readPreference - which makes me think that 4.0.20 stopped obeying that option for some reason. I stopped my digging there, my next step would probably be to bisect mongodb and see what commit broke this, but I haven't.

We are disabling the test in ansible/ansible for now. Ideally if you're able to look into this and work around it, a backport to 2.9 would be great.

SUMMARY

Currently we manually specify the lit of modules we test in CI with a lit of strings. It would be good to populate this dynamically so we don't have to manage it. Need to remember cache(lookup plugins also)

Maybe something like this will work?

- name: Get pip cache dir
  id: pip-cache
  run: |
    echo "::set-output name=dir::$(pip cache dir)"

https://github.com/actions/cache/blob/main/examples.md#python---pip

ISSUE TYPE

• Feature Idea

COMPONENT NAME

CI workflows

SUMMARY

Couple of issues noted from script output...

Many reports. Old ones not purged? Should they be?

+ ./tests/output/coverage/integration=mongodb_status=docker-default=python-3.6=coverage.33df63ea82fd.21336.617885 bytes=74
+ ./tests/output/coverage/integration=mongodb_shard=docker-default=python-3.6=coverage.33df63ea82fd.16556.359546 bytes=74
+ ./tests/output/coverage/integration=mongodb_parameter=docker-default=python-3.6=coverage.33df63ea82fd.2458.500220 bytes=74
+ ./tests/output/coverage/integration=mongodb_status=docker-default=python-3.6=coverage.33df63ea82fd.20412.121263 bytes=74
+ ./tests/output/coverage/integration=mongodb_shard=docker-default=python-3.6=coverage.33df63ea82fd.14135.428499 bytes=74
+ ./tests/output/coverage/integration=mongodb_replicaset=docker-default=python-3.6=coverage.33df63ea82fd.7543.442920 bytes=74
+ ./tests/output/coverage/integration=mongodb_replicaset=docker-default=python-3.6=coverage.33df63ea82fd.6263.373808 bytes=74
+ ./tests/output/coverage/integration=mongodb_parameter=docker-default=python-3.6=coverage.33df63ea82fd.3193.880675 bytes=268
+ ./tests/output/coverage/integration=mongodb_replicaset=docker-default=python-3.6=coverage.33df63ea82fd.4286.009747 bytes=74
+ ./tests/output/coverage/integration=mongodb_status=docker-default=python-3.6=coverage.33df63ea82fd.18989.000571 bytes=74
+ ./tests/output/coverage/integration=mongodb_shard=docker-default=python-3.6=coverage.33df63ea82fd.15595.861734 bytes=74
+ ./tests/output/coverage/integration=mongodb_shard=docker-default=python-3.6=coverage.33df63ea82fd.16671.557285 bytes=74

Other issues...

+ -X coveragepy -X gcov -X fix -X search -X xcode -K
tests/coverage.sh: line 27: -X: command not found
+ echo 'Failed to upload code coverage report to codecov.io: tests/output/coverage/coverage=*.xml'
Failed to upload code coverage report to codecov.io: tests/output/coverage/coverage=*.xml

ISSUE TYPE

• Bug Report

COMPONENT NAME

coverage.sh

SUMMARY

Upgrade all tests to use MongoDB 4.2 repo

ISSUE TYPE

• Feature Idea

SUMMARY

MongoDB cache fails to run if cache exists with no TTL

ISSUE TYPE

• Bug Report

COMPONENT NAME

MongoDB cache

ANSIBLE VERSION

ansible 2.9.11
  config file = /home/{user}/.ansible.cfg
  configured module search path = ['/home/{user}/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.6/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.6.8 (default, Dec  5 2019, 15:45:45) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]

CONFIGURATION

ANSIBLE_SSH_ARGS(/home/{user}/.ansible.cfg) = -o ControlMaster=auto -o ControlPersist=90s
ANSIBLE_SSH_CONTROL_PATH(/home/{user}/.ansible.cfg) = %(directory)s/%%h-%%p-%%r
CACHE_PLUGIN(/home/{user}/.ansible.cfg) = mongodb
CACHE_PLUGIN_CONNECTION(/home/{user}/.ansible.cfg) = mongodb://{user}:{password}@127.0.0.1:27017/
CACHE_PLUGIN_PREFIX(/home/{user}/.ansible.cfg) = fact_
CACHE_PLUGIN_TIMEOUT(/home/{user}/.ansible.cfg) = 0
DEFAULT_FORKS(/home/{user}/.ansible.cfg) = 100
DEFAULT_GATHERING(/home/{user}/.ansible.cfg) = implicit
DEFAULT_GATHER_SUBSET(/home/{user}/.ansible.cfg) = ['all']
DEFAULT_LOG_PATH(/home/{user}/.ansible.cfg) = /var/log/ansible.log
DEFAULT_NO_TARGET_SYSLOG(/home/{user}/.ansible.cfg) = True
DEFAULT_POLL_INTERVAL(/home/{user}/.ansible.cfg) = 15
DEFAULT_SCP_IF_SSH(/home/{user}/.ansible.cfg) = True
DEFAULT_TIMEOUT(/home/{user}/.ansible.cfg) = 5
DEFAULT_VAULT_PASSWORD_FILE(/home/{user}/.ansible.cfg) = /home/{user}/ans.txt
HOST_KEY_CHECKING(/home/{user}/.ansible.cfg) = False
RETRY_FILES_ENABLED(/home/{user}/.ansible.cfg) = False

OS / ENVIRONMENT

OS: RHEL 8.2
Kernel: 4.18.0-193.14.3.el8_2.x86_64
Mongo Ver: 4.4.0

STEPS TO REPRODUCE

Configure mongodb cache plugin to have CACHE_PLUGIN_TIMEOUT=0. Run any playbook that uses cache twice. Do not delete the cache between runs.

EXPECTED RESULTS

Run playbook and cache in mongodb

ACTUAL RESULTS

Fails on second run with the following error:

 ERROR! Unexpected Exception, this is probably a bug: index not found with name [ttl], full error: {'ok': 0.0, 'errmsg': 'index not found with name [ttl]', 'code': 27, 'codeName': 'IndexNotFound'}

SUMMARY

The mongodb_shell module only supports a limited number of cmd line options. Add the ability to add arbitrary cmd line options so the user is not limited in any way. Hint: Could be implemented in a similar way to connection_options

ISSUE TYPE

• Feature Idea

COMPONENT NAME

mongodb_shell & int tests

SUMMARY

Add ability to install specific minor version of mongodb-org package.

ISSUE TYPE

• Feature Idea
  Add variable to be able to set specific minor version.

COMPONENT NAME

mongodb_install role

SUMMARY

Implement the ability to manage the balancer through the mongodb_shard module. Can use the following methods...

https://docs.mongodb.com/manual/reference/method/sh.isBalancerRunning/

ISSUE TYPE

• Feature Idea

COMPONENT NAME

mongodb_shard

SUMMARY

When adding a shard the module checks for the connected server being a mongos by comparing the process name returned from the serverStatus to 'mongos'. That process name can be changed by using a custom name for the mongos binary (different versions on the same server or other reasons). Therefor the module fails in that case complaining that the process running on the specified host/port is not a mongos.

See https://github.com/ansible-collections/community.mongodb/blob/master/plugins/modules/mongodb_shard.py#L478

ISSUE TYPE

• Bug Report

COMPONENT NAME

mongodb_shard

ANSIBLE VERSION

ansible 2.8.11
  config file = /ansible/playbooks/de/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.7.5 (default, Oct 17 2019, 12:25:15) [GCC 8.3.0]

CONFIGURATION

ANSIBLE_PIPELINING(/ansible/playbooks/de/ansible.cfg) = True
ANSIBLE_SSH_ARGS(/ansible/playbooks/de/ansible.cfg) = -o ForwardAgent=yes -o ControlMaster=auto -o ControlPersist=60s -o PreferredAuthentications=password,publickey
DEFAULT_ACTION_PLUGIN_PATH(env: ANSIBLE_ACTION_PLUGINS) = ['/ansible/plugins/action_plugins']
DEFAULT_FORKS(/ansible/playbooks/de/ansible.cfg) = 20
DEFAULT_LOG_PATH(/ansible/playbooks/de/ansible.cfg) = /ansible/playbooks/de/ansible.log
DEFAULT_TIMEOUT(/ansible/playbooks/de/ansible.cfg) = 30
DEFAULT_VAULT_IDENTITY_LIST(env: ANSIBLE_VAULT_IDENTITY_LIST) = ['production-de@/tmp/.vault-password-production-de', 'staging-de@/tmp/.vault-password-staging-de', 'test-de@/tmp/.vault-password-test-de']
HOST_KEY_CHECKING(/ansible/playbooks/de/ansible.cfg) = False

OS / ENVIRONMENT

Debian 10.2

STEPS TO REPRODUCE

Rename the mongos binary to some random name or create a symlink with another name (like custom-mongos-1) and use that for starting the mongos service. The server status of the mongos should show the custom binary in the process field:

mongos> db.serverStatus()
{
	"host" : "mongos-1.yourdomain.net:58350",
	"version" : "3.4.24",
	"process" : "custom-mongos-1",
        ...
}

Now try adding a shard using the mongodb_shard module.

- name: Add all shards to the cluster
  mongodb_shard:
    login_host: "{{ item.0.mongos_login_host }}"
    login_port: "{{ item.0.mongos_login_port|int }}"
    shard: "{{ item.0.replicaset }}/{{ item.1 }}"
    state: present
  loop: "{{ mongodb_shards|subelements('members') }}"
  when: item.0.type == 'shard'
  run_once: yes

EXPECTED RESULTS

Shard is added to MongoDB cluster

ACTUAL RESULTS

failed: [shard1-1.yourdomain.net] (item=[{'replicaset': 'shard1', 'type': 'shard', 'login_host': 'shard1-1.yourdomain.net', 'login_port': 28351, 'mongos_login_host': 'mongos-1.yourdomain.net', 'mongos_login_port': 58350, 'members': ['shard1-1.yourdomain.net:28351', 'shard1-2.yourdomain.net:28351', 'shard1-3.yourdomain.net:28351']}, 'shard1-3.yourdomain.net:28351']) => {"ansible_loop_var": "item", "changed": false, "item": [{"login_host": "shard1-1.yourdomain.net", "login_port": 28351, "members": ["shard1-1.yourdomain.net:28351", "shard1-2.yourdomain.net:28351", "shard1-3.yourdomain.net:28351"], "mongos_login_host": "mongos-1.yourdomain.net", "mongos_login_port": 58350, "replicaset": "shard1", "type": "shard"}, "shard1-3.yourdomain.net:28351"], "msg": "Process running on mongos-1.yourdomain.net:58350 is not a mongos"}

Migrated issue from ansible/ansible#69256.

SUMMARY

The mongod service breaks after being restarted in RedHat 8 because the pid dir is cleaned up but then cannot be recreated. Modifiy the template to not include this when RedHat 8 plus ... or different path...

https://github.com/ansible-collections/community.mongodb/blob/master/roles/mongodb_mongod/templates/mongod.conf.j2

ISSUE TYPE

• Bug Report

SUMMARY

Add integration tests for the auth feature discussed in #177.

The pymongo based module all use the same code, so if one work they all should, still probably not a bad idea to add tests for multiple modules where reasonable. The k8 env in #179 can be used. Rhys to add a few notes to the README.md

ISSUE TYPE

• Feature Idea

COMPONENT NAME

integration tests

SUMMARY

Already done this for ssl options. Do the same for the other shared options.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

All modules.

SUMMARY

Add ability to enable sharding on a database to mongodb_shard.

• Enable sharding on a db: adminCommand({enableSharding: dbname});
• Disable sharding? Not possible?

ISSUE TYPE

• Feature Idea

COMPONENT NAME

mongodb_shard

SUMMARY

Incorrect references to namespace/project? Or is this simply waiting for further setup? Same issue in the community.cassandra namespace https://github.com/ansible-collections/cassandra/blob/master/galaxy.yml

galaxy.yml contains references to community.mongo, i.e.

homepage: https://github.com/ansible-collections/community.mongo

Should this not be...

homepage: https://github.com/ansible-collections/mongodb?

There are references elsewhere to this namespace.project form. These links 404.

ISSUE TYPE

• Bug Report

COMPONENT NAME

galaxy.yml

SUMMARY

The "Big Migration" has now taken place.

As this collection already exists, we need to carefully check to see if any further commits went into devel since this repo was created.

Please check the contents of https://github.com/ansible-collection-migration/community.mongo against this repo

ISSUE TYPE

• Bug Report

SUMMARY

Move duplicated code into a ./module_utils directory. Perhaps units tests too?

https://docs.ansible.com/ansible/latest/dev_guide/developing_module_utilities.html

ISSUE TYPE

• Feature Idea

SUMMARY

It seems the update_password does not compare the current password in the database and update the password on every run even if it's the same one. According to the doc: always(which is the default) will update passwords if they differ

ISSUE TYPE

• Bug Report

COMPONENT NAME

mongodb_user

ANSIBLE VERSION

ansible 2.9.10
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/var/lib/rundeck/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.12 (default, Nov 12 2018, 14:36:49) [GCC 5.4.0 20160609]

CONFIGURATION

DEFAULT_FORKS(/etc/ansible/ansible.cfg) = 25
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = [u'/etc/ansible/inventories']
DEFAULT_REMOTE_USER(/etc/ansible/ansible.cfg) = rundeck
DEFAULT_VAULT_PASSWORD_FILE(/etc/ansible/ansible.cfg) = /var/lib/rundeck/vault_pass.txt
INTERPRETER_PYTHON(/etc/ansible/ansible.cfg) = /usr/bin/python3

OS / ENVIRONMENT

Target OS:

Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.4 LTS
Release:	18.04
Codename:	bionic
MongoDB shell version v4.2.8
git version: 43d25964249164d76d5e04dd6cf38f6111e21f5f
OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
allocator: tcmalloc
modules: none
build environment:
    distmod: ubuntu1804
    distarch: x86_64
    target_arch: x86_64

STEPS TO REPRODUCE

Use the following code:

- name: Create Mongodb users
  mongodb_user:
    database: admin
    name: "mongo"
    password: "changeme"
    roles: readWriteAnyDatabase
    state: present

and watch the password being overwritten every run with:

mongo
use admin
db.getUsers({showCredentials: true})

EXPECTED RESULTS

Return 'Changed' the first time the user is created. Subsequent runs should not overwrite the password if it's the same thing already

ACTUAL RESULTS

Password is changed on every run which result in always a 'Changed'

changed: [test] => {
    "changed": true,
    "invocation": {
        "module_args": {
            "database": "admin",
            "login_database": null,
            "login_host": "localhost",
            "login_password": null,
            "login_port": "27017",
            "login_user": null,
            "name": "mongo",
            "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
            "replica_set": null,
            "roles": [
                "readWriteAnyDatabase"
            ],
            "ssl": false,
            "ssl_cert_reqs": "CERT_REQUIRED",
            "state": "present",
            "update_password": "always"
        }
    },
    "user": "mongo"
}

SUMMARY

Ensure changes from ansible/ansible#71393 are put into this collections version of the module.

ISSUE TYPE

• Bug Report

COMPONENT NAME

mongodb_replicaset

SUMMARY

There's a few methods in module_utils/mongodb_common.py that access MongoDB and could do with unit tests. We could use https://github.com/mongomock/mongomock for these.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

module_utils/mongodb_common.py

SUMMARY

The integration tests (at least for mongodb_shard/replicaset) contain version specific checks that we were forced to do. We basically repeat the same tasks with version 3/4. Since we only test only the two previous releases (currently 4.0 and 4.2) we should remove the version check stuff.

ISSUE TYPE

• Bug Report

SUMMARY

Add integration tests for ssl options. All modules now have corresponding options for the pymongo ssl connection options. These should be tested against ssl enabled mongod/s instances.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

All modules.