-
Type:
Bug
-
Resolution: Done
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
0.25
With v3.4 documentation rolled out we have major inconsistencies in installation instructions for the Enterprise version of MongoDB (docs for Community edition look ok).
For RedHat - note the 3.2 repo being suggested:
[mongodb-enterprise] name=MongoDB Enterprise Repository baseurl=https://repo.mongodb.com/yum/redhat/$releasever/mongodb-enterprise/3.2/$basearch/ gpgcheck=1 enabled=1 gpgkey=https://www.mongodb.org/static/pgp/server-3.4.asc
The same problem is with the Amazon Linux docs.
For Ubuntu we suggest installing a new public key:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 0C49F3730359A14518585931BC711F9BA15703C6
But the repos are still the 3.2 ones:
echo "deb http://repo.mongodb.com/apt/ubuntu precise/mongodb-enterprise/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-enterprise.list echo "deb http://repo.mongodb.com/apt/ubuntu trusty/mongodb-enterprise/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-enterprise.list echo "deb http://repo.mongodb.com/apt/ubuntu xenial/mongodb-enterprise/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-enterprise.list
For Debian we have the same issue - new key, old repos. I've tried following the instruction on my test machine and found that the new key does not fit the old (3.2) repos:
W: GPG error: http://repo.mongodb.com wheezy/mongodb-enterprise/3.2 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D68FA50FEA312927
SUSE looks good.