That’s very strange, looks like it isn’t switching to the SCL (software
colletion) correctly.
What’s the output of:
bash -x /usr/sbin/foreman-rake plugins
scl enable ruby193 “ruby -v”
/usr/bin/ruby193-rake --version
/usr/bin/ruby193-ruby -v
I’m concerned that you’re downloading software collections from
people.redhat.com, that doesn’t appear official. You may have
somebody’s random build, or alpha/beta version installed from a test
repository.
If you’re using RHEL itself, then you should have access to software
collections as part of the supported OS.
https://access.redhat.com/site/solutions/472793 has more information.
There are also unsupported versions available from
softwarecollections.org, which we use on CentOS and RHEL clones:
https://www.softwarecollections.org/en/scls/rhscl/ruby193/ and
https://www.softwarecollections.org/en/scls/rhscl/v8314/
–
Dominic Cleal
Red Hat Engineering
On 07/01/15 15:01, Peter Berghold wrote:
Failures I’m seeing when running foreman-rake db:migrate
short version
/usr/sbin/foreman-rake db:migrate
(in /usr/share/foreman)
rake aborted!
no such file to load – apipie/middleware/checksum_in_headers
/usr/share/foreman/Rakefile:1
(See full trace by running task with --trace)
and with --trace
/usr/sbin/foreman-rake --trace db:migrate
(in /usr/share/foreman)
rake aborted!
no such file to load – apipie/middleware/checksum_in_headers
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:inrequire’
/usr/share/foreman/config/application.rb:2
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:inrequire’
/usr/share/foreman/Rakefile:1
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2382:in load' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2382:inraw_load_rakefile’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in
load_rakefile' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2067:instandard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2015:in
load_rakefile' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1999:inrun’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2067:in
standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1997:inrun’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
/usr/bin/ruby193-rake:19:in `load’
/usr/bin/ruby193-rake:19
On Wed, Jan 7, 2015 at 9:53 AM, Peter Berghold <salty.cowdawg@gmail.com > > mailto:salty.cowdawg@gmail.com> wrote:
I thought I had been clear before, but here the process is in its
entirety:
I copied the following repositories in their entirety:
dl.fedoraproject.org <http://dl.fedoraproject.org> (for EPEL)
people.redhat.com <http://people.redhat.com> (for Ruby)
yum.puppetlabs.com <http://yum.puppetlabs.com> (puppet and
puppet-deps)
yum.theforeman.org <http://yum.theforeman.org> (foreman and
foreman-deps)
I extracted out the pieces (RPMS only) pertaining to RHEL 6 x86_64
and put them in a staging directory on my personal server, tar-ed
them up and sneaker-netted them to my server at work. Untarred the
data into
puppet-deps
puppet
foreman
foreman-deps
ruby
epel
ran "createrepo" in each and configured them under /etc/yum.repos.d
on the target system.
When running the foreman-installer this morning I noticed that
foreman-cli and foreman-postgresql fail to install. When I install
them manually (yum -y install <blah>) they install fine.
However that said I am now seeing failures (I'll post seperately)
when running /usr/sbin/foreman-rake db:migrate and /usr/sbin/foreman
db:seed
On Wed, Jan 7, 2015 at 9:04 AM, Lukas Zapletal <lzap@redhat.com > > <mailto:lzap@redhat.com>> wrote:
> Not only is there a proxy involved by the proxy is set up to
not allow
> downloads of binary files such as tarballs, RPMs etc.
I am afraid we can't help you until you fully specify all the
steps you
followed to workaround this limitation.
--
Later,
Lukas #lzap Zapletal
--
You received this message because you are subscribed to the
Google Groups "Foreman users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
To post to this group, send email to
foreman-users@googlegroups.com
<mailto:foreman-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/d/optout.
--
Peter L. Berghold Salty.Cowdawg@gmail.com
<mailto:Salty.Cowdawg@gmail.com>
h <http://blog.berghold.net>ttp://science-fiction.berghold.net
<http://science-fiction.berghold.net>
–
Peter L. Berghold Salty.Cowdawg@gmail.com
mailto:Salty.Cowdawg@gmail.com
h http://blog.berghold.netttp://science-fiction.berghold.net
http://science-fiction.berghold.net
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
