Bug 1004805
| Summary: | pulp-dev.py script doesn't handle F19 | ||
|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | Jay Dobies <jason.dobies> |
| Component: | z_other | Assignee: | Michael Hrivnak <mhrivnak> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Preethi Thomas <pthomas> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | Master | CC: | mhrivnak, skarmark |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-09 14:31:04 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: | |||
need to now only check for whether this is fedora, any version. This is only a problem in dev environment, so not sure why this was aligned to 2.2 and on high priority. Moving it to 2.3 and medium priority. build: 2.3.0-0.18.beta Verified the PR and also the output of pulp-dev.py - creating link: /etc/httpd/conf.d/pulp.conf pointing to /home/skarmark/git/pulp/server/etc/httpd/conf.d/pulp_apache_24.conf Pulp 2.3 released. |
With F18, the pulp-dev.py script was modified to symlink a specific HTTP conf file. This check is for F18 explicitly and not a greater than check, so F19 dev installs are broken. Below is the relevant snippet from pulp-dev.py: # Get links for httpd conf files according to distro pre_f18_apache_conf = ('server/etc/httpd/conf.d/pulp.conf', '/etc/httpd/conf.d/pulp.conf') f18_apache_conf = ('server/etc/httpd/conf.d/pulp_f18.conf', '/etc/httpd/conf.d/pulp.conf') s, n, r, v, m = os.uname() if 'fc18' in r: src, dst = f18_apache_conf else: src, dst = pre_f18_apache_conf links.append((src, dst)) The RPM spec is correct, it checks for version >= 18, so this is only an issue for developer installs.