Bug 1717071

Summary: rhel-x86_64-appstream-8 channel causes cobbler-sync-default to look for non-existent kickstart on Satellite 5.8
Product: Red Hat Satellite 5 Reporter: Ricardo Santamaria <risantam>
Component: ProvisioningAssignee: Michael Mráka <mmraka>
Status: CLOSED ERRATA QA Contact: Radovan Drazny <rdrazny>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 580CC: bishop, rdrazny, sraut, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-2.5.14-133-sat Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-18 02:49:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ricardo Santamaria 2019-06-04 16:12:42 UTC 
Description of problem:

On Satellite 5.8 syncing both rhel-x86_64-baseos-8 and rhel-x86_64-appstream-8 causes countless messages in rhn_taskomatic_daemon.log looking for kickstart tree for the appstream channel. found in /var/satellite/rhn/kickstart/

Version-Release number of selected component (if applicable):
Satellite schema: 5.8.0.51-1.el6sat
cdn-sync-mappings-2.54-1.el6sat.noarch

How reproducible:


Steps to Reproduce:
1. Sync both baseos and appstream RHEL 8 channels cdn-sync -c rhel-x86_64-baseos-8 -c rhel-x86_64-appstream-8
2. Monitor /var/log/rhn/rhn_taskomatic_deamon.log as cobbler-sync-default task schedule runs every '0 * * * * ?' 




Actual results:

]# grep "Could not sync tree ks-rhel-x86_64-appstream-8-8.0" /var/log/rhn/rhn_taskomatic_daemon.log | wc -l
20765

]# grep "Could not sync tree ks-rhel-x86_64-appstream-8-8.0" /var/log/rhn/rhn_taskomatic_daemon.log | tail 
INFO   | jvm 1    | 2019/06/04 11:53:00 | 2019-06-04 11:53:00,148 [DefaultQuartzScheduler_Worker-8] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 11:54:00 | 2019-06-04 11:54:00,159 [DefaultQuartzScheduler_Worker-2] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 11:55:00 | 2019-06-04 11:55:00,188 [DefaultQuartzScheduler_Worker-5] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 11:56:00 | 2019-06-04 11:56:00,148 [DefaultQuartzScheduler_Worker-4] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 11:57:00 | 2019-06-04 11:57:00,159 [DefaultQuartzScheduler_Worker-1] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 11:58:00 | 2019-06-04 11:58:00,153 [DefaultQuartzScheduler_Worker-3] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 11:59:00 | 2019-06-04 11:59:00,167 [DefaultQuartzScheduler_Worker-2] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 12:00:00 | 2019-06-04 12:00:00,326 [DefaultQuartzScheduler_Worker-9] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 12:01:00 | 2019-06-04 12:01:00,155 [DefaultQuartzScheduler_Worker-7] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0
INFO   | jvm 1    | 2019/06/04 12:02:00 | 2019-06-04 12:02:00,231 [DefaultQuartzScheduler_Worker-8] WARN  com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - Could not sync tree ks-rhel-x86_64-appstream-8-8.0


Expected results:
 the expectation is to sync both - baseos and appstream ks repositories
 if both are synced the error/message cobbler msg does not disappear
 this does not happen. 

Additional info:

The parent has the kickstart tree in it as seen in 

/var/satellite/rhn/kickstart/ks-rhel-x86_64-baseos-8-8.0

but none in 

/var/satellite/rhn/kickstart/ks-rhel-x86_64-appstream-8-8.0

]# ls /var/satellite/rhn/kickstart | grep 8-8
ks-rhel-x86_64-appstream-8-8.0
ks-rhel-x86_64-baseos-8-8.0
Comment 2 Bishop Clark 2019-06-23 17:51:06 UTC 
In case it's relevant, here's the current set of installed java packages containing the CobblerDistroSyncCommand , as found by grep:

# rpm -qa --qf "%{name}\n" \
| egrep -i 'satellite|spacewalk|cdn-sync|java'- \
| xargs rpm -ql \
| xargs -n1 echo \
| xargs -n1 -iHH grep -il CobblerDistroSyncCommand  /dev/null HH 2>/dev/null \
| xargs rpm -qf

spacewalk-java-2.5.14-132.el6sat.noarch
spacewalk-java-lib-2.5.14-132.el6sat.noarch


(yeah, I could make it better; fgrep et al.  Also the echo bit avoids EOL voodoo)
Comment 3 Michael Mráka 2019-07-08 12:56:23 UTC 
Fixed in upstream spacewalk git by
commit 1363587f90aeafe29e1a9cc9f8c3bcfa1b66dcce
    1717071 - appstream repos are not synced to cobbler
Comment 6 Michael Mráka 2019-08-07 09:52:04 UTC 
Backported to SATELLITE-5.8 as
commit d17d8e1ee59416d996ce6952e7e050caf2a9ff45
    1717071 - appstream repos are not synced to cobbler
Comment 8 Radovan Drazny 2019-08-13 16:27:53 UTC 
Reproduced with spacewalk-java-2.5.14-132 using the initial report. After update to spacewalk-java-2.5.14-133 and resyncing RHEL8 channels there are no error messages in the Taskomatic log.
Comment 10 errata-xmlrpc 2019-09-18 02:49:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2783
Comment 16 Tomas Lestach 2019-10-07 12:35:46 UTC 
Newly opened bug for reference: Bug 1757198