Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Satellite to Capsule sync fails with "Could not save document (BSONObj size: 16797589 (0x1004F95) is invalid. Size must be between 0 and 16793600(16MB)"
Description of problem:
Satellite/Capsule is trying to save information to the mongodb with a size larger than the BSONObj batch size is set for.
Version-Release number of selected component (if applicable):
Satellite 6.2.7
Capsule 6.2.7
mongodb-2.6.11-2.el7sat.x86_64
How reproducible:
N/A
Steps to Reproduce:
1.
2.
3.
Actual results:
From the task:
"Could not save document (BSONObj size: 16797589 (0x1004F95) is invalid. Size must be between 0 and 16793600(16MB) First element: _id: \"a4e92bb7-01be-4a4d-a1ed-6193b6d915d3\")"},
"metadata"=>{"state"=>"FINISHED"}}
Satellite's /var/log/mongodb/mongodb.log
2017-04-26T09:55:44.789-0400 [conn11543] warning: log line attempted (677k) over max size (10k)
2017-04-26T09:55:42.131-0400 [conn11543] warning: log line attempted (677k) over max size (10k)
Capsule's /var/log/mongodb/mongodb.log
2017-04-27T10:45:47.012-0400 [conn94] warning: log line attempted (6278k) over max size (10k)
2017-04-27T10:45:46.923-0400 [conn94] warning: log line attempted (6278k) over max size (10k)
2017-04-27T10:44:06.318-0400 [conn96] warning: log line attempted (11535k) over max size (10k)
2017-04-27T10:44:00.997-0400 [conn94] warning: log line attempted (13162k) over max size (10k)
Expected results:
Successful sync
Additional info:
Comment 8pulp-infra@redhat.com
2017-04-27 21:03:09 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 9pulp-infra@redhat.com
2017-04-27 21:03:12 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 10Marcelo Moreira de Mello
2017-04-27 21:10:13 UTC
Workaround notes from bz #1388296https://bugzilla.redhat.com/show_bug.cgi?id=1388296#c22
=== HOTFIX INSTRUCTIONS FOR SATELLITE 6.2.7 ONLY ===
1. Download attached files
2. Stop services on both Capsule and Satellite
katello-service stop
3. Extract both tarballs on the Satellite server
tar xvf hotfix_katello-3.0.0.95-2.BZ1388296.el7sat.noarch.tar.bz2
tar xvf pulp-hotfix-2.8.7.5-2.BZ_1388296.el7.tar.bz2
4. Extract the only the pulp tarball on the Capsule servers
tar xvf pulp-hotfix-2.8.7.5-2.BZ_1388296.el7.tar.bz2
5. Update the packages on both the Satellite and Capsule servers
yum update *.rpm (be sure that the untared rpms are the only ones in the cwd)
6. Upgrade Satellite
satellite-installer --scenario satellite --upgrade
wait for this to finish and the Satellite to be running, then:
7. Upgrade the capsules
satellite-installer --scenario capsule --upgrade
To rollback any changes you can use yum history to view the yum transactions and yum history undo <yum_transaction_number>
You may run into this error on the capsules when re-running the installer:
Upgrade Step: start_httpd...
Redirecting to /bin/systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Some services failed to start: httpd
in httpd logs:
Feb 22 18:33:54 capsule627.example.com httpd[25756]: AH00526: Syntax error on line 28 of /etc/httpd/conf.d/pulp.conf:
Feb 22 18:33:54 capsule627.example.com httpd[25756]: Name duplicates previous WSGI daemon definition.
workaround:
Manually edit /etc/httpd/conf.d/pulp.conf to only include the first commented out line and restart httpd` and re-run satellite-installer --scenario capsule --upgrade. Be sure to backup the original pulp.conf file to be safe.
=== HOTFIX DOWNLOAD URL ==
You can fetch the 2 tarballs as mentioned in prior comment from:
* http://people.redhat.com/~mmccune/hotfix/1388296/hotfix_katello-3.0.0.95-2.BZ1388296.el7sat.noarch.tar.bz2
* http://people.redhat.com/~mmccune/hotfix/1388296/pulp-hotfix-2.8.7.5-2.BZ_1388296.el7.tar.bz2
verify sums:
$ sha256sum hotfix_katello-3.0.0.95-2.BZ1388296.el7sat.noarch.tar.bz2
c928375ae05d1e81228e2bd126fcd242ca12b52cc4dd8e7cbd0c9fe70ef71e49 hotfix_katello-3.0.0.95-2.BZ1388296.el7sat.noarch.tar.bz2
$ sha256sum pulp-hotfix-2.8.7.5-2.BZ_1388296.el7.tar.bz2
506ec90744999d2c9f5c68f2dd5bb68cf3a2987d3fb363f1fa386d62c964a266 pulp-hotfix-2.8.7.5-2.BZ_1388296.el7.tar.bz2
Comment 11Tanya Tereshchenko
2017-04-28 08:23:40 UTC
Description of problem: Satellite/Capsule is trying to save information to the mongodb with a size larger than the BSONObj batch size is set for. Version-Release number of selected component (if applicable): Satellite 6.2.7 Capsule 6.2.7 mongodb-2.6.11-2.el7sat.x86_64 How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: From the task: "Could not save document (BSONObj size: 16797589 (0x1004F95) is invalid. Size must be between 0 and 16793600(16MB) First element: _id: \"a4e92bb7-01be-4a4d-a1ed-6193b6d915d3\")"}, "metadata"=>{"state"=>"FINISHED"}} Satellite's /var/log/mongodb/mongodb.log 2017-04-26T09:55:44.789-0400 [conn11543] warning: log line attempted (677k) over max size (10k) 2017-04-26T09:55:42.131-0400 [conn11543] warning: log line attempted (677k) over max size (10k) Capsule's /var/log/mongodb/mongodb.log 2017-04-27T10:45:47.012-0400 [conn94] warning: log line attempted (6278k) over max size (10k) 2017-04-27T10:45:46.923-0400 [conn94] warning: log line attempted (6278k) over max size (10k) 2017-04-27T10:44:06.318-0400 [conn96] warning: log line attempted (11535k) over max size (10k) 2017-04-27T10:44:00.997-0400 [conn94] warning: log line attempted (13162k) over max size (10k) Expected results: Successful sync Additional info: