Bug 1664129 - productid is not published in the content view if that is the only item which changed in the sync
Summary: productid is not published in the content view if that is the only item which...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.3.4
Hardware: All
OS: Linux
high vote
Target Milestone: Released
Assignee: Partha Aji
QA Contact: Lai
Depends On: 1659549 1664127
TreeView+ depends on / blocked
Reported: 2019-01-07 19:44 UTC by Partha Aji
Modified: 2019-10-07 16:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1664127
Last Closed: 2019-10-07 16:44:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

Comment 7 Partha Aji 2019-03-01 22:22:30 UTC
Steps to verify

0) Create a repo with the following bash script (Note it doesnot have a productid file)
mkdir $DIR
cd  $DIR
wget https://partha.fedorapeople.org/test-repos/rpm-with-productid/elephant-0.3-0.8.noarch.rpm
createrepo .
#start serving this dir
python -m SimpleHTTPServer 5050

1) Create and sync repo in sat with feed pointing to http://<fqdn>:5050 
2) put it in a CV and publish and promote to an env
3) now update the repo with a product id. Something like
cd  $DIR
echo "100000" > productid
modifyrepo  --mdtype=productid productid repodata 

4) resync, publish the CV and promote the new version
5) Go to Monitor -> Tasks view and look for the latest promote 
6) Go to dynflow console Run tab
7) Search for Actions::Katello::Repository::CheckMatchingContent
8) Expand and see check the value of match content 
 matching_content: false
 matching_content: true

The point here is that "matching_content" value is used to determine whether metadata needs to be republished. However since katello was not tracking stuff in "repodata" directory (aka Yum Metadata) it ignored the fact that a productid file got added there. This fix indexes the yum metadata and thus katello is able to track changes in the repodata directory including productid.

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