Project

General

Profile

Bug #10327

Package Upload via GUI to Products is not updating Info

Added by Christian Ehart about 7 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Package Upload via GUI to Products is not updating Info

Release:
Katello 2.2 RC3

Steps to Reproduce:
perform Package Upload "vlc-2.1.4-14.el6.x86_64" via GUI to Products (e.g. EPEL-6 in my case)

Actual results:
Number of Packages (Count) not getting updated
Package "vlc*" not found under Content Search

BUT RPM is uploaded to Pulp Repo Directory:
/var/www/html/pub/repos/CESYSTEMS/Library/custom/EPEL-6/Base_RPMs_x86_64/vlc-2.1.4-14.el6.x86_64.rpm
/var/lib/pulp/content/rpm/vlc/2.1.4/14.el6/x86_64/c2a9a6cc94ffdd05c750b27d6999d2621c71290aa89039376091c584094c2e91/vlc-2.1.4-14.el6.x86_64.rpm

Expected results:
Package "vlc*" should be found, Number (Count) of Package should be updated

Logs:
1.log = Package Upload "vlc-2.1.4-14.el6.x86_64" via GUI (Message = Content successfully uploaded)
2.log = Package Search "vlc*" via GUI
3.log = Package Upload "vlc-devel-2.1.4-14.el6.x86_64" via Hammer (no Error)
4.log = Package Search "vlc*" via GUI

Additional Info:
Package Upload via CLI (Hammer) is ok

Logs.zip Logs.zip 18.4 KB production.log in debug, messages file Christian Ehart, 04/29/2015 04:03 PM

History

#1 Updated by Eric Helms about 7 years ago

  • Legacy Backlogs Release (now unused) changed from 23 to 51

#2 Updated by Eric Helms about 7 years ago

  • Triaged changed from No to Yes

#3 Updated by Eric Helms about 7 years ago

  • Status changed from New to Need more information

I have attempted to recreate this by creating a Product with an empty repository and uploading a package to it. For me, on 2.2, the counts update properly and content search shows what I expect.

#4 Updated by Christian Ehart about 7 years ago

Issue has been resolved with 2.2.0, Ticket can be closed

#5 Updated by Eric Helms about 7 years ago

  • Status changed from Need more information to Resolved
  • Legacy Backlogs Release (now unused) deleted (51)

#6 Updated by Eric Helms about 7 years ago

  • Legacy Backlogs Release (now unused) set to 51

#7 Updated by roman plevka over 6 years ago

Issue reoccurred:

External (bugzilla) issue id: #1271586

Description of problem:
After uploading a package to the yum repo using WebGUI, the repository is not being refreshed and the package is not visible.
The package is being uploaded and added to the pulp directory tree correctly.
Same action works correctly with using Hammer CLI.
(hammer repository upload-content --product my_product_1 --organization-id 1 --name test_1_good --path mypackage.9.603.5-1.x86_64.rpm )

Version-Release number of selected component (if applicable):
  1. rpm -qa katello
    katello-2.4.0-6.nightly.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. using WebUI, create a product
2. create a yum repository within this product
3. upload a package using the 'upload package' form

Actual results:
The info about packages and errata is not being refreshed,
the package is unable to be found.

Expected results:
The uploaded packages are properly indexed and shown

Additional info:
Workaround:
you can have the repo 'refreshed' by 'syncing' it.
Even if it is a custom local repo, you can put some text into "url" field, which enables the "Sync Now" button.
The sync runs and fails (of course), but the task performs some kind of refresh.
The packages will be now shown.

#8 Updated by Bryan Kearney over 6 years ago

  • Category changed from Content Uploads to Repositories

#9 Updated by Karolis Pocius over 6 years ago

roman plevka wrote:

Workaround:
you can have the repo 'refreshed' by 'syncing' it.
Even if it is a custom local repo, you can put some text into "url" field, which enables the "Sync Now" button.
The sync runs and fails (of course), but the task performs some kind of refresh.
The packages will be now shown.

Running into the same issue using Katello 2.3.0 on CentOS 7.1

Workaround works great.

#10 Updated by Vyron Tsingaras almost 6 years ago

Issue exists on foreman 1.12.1 and katello 3.1.0.1 on CentOS 7.2
Workaround does not work.

#11 Updated by Vyron Tsingaras almost 6 years ago

What DOES work is setting the upstream URL to its own 'published at' URL. :P

Also available in: Atom PDF