Bug 752098 - content upload does not allow the stacking of metadata update
Summary: content upload does not allow the stacking of metadata update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: dgao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-08 14:49 UTC by dgao
Modified: 2013-09-09 16:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-21 14:26:22 UTC


Attachments (Terms of Use)

Description dgao 2011-11-08 14:49:56 UTC
pulp-admin content upload -v --repoid=package_test_repo /tmp/patb-0.1-1.noarch.rpm


* Starting Content Upload

* Performing Content Uploads to Pulp server
  Successfully uploaded [patb-0.1-1.noarch.rpm] to server
 
* Performing Repo Associations 
 
* Metadata generation has been scheduled for repository [package_test_repo] with a task id [a645807d-0a16-11e1-82df-5254009326ae]; use `pulp-admin repo generate_metadata --status` to check the status.
  Content association Complete for Repo [package_test_repo]: 
  Packages: 
    patb-0.1-1.noarch.rpm 
     
    Files: 
     None
    
* Content Upload complete.



pulp-admin content upload -v --repoid=package_test_repo /tmp/emoticons-0.1-1.noarch.rpm (com.redhat.qe.tools.SSHCommandRunner.run)
   * Starting Content Upload
   
   * Performing Content Uploads to Pulp server
   Successfully uploaded [emoticons-0.1-1.noarch.rpm] to server
   
   * Performing Repo Associations 
    (com.redhat.qe.tools.SSHCommandRunner.runCommandAndWait)
error: operation failed: Metadata generation already in process for repo [package_test_repo]

While the package is uploaded, the metadata is not updated unless it's manually kicked off. Ideally, the metadata update would be stored in a queue and execute in order.

Comment 1 Jay Dobies 2012-11-21 14:26:22 UTC
This is handled in v2 by exposing the publish call. There are no new v1 releases planned so I'm closing this out.


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