[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Trouble installing Origin on RHEL using comprehensive guide



Luke,

For what it's worth, I've still been having success recently installing Origin from the Puppet module using git hash d9f48a30. Is that a viable option?

And to add to a few more things that I have found in installing Origin on EL/CentOS - the issue with scaled apps (or Jenkins) might be that Release 2 uses these three variables for the path to its keys:

AUTH_PRIVKEYFILE
AUTH_PRIVKEYPASS
AUTH_PUBKEYFILE

Whereas in newer releases, they are:

AUTH_PRIV_KEY_FILE
AUTH_PRIV_KEY_PASS
AUTH_PUB_KEY_FILE

Check if you have the correct variable name in /etc/openshift/broker.conf.


On Fri, Oct 18, 2013 at 10:26 AM, Luke Meyer <lmeyer redhat com> wrote:
I think the comprehensive guide has seen Origin change out from underneath it. In response to several users reporting problems using it, I ran through an all-in-one install on RHEL 6 and observed numerous issues.

The main one I want to ask about is the SCL-ization of mcollective. It looks like the packages are still requiring mcollective-common, mcollective-client, and that we're installing mcollective. There doesn't seem to be a lot in these so maybe it can work... but shouldn't we be using the ruby193- versions of these on EL?

Also wondering why ruby193-rubygem-haml-4.0.3 is in origin-deps -- both consoles choke on this.

With the puppet configs in flux it's hard to set up a comparable system to check against.

Other notes I made as I was going along... in case they might help someone else (accuracy far from guaranteed):
----------------------------------------------------------
Need the "optional" channel, but this is not mentioned!

ruby193 wouldn't install directly. Had to work around dep issue with:
yum install ruby193-rubygem-json-1.7.3-5.el6.x86_64

There was no /usr/bin/mongo - had to also install mongodb

admin mongo pass does not need to be same as openshift pass

RHEL for mcollective client - mcollective has been scl-ized:

yum install -y ruby193-mcollective-client
cat <<EOF > /opt/rh/ruby193/root/etc/mcollective/client.cfg


Broker packages:
There is no  rubygem-openshift-origin-dns-avahi

openshift-origin-broker-util requires mcollective-client; should require ruby193-mcollective-client. This chain of dependencies leads to requiring rubygems, which requires enabling optional. But it'd be better if the deps were right.

broker required ruby193-rubygem-poltergeist

with admin-console:
Could not find gem 'haml (~> 3.1.7) ruby', which is required by gem 'openshift-origin-admin-console (>= 0) ruby', in any of the sources.
haml v. 4.0.3 is shipped which... probably works? but doesn't match the gemspec
I had to remove this and install ruby193-rubygem-haml-3.1.7 explicitly
Why are we shipping the new version? Or is this EPEL...
Same problem for console

oo-register-dns doesn't really need a keyfile

9.2 SSH Key Auth "This will enable operations to work from inside of OpenShift Origin without requiring a password." No - this will enable moving gears without a password.

http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#configure-mcollective
"Configure the MCollective client to communicate with the broker application service." => "Configure the MCollective server to communicate with the messaging service on the broker host."

rpm -ql openshift-origin-msg-node-mcollective
/etc/cron.minutely/openshift-facts
/opt/rh/ruby193/root/usr/libexec/mcollective/mcollective/agent/openshift.rb
However, the requires is for "mcollective" which installs the standard mcollective
I added ruby193-mcollective too. But by starting the "mcollective" service what do I get?

http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#enable-control-groups-cgroups
Mentions openshift-cgroups which... no longer exists?

http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#configuring-the-port-proxy
Isn't the port proxy now openshift-iptables-port-proxy?

http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#the-web-console
not mentioned: SESSION_SECRET must be set in /etc/openshift/console.conf

abrt-addon-python has a known conflict with openshift-origin-cartridge-python (https://bugzilla.redhat.com/show_bug.cgi?id=907449)
yum remove abrt-addon-python

On creating scaled app I'm getting:
Unable to complete the requested operation due to: No such file or directory - /var/www/openshift/broker/config/server_pub.pem.
I think maybe the location for the scaling/Jenkins keys has moved - need to look into this.

_______________________________________________
dev mailing list
dev lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev



--
Thanks,

Steven Merrill
steven merrill gmail com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]