Description of problem: If user successfully creates a yum repo on rhq, associates a platform and enables local repo on that system, running `yum list|grep rhq` shows a bunch of entries in the repo that apparently have no package name. Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. Create a CP; sync a small channel, i.e., one of the tools channels. 2. Register a platform to your server; associate it with the repo. 3. $platform > Inventory > Connection; enable "Enable Internal Yum Server" 4. From within a terminal on the target $platform, `yum list |grep rhq` Actual results: [...] auto-kickstart-ks-rhel-i386-as-4-u2.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-i386-as-4-u3.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-i386-as-4-u4.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-i386-as-4-u5.noarch 1.14-1.el4 rhq auto-kickstart-ks-rhel-i386-as-4-u6.noarch 1.14-3.el4 rhq auto-kickstart-ks-rhel-i386-as-4-u7.noarch 1.14-4.el4 rhq auto-kickstart-ks-rhel-i386-as-4-u8.noarch 1.14-5.el4 rhq 1.13-4.el5 rhq 1.13-4.el5 rhq 1.13-4.el5 rhq 1.13-4.el5 rhq 1.13-4.el5 rhq 1.13-4.el5 rhq 1.13-4.el5 rhq 1.14-2.el4 rhq auto-kickstart-ks-rhel-i386-es-3.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-i386-es-3-u1.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-i386-es-3-u2.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-i386-es-3-u3.noarch 1.13-4.el5 rhq [...] Expected results: Correct data in repo xml and/or `yum list` output Additional info:
After investigating this issue, I do not believe it is an issue with RHQ. I believe the blank names are caused because some of the package names are quite long and they cause a newline char to be printed after the package name, this causes the second line to contain the 'rhq' picked up by grep. Example, using the rhel5 i386 tools channel 1) "yum list > filelist.txt" We can see the new line char by doing a "cat -A" and looking for "$". Notice that normally we see the "$" at the end of the line, but for several packages of long package name we see the "$" directly after the package name. Example: tail -n 200 filelist.txt | cat -A <snip> auto-kickstart-ks-rhel-i386-as-4-u6.noarch 1.14-3.el4 rhq $ auto-kickstart-ks-rhel-i386-as-4-u7.noarch 1.14-4.el4 rhq $ auto-kickstart-ks-rhel-i386-as-4-u8.noarch 1.14-5.el4 rhq $ auto-kickstart-ks-rhel-i386-desktop-3.noarch 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u3.noarch$ 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u4.noarch$ 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u5.noarch$ 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u6.noarch$ 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u7.noarch$ 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u8.noarch$ 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-desktop-3-u9.noarch$ 1.14-2.el4 rhq $ auto-kickstart-ks-rhel-i386-es-3.noarch 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-es-3-u1.noarch 1.13-4.el5 rhq $ auto-kickstart-ks-rhel-i386-es-3-u2.noarch 1.13-4.el5 rhq $ Another way to see this is to do: (This will print one line of text prior to each match with grep) yum list | grep -B 1 rhq auto-kickstart-ks-rhel-x86_64-as-4-u6.noarch 1.14-3.el4 rhq auto-kickstart-ks-rhel-x86_64-as-4-u7.noarch 1.14-4.el4 rhq auto-kickstart-ks-rhel-x86_64-as-4-u8.noarch 1.14-5.el4 rhq auto-kickstart-ks-rhel-x86_64-desktop-3.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-desktop-3-u3.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-desktop-3-u4.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-desktop-3-u5.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-desktop-3-u6.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-desktop-3-u7.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-desktop-3-u8.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-es-3-u2.noarch 1.13-4.el5 rhq auto-kickstart-ks-rhel-x86_64-es-3-u3.noarch 1.13-4.el5 rhq Marking as ON_QA so QA can determine if they want to close this.
QA Closing