Bug #19684
closed
server and foreman-proxy-content installer misses /etc/crane.conf data_dir
Added by Thomas McKay about 7 years ago.
Updated about 6 years ago.
Description
Unsure if this is just devel server and capsule or applies to production as well; all need to be confirmed working.
Using forklift, create a devel server as well as a devel capsule following the instructions here:
https://github.com/theforeman/forklift/blob/master/docs/development.md
Note that /etc/crane.conf has default data_dir value. It should have /var/lib/pulp/published/docker
Related issues
1 (1 open — 0 closed)
- Translation missing: en.field_release set to 228
I can confirm this still exists in 3.4
`data_dir: /var/lib/crane/metadata`
- Translation missing: en.field_release changed from 228 to 258
- Status changed from New to Ready For Testing
- Assignee changed from Partha Aji to Justin Sherrill
- Target version changed from 194 to 196
- Difficulty set to easy
- Pull request https://github.com/Katello/puppet-foreman_proxy_content/pull/127 added
- Translation missing: en.field_release changed from 258 to 228
- Translation missing: en.field_release changed from 228 to 258
- Status changed from Ready For Testing to Closed
- Translation missing: en.field_release changed from 258 to 267
- Translation missing: en.field_release changed from 267 to 258
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by