Bug 1485010

Summary: media_path incorrect set on Cobbler profile creation
Product: Red Hat Satellite 5 Reporter: Shannon Hughes <shughes>
Component: WebUIAssignee: Jiří Dostál <jdostal>
Status: CLOSED ERRATA QA Contact: Ales Dujicek <adujicek>
Severity: high Docs Contact:
Priority: high    
Version: 560CC: adujicek, jdostal, ktordeur, tlestach, xdmoon
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-2.0.2-116-sat Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 07:57:34 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:
Bug Depends On:    
Bug Blocks: 1450111    

Description Shannon Hughes 2017-08-24 20:17:03 UTC
Description of problem:

This looks to be a regression from Erratum RHBA-2016:1866-1

When creating a kickstart profile in 5.6 the media_path get incorrectly set to the /rhn/kickstart/ path which results in the request getting sent directly to tomcat resulting in a 404. the media path should most likely be the /ks/dist path so the url is properly handed by the rewrite rule in apache: 

RewriteRule ^/ks/dist(.*)$ /rhn/common/DownloadFile.do?url=/ks/dist$1

code commit where problem introduced in commit b3e3e1609102d4486a38d905a4a9064f8731d5d0

+++ b/java/code/src/com/redhat/rhn/manager/kickstart/cobbler/CobblerProfileCommand.java
@@ -106,6 +106,9 @@ public abstract class CobblerProfileCommand extends CobblerCommand {
 
         Map meta = profile.getKsMeta();
         meta.put("org", this.ksData.getOrg().getId());
+        if (this.ksData.getUrl().startsWith("/")) {
+            meta.put("media_path", this.ksData.getUrl());
+        }
         profile.setKsMeta(meta);

Comment 14 errata-xmlrpc 2017-12-13 07:57:34 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-2017:3444