[katello-devel] Foreman on Rails32 is ready

Ivan Necas inecas at redhat.com
Mon Apr 8 13:17:20 UTC 2013 


----- Original Message -----
> Horray! I'm running Katello & Foreman from scl ruby193 on Rails 32.

Still not finished though: I run my tests on my local machine, where previous packages
were already installed. With a machine provisioned from scratch, katello-configure
fails, because some actions (such as rake db:migrate) don't run in scl.

We're looking into it right now.

-- Ivan

> 
> The only problem left is getting:
> 
> err: /Stage[main]/Katello::Service/Service[katello-jobs]: Could not evaluate:
> undefined method `[]=' for nil:NilClass
> 
> from katello configure, rerunning katello-configure works ok, investigating…
> 
> -- Ivan
> 
> ----- Original Message -----
> > 
> > 
> > ----- Original Message -----
> > > 
> > > 
> > > ----- Original Message -----
> > > > First issue found: yum update end up with:
> > > > 
> > > > Error: Package: pulp-rpm-plugins-2.1.0-0.26.beta.1.el6.noarch (@pulp)
> > > >            Requires: pulp-server = 2.1.0-0.26.beta.1.el6
> > > >            Removing: pulp-server-2.1.0-0.26.beta.1.el6.noarch (@pulp)
> > > >                pulp-server = 2.1.0-0.26.beta.1.el6
> > > >            Updated By: pulp-server-2.1.1-1.el6.noarch (pulp)
> > > >                pulp-server = 2.1.1-1.el6
> > > > Error: Package: katello-glue-pulp-1.3.14-1.git.1165.7f13583.el6.noarch
> > > > (katello)
> > > > 
> > > >            Requires: ruby193-rubygem(runcible) >= 0.4.1
> > > >            Available: ruby193-rubygem-runcible-0.3.3-4.el6.noarch
> > > >            (katello)
> > > >                ruby193-rubygem(runcible) = 0.3.3
> > > > Error: Package: python-pulp-rpm-common-2.1.0-0.26.beta.1.el6.noarch
> > > > (@pulp)
> > > >            Requires: python-pulp-common = 2.1.0-0.26.beta.1.el6
> > > >            Removing: python-pulp-common-2.1.0-0.26.beta.1.el6.noarch
> > > >            (@pulp)
> > > >                python-pulp-common = 2.1.0-0.26.beta.1.el6
> > > >            Updated By: python-pulp-common-2.1.1-1.el6.noarch (pulp)
> > > >                python-pulp-common = 2.1.1-1.el6
> > > > 
> > > > Solving…
> > > 
> > > This were two separate problems:
> > > 
> > > ruby193-rubygem(runcible)
> > >   the scl version of our spec had unresolved conflicts, I've fixed them
> > >   locally and rebuild the package. I will push the fixes to the remote
> > >   repo
> > >   once I will get write
> > >   access there (If I'm trusted enough :) Eric, Justin?), the build is
> > >   here
> > > 
> > >   http://koji.katello.org/koji/buildinfo?buildID=3845
> > > 
> > > pulp-rpm-plugins
> > >   Mirek built a pulp-2.1.1, but pulp-rpm needed to be built as well, as
> > >   Mirek, I've tagged the pulp-rpm
> > >   locally so far, as a quickfix, we will resolve the issue properly with
> > >   Pulp
> > >   guys,
> > > 
> > >   the builds are here:
> > >   http://koji.katello.org/koji/buildinfo?buildID=3847
> > >                        http://koji.katello.org/koji/buildinfo?buildID=3848
> > > 
> > > Solved once new packages arrive to our yum repo.
> > > 
> > > Right now I've run into some other issues with katello-configure:
> > > 
> > > err: /Stage[main]/Katello::Service/Service[katello-jobs]/ensure: change
> > > from
> > > stop
> > > ped to running failed: Could not start Service[katello-jobs]: Execution
> > > of
> > > '/sbi
> > > n/service katello-jobs start' returned 1:  at
> > > /usr/share/katello/install/puppet/
> > > modules/katello/manifests/service.pp:21
> > > 
> > > and
> > > 
> > > err: /Stage[main]/Katello::Service/Service[katello-jobs]/ensure: change
> > > from
> > > stop
> > > ped to running failed: Could not start Service[katello-jobs]: Execution
> > > of
> > > '/sbi
> > > n/service katello-jobs start' returned 1:  at
> > > /usr/share/katello/install/puppet/
> > > modules/katello/manifests/service.pp:21
> > > 
> > > Investigating…
> > 
> > The problem with staring katello is fixed here - missing dep on some
> > JavaScript engine:
> > 
> > https://github.com/Katello/katello/pull/1870
> > 
> > Please ACK
> > 
> > -- Ivan
> > 
> > > 
> > > -- Ivan
> > > 
> > > > 
> > > > -- Ivan
> > > > 
> > > > ----- Original Message -----
> > > > > Just so we are all on the same page - Monday morning European time,
> > > > > Mirek
> > > > > you
> > > > > are going to:
> > > > > 
> > > > > 1) Change "Gemfile" to require "gem 'rails', '~> 3.2.8'
> > > > > 2) Open a pull request to change such
> > > > > 3) Ivan will varify and ACK if appropriate
> > > > > 4) Send an email warning all developers of the change that
> > > > > a) on RHEL, for development, SCL commands must be used
> > > > > b) on Fedora < 18, RVM with 1.9.3 and a new gemset must be created
> > > > > and
> > > > > used
> > > > > 
> > > > > If I missed anything please and add and re-clarify the entire list so
> > > > > that
> > > > > we
> > > > > are all clear.
> > > > > 
> > > > > -Eric
> > > > > 
> > > > > On Thu, Apr 4, 2013 at 10:18 AM, Miroslav Suchý < msuchy at redhat.com >
> > > > > wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > On 04/04/2013 02:36 PM, Eric Helms wrote:
> > > > > 
> > > > > 
> > > > > 2) Monday morning Brno or EST and who is going to move the Gemfile
> > > > > and
> > > > > open the pull request? (They should also remove the 1.8.7 and non
> > > > > Rails
> > > > > 3.2 travis builds)
> > > > > 3) Should we do this prior to Monday so that Monday morning nightlies
> > > > > are on 3.2?
> > > > > 
> > > > > Yes, we can prepare as much on Friday. And Brno will pull trigger on
> > > > > European
> > > > > morning. We will try to fix as much problems (I'm sure there will be
> > > > > some).
> > > > > But I will bet that Monday will be broken anyway. So US will continue
> > > > > in
> > > > > fixing...
> > > > > I do not think we are able to prepare nightlies on Monday morning
> > > > > (definitely
> > > > > not in EU time-zone, maybe in US time-zone). Of course unless you
> > > > > volunteer
> > > > > to work during weekend :))
> > > > > 
> > > > > 
> > > > > --
> > > > > Miroslav Suchy
> > > > > Red Hat Systems Management Engineering
> > > > > 
> > > > > ______________________________ _________________
> > > > > katello-devel mailing list
> > > > > katello-devel at redhat.com
> > > > > https://www.redhat.com/ mailman/listinfo/katello-devel
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > katello-devel mailing list
> > > > > katello-devel at redhat.com
> > > > > https://www.redhat.com/mailman/listinfo/katello-devel
> > > > 
> > > > _______________________________________________
> > > > katello-devel mailing list
> > > > katello-devel at redhat.com
> > > > https://www.redhat.com/mailman/listinfo/katello-devel
> > > 
> > > _______________________________________________
> > > katello-devel mailing list
> > > katello-devel at redhat.com
> > > https://www.redhat.com/mailman/listinfo/katello-devel
> > 
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel

More information about the katello-devel mailing list