MongoDB "not authorized for query on local.system.replset"

[Vlad Okhrimenko]

The deployment of MOS 7 has failed

In logs from the diagnostic snapshot:

2015-10-01 18:23:37 +0000 /Stage[main]/Openstack::Mongo/Notify[MongoDB params: 127.0.0.110.80.20.5]/message (notice): defined 'message' as 'MongoDB params: 127.0.0.110.80.20.5'
2015-10-01 18:23:38 +0000 Puppet (err): Could not prefetch mongodb_replset provider 'mongodb': Execution of '/usr/bin/mongo --quiet --host 127.0.0.1:27017 --eval load('/root/.mongorc.js'); printjson(rs.conf())' returned 252: Error: 18 { ok: 0.0, errmsg: "auth failed", code: 18 }
2015-10-01T18:23:38.205+0000 error: { "$err" : "not authorized for query on local.system.replset", "code" : 13 } at src/mongo/shell/query.js:131/usr/lib/ruby/vendor_ruby/puppet/util/execution.rb:188:in `execute'
/usr/lib/ruby/vendor_ruby/puppet/provider/command.rb:23:in `execute'
/usr/lib/ruby/vendor_ruby/puppet/provider.rb:237:in `block in has_command'
/etc/puppet/modules/mongodb/lib/puppet/provider/mongodb_replset/mongodb.rb:338:in `mongo_command'
/etc/puppet/modules/mongodb/lib/puppet/provider/mongodb_replset/mongodb.rb:148:in `get_replset_properties'
/etc/puppet/modules/mongodb/lib/puppet/provider/mongodb_replset/mongodb.rb:31:in `instances'
/etc/puppet/modules/mongodb/lib/puppet/provider/mongodb_replset/mongodb.rb:41:in `prefetch'

diagnostic snapshot:
https://drive.google.com/a/mirantis.com/file/d/0B3-pc36alqDQMmZmRGdDc1pKcHM/view?usp=sharing

[Stanislav Makar (smakar)]

There are no other logs from master node except atop in this diag snap

 ll fuel-snapshot-2015-10-01_18-45-19/10.80.0.2/var/log/
загалом 12
drwxr-xr-x 3 stas stas 4096 жов 1 21:46 ./
drwxr-xr-x 3 stas stas 4096 жов 1 21:46 ../
drwxr-xr-x 2 stas stas 4096 жов 1 21:46 atop/

ll fuel-snapshot-2015-10-01_18-45-19/10.80.0.2/etc/
загалом 12
drwxr-xr-x 3 stas stas 4096 жов 1 21:46 ./
drwxr-xr-x 6 stas stas 4096 жов 1 21:46 ../
drwxr-xr-x 2 stas stas 4096 жов 1 21:46 sysconfig/

Please provide ISO version first of all?

[Vlad Okhrimenko (vokhrimenko)]

[root@fuel ~]# cat /etc/fuel/version.yaml
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "7.0"
openstack_version: "2015.1.0-7.0"
api: "1.0"
build_number: "301"
build_id: "301"
nailgun_sha: "4162b0c15adb425b37608c787944d1983f543aa8"
python-fuelclient_sha: "486bde57cda1badb68f915f66c61b544108606f3"
fuel-agent_sha: "50e90af6e3d560e9085ff71d2950cfbcca91af67"
fuel-nailgun-agent_sha: "d7027952870a35db8dc52f185bb1158cdd3d1ebd"
astute_sha: "6c5b73f93e24cc781c809db9159927655ced5012"
fuel-library_sha: "5d50055aeca1dd0dc53b43825dc4c8f7780be9dd"
fuel-ostf_sha: "2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c"
fuelmain_sha: "a65d453215edb0284a2e4761be7a156bb5627677"

[Stanislav Makar (smakar)]

Please provide steps how to reproduce it ?

[Adam Heczko (aheczko-mirantis)]

Folks, why is this marked as private security?
My understanding is that failed deployment (even because of some authorization problem) doesn't affect environment/product security.

[Matthew Mosesohn (raytrac3r)]

Removing private security. Still needs research

[Maciej Relewicz (rlu)]

After talk to Vlad I close the bug

[Mike Scherbakov (mihgen)]

Maciej,
can you please provide more details on your conversation with Vlad? Why did you decide to close this issue?
We need to provide a clear reason for every bug status change, including priority.
Thanks!

[Maciej Relewicz (rlu)]

I closed this bug because Vlad didnt have pemission to set 'won't fix' status. Problem wasn't related with bug, but with something else.

[Vitaly Sedelnik (vsedelnik)]

Per latest comment from Maciej the proper status would be Invalid, not Won't Fix