Bug 693742 - File opening traceback is returned for sync status API call after sync spam
Summary: File opening traceback is returned for sync status API call after sync spam
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: z_other
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Sprint 22
Assignee: John Matthews
QA Contact: dgao
URL:
Whiteboard:
Depends On:
Blocks: verified-to-close
TreeView+ depends on / blocked
 
Reported: 2011-04-05 13:38 UTC by dgao
Modified: 2011-08-16 12:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-16 12:07:29 UTC
Embargoed:


Attachments (Terms of Use)

Description dgao 2011-04-05 13:38:44 UTC
Scenario:

After 100x sync calls

After ~5 sync status calls

This is returned from the repo status API call:


{
  "id": "777c986e-5f5a-11e0-9092-5452004fdd6d",
  "progress": {
    "num_success": 7,
    "details": {
      "rpm": {
        "num_success": 7,
        "num_error": 0,
        "size_left": 0,
        "total_size_bytes": 3170837,
        "total_count": 7,
        "items_left": 0
      }
    },
    "error_details": [

    ],
    "item_name": null,
    "status": "FINISHED",
    "num_error": 0,
    "size_left": 0,
    "size_total": 3170837,
    "num_download": 0,
    "step": "Processing Errata",
    "items_left": 0,
    "items_total": 7
  },
  "result": null,
  "status_path": "/pulp/api/repositories/api_test_repo/sync/777c986e-5f5a-11e0-9092-5452004fdd6d/",
  "scheduled_time": 0,
  "traceback": [
    "Traceback (most recent call last):\n",
    "  File \"/usr/lib/python2.6/site-packages/pulp/server/tasking/task.py\", line 131, in run\n    result = self.callable(*self.args, **self.kwargs)\n",
    "  File \"/usr/lib/python2.6/site-packages/pulp/server/api/repo.py\", line 1524, in _sync\n    self.delete_errata(id, old_errata)\n",
    "  File \"/usr/lib/python2.6/site-packages/pulp/server/api/repo.py\", line 1104, in delete_errata\n    updateinfo.generate_updateinfo(repo)\n",
    "  File \"/usr/lib/python2.6/site-packages/pulp/server/updateinfo.py\", line 163, in generate_updateinfo\n    updateinfo_path)\n",
    "  File \"/usr/lib/python2.6/site-packages/pulp/server/util.py\", line 395, in modify_repo\n    raise ModifyRepoError(out)\n",
    "ModifyRepoError: Wrote: /var/lib/pulp/repos/pub/updates/repodata/updateinfo.xml.gz\nTraceback (most recent call last):\n  File \"/usr/share/createrepo/modifyrepo.py\", line 150, in <module>\n    repomd.add(sys.argv[1])\n  File \"/usr/share/createrepo/modifyrepo.py\", line 94, in add\n    csum, destmd = checksum_and_rename(destmd, self.checksum_type)\n  File \"/usr/lib/python2.6/site-packages/createrepo/utils.py\", line 106, in checksum_and_rename\n    csum = misc.checksum(sumtype, fn_path)\n  File \"/usr/lib/python2.6/site-packages/yum/misc.py\", line 338, in checksum\n    raise MiscError, 'Error opening file for checksum: %s' % file\nyum.Errors.MiscError: Error opening file for checksum: /var/lib/pulp/repos/pub/updates/repodata/updateinfo.xml.gz\n"
  ],
  "finish_time": "1301990301",
  "exception": "ModifyRepoError()",
  "state": "error",
  "method_name": "_sync",
  "start_time": "1301990297"
}

Comment 1 John Matthews 2011-04-11 13:07:36 UTC
Issue described here was related to multiple syncs operating at the same time on the same exact repo.  We do not want to allow that behavior.

Below commit will limit only 1 sync per repo at the same time.
http://git.fedorahosted.org/git/?p=pulp.git;a=commitdiff;h=33ef2654804e6f9a0b2bbd575e493f9a9e206f1a

Comment 2 Jeff Ortel 2011-04-11 14:08:10 UTC
build: 0.162

Comment 3 Jay Dobies 2011-04-13 19:23:05 UTC
Fixed in build 0.163.

Comment 4 dgao 2011-04-29 14:13:49 UTC
This no longer seems to be happening when automation run this scenario, closing.

Comment 5 Preethi Thomas 2011-08-16 12:07:29 UTC
Closing with Community Release 15

pulp-0.0.223-4.

Comment 6 Preethi Thomas 2011-08-16 12:21:03 UTC
Closing with Community Release 15

pulp-0.0.223-4.


Note You need to log in before you can comment on or make changes to this bug.