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

Re: oo-install requeriments



Yeah, it seems that it's working after the reboot. I had to reboot it myself, but now seems to be working.

Thanks so much for the help! :-)


On Mon, Oct 28, 2013 at 10:59 PM, Juanje Ojeda Croissier <juanje ojeda gmail com> wrote:
Hummmm... it didn't reboot my machine either. I'll reboot it when it finish.


On Mon, Oct 28, 2013 at 10:27 PM, Krishna Raman <kraman gmail com> wrote:
Harrison,

Does your install script restart the machine so that the services come up?

—Kr

On Oct 28, 2013, at 3:27 PM, Arunabha Ghosh <arunabha gh gmail com> wrote:

Hmm, I can't seem to get to the console, looking at the list of processes on the machine, I can't find apache running. Further doing a curl 127.0.0.1 on the machine returns 'connection refused'.

How can I verify the installation ? 


On Mon, Oct 28, 2013 at 3:03 PM, Krishna Raman <kraman gmail com> wrote:

On Oct 28, 2013, at 2:39 PM, Arunabha Ghosh <arunabha gh gmail com> wrote:

Here's what I got 

Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Error: Could not enable NetworkManager-wait-online: Execution of '/sbin/chkconfig NetworkManager-wait-online on' returned 1: error reading information on service NetworkManager-wait-online: No such file or directory

Error: /Stage[main]/Openshift_origin/Service[NetworkManager-wait-online]/enable: change from false to true failed: Could not enable NetworkManager-wait-online: Execution of '/sbin/chkconfig NetworkManager-wait-online on' returned 1: error reading information on service NetworkManager-wait-online: No such file or directory

Warning: Augeas[network-scripts](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output

Should be able to ignore these for now. NetworkManager-wait-online is not available on ec2 instances for some reason but since network init seems to happen before machine comes up, it is safe to ignore.


It looks like the deployment did not go so well, oo-accept-node -v returns a few errors

FAIL: /etc/openshift/node.conf: PUBLIC_HOSTNAME localhost should be public, not localhost
FAIL: /etc/openshift/node.conf: PUBLIC_HOSTNAME localhost resolves to ::1; expected xx.xx.xx.xx
FAIL: service cgconfig not running
FAIL: service cgred not running
FAIL: service httpd not running
FAIL: service oddjobd not running
FAIL: Could not get SELinux context for mcollective
FAIL: Could not get SELinux context for oddjobd
FAIL: Process 8421 is owned by a gear that's no longer on the system, uid: 1000
FAIL: Process 8422 is owned by a gear that's no longer on the system, uid: 1000
FAIL: no manifest in the cart repo matches /usr/libexec/openshift/cartridges/php/metadata/manifest.yml
FAIL: no manifest in the cart repo matches /usr/libexec/openshift/cartridges/perl/metadata/manifest.yml
FAIL: no manifest in the cart repo matches /usr/libexec/openshift/cartridges/jenkins-client/metadata/manifest.yml


oo-accept-* script are known to be broken at this time. They are on backlog to fix before next release.
You should still have a suable system. Can you please create an application and check?

—Kr


On Mon, Oct 28, 2013 at 2:30 PM, N. Harrison Ripps <hripps redhat com> wrote:

On Oct 28, 2013, at 17:20 , Juanje Ojeda Croissier <juanje ojeda gmail com> wrote:

> Hi, I've just try the curl install and I got this output for the Puppet part:
>
> Running Puppet deployment
>
> Command "bash -l -c 'puppet module list'" on target localhost completed.
> Skipping module installation.
> Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults

The hiera warning is not a problem.

> Error: /usr/sbin/oo-init-quota returned 1 instead of one of [0]
> Error: /Stage[main]/Openshift_origin::Node/Exec[Initialize quota DB]/returns: change from notrun to 0 failed: /usr/sbin/oo-init-quota returned 1 instead of one of [0]

I didn't get this error...

> Warning: Augeas[network-scripts](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output

I did get this error but it didn't -seem- to adversely affect the installation. Krisha, any ideas on these?

> Command "bash -l -c 'puppet apply --verbose ~/oo_install_configure_localhost.pp'" on target localhost completed.
> Command "bash -l -c 'rm ~/oo_install_configure_localhost.pp'" on target localhost completed.
> OpenShift Origin deployment completed.
>
> Installation completed.
> oo-install exited; removing temporary assets.
>
>
>
>
> On Mon, Oct 28, 2013 at 8:10 PM, N. Harrison Ripps <hripps redhat com> wrote:
> I think this issue is resolved now, and I've pushed the fix to the installer server. give another localhost installation a try and let us know if you see any other problems.
>
> Cheers,
> Harrison
>
> On Oct 28, 2013, at 11:57 , Juanje Ojeda Croissier <juanje ojeda gmail com> wrote:
>
> > Thanks to both,
> >
> > Any testing you need for that, just tell me. I'll keep trying things anyway.
> >
> >
> > On Mon, Oct 28, 2013 at 3:44 PM, Krishna Raman <kraman gmail com> wrote:
> > Hi Juanje,
> >
> > Harrison and I think we know the reason for these failures. Its basically due to how the installer sets up the Ruby environment for itself.
> > We are working on a fix for the issue. Thanks for testing out the install and bringing the failure to our attention.
> >
> > —Kr
> >
> > On Oct 28, 2013, at 7:38 AM, Krishna Raman <kraman gmail com> wrote:
> >
> >> Hi Juanje, Harrison,
> >>
> >> Im trying to reproduce this on ec2 now to debug why this may be happening. Will keep you updated.
> >>
> >> —kr
> >>
> >> On Oct 28, 2013, at 6:18 AM, N. Harrison Ripps <hripps redhat com> wrote:
> >>
> >>>
> >>> On Oct 28, 2013, at 4:46 , Juanje Ojeda Croissier <juanje ojeda gmail com> wrote:
> >>>
> >>>> Hi Harrison, thanks for your answer :-)
> >>>>
> >>>> On Mon, Oct 28, 2013 at 1:10 AM, N. Harrison Ripps <hripps redhat com> wrote:
> >>>> [...]
> >>>>>
> >>>>> So far I've tried with Fedora 18, Fedora 19, Centos 6.4.
> >>>>> I tried the Puppet method described at the blog[1], but it has some issues with links and versions. I fixed some but I couldn't make it work.
> >>>>
> >>>> Any specific error information that you can provide for the straight puppet installation path would be great. That said, oo-install uses the latest puppet scripts and part of oo-install is to write a *.pp file that configures the openshift/openshift_origin puppet module.
> >>>>
> >>>> Well, I got errors since the first line:
> >>>> $ curl -s https://nodeload.github.com/openshift/puppet-openshift_origin/legacy.tar.gz/master | tar zxf - --strip 1 '**/test'
> >>>> tar: Pattern matching characters used in file names
> >>>> tar: Use --wildcards to enable pattern matching, or --no-wildcards to suppress this warning
> >>>> tar: **/test: Not found in archive
> >>>> tar: Exiting with failure status due to previous errors
> >>>>
> >>>> Then it tries to get the Vagrant's box but it seems to be gone:
> >>>> $ wget https://mirror.openshift.com/pub/vagrant/boxes/fedora-sphericalcow.box
> >>>> --2013-10-28 08:13:41--  https://mirror.openshift.com/pub/vagrant/boxes/fedora-sphericalcow.box
> >>>> Resolving mirror.openshift.com (mirror.openshift.com)... 184.72.214.144
> >>>> Connecting to mirror.openshift.com (mirror.openshift.com)|184.72.214.144|:443... connected.
> >>>> HTTP request sent, awaiting response... 404 Not Found
> >>>> 2013-10-28 08:13:42 ERROR 404: Not Found.
> >>>>
> >>>> There is a fedora-19 box instead: https://mirror.openshift.com/pub/vagrant/boxes/fedora-19.box
> >>>>
> >>>> I made some changes and I got this working, but i got more issues that I don't remember now.
> >>>>
> >>>>> I've also tried with the oo-install gem[2] (which isn't at rubygems and you have to buid yourself, despite what the doc says), but nothing.
> >>>>
> >>>> I use the bundler as a way of bootstrapping the app in development, but I believe that in the long term, the curl-to-shell method will be the supported approach for delivery. That said, if you want to work from your own copy of the source, you can always:
> >>>> 1. clone [openshift-extras]
> >>>> 2. cd to [openshift-extras]/oo-install
> >>>> 3. bundle install
> >>>> 4. bundle exec bin/oo-install
> >>>>
> >>>> Thanks for the tip, I'll try next test.
> >>>> But probably it would be a good idea to change this at the README file, because it says to install with "gem install oo-install", which doesn't work.
> >>>
> >>> This is a great point; I will correct that this morning. The README hasn't been touched since I started the curl => shell bootstrapping work.
> >>>
> >>>>
> >>>>
> >>>> [...]
> >>>>
> >>>>> But Puppet finished without success.
> >>>>
> >>>> That's a bummer. Let's figure out what happened there.
> >>>>
> >>>>> I can provide you logs, but I guess it's better do it at the Github project, right?
> >>>>
> >>>> Actually for log files, are you familiar with the Fedora pastebin? https://paste.fedoraproject.org/ - Just throw log files there and send the URL to the list.
> >>>>
> >>>>
> >>>> Well, I used Vagrant for my testing and I was using the opscode-fedora-19 box. I got up the VM and then:
> >>>> $ sudo su -
> >>>> $ yum -y update
> >>>> $ yum -y puppet bind httpd-tools unzip
> >>>> $ sh <(curl -s http://oo-install.rhcloud.com/)
> >>>>
> >>>> Here is the output:
> >>>> https://paste.fedoraproject.org/49848/
> >>>>
> >>>> Then I ran the curl again and I got less Puppet errors:
> >>>> https://paste.fedoraproject.org/49852/
> >>>
> >>> Okay. So oo-install appears to have correctly configured Puppet, but Puppet ran into some trouble.
> >>>
> >>> Krishna, can you please have a look at these logs? Is there something the installer should be doing differently to configure the Puppet module?
> >>>
> >>>>
> >>>>> One thing I discovered is that Fedora 19 (most o my tests were with that distro) has Ruby 2.0.0 and the script search for Ruby 1.8 or 1.9.2. And later for a fixed path /opt/rh/ruby193/ which I didn't have in any distro.
> >>>>
> >>>> oo-install is "vendored everything", meaning that all of its gem requirements are packaged with it. (I took care -not- to use any gems that need to be natively compiled.) Because of the differences between Ruby 1.8.7 and Ruby 1.9.x, I vendored two sets of gems. The bootstrapper chooses which set to make available through the $GEM_PATH based on some very simple logic: "Ruby 1.8.7" or "Everything Else".
> >>>>
> >>>> That's a long way of saying, if you are using the curl-to-shell method (or using bundler) with Ruby 2.0.0 and you are running into problems, please send me some log files. I may need to vendor in gems expressly for Ruby 2.0.0, but my own recent experience with oo-install on Ruby 2.0.0 led me to believe that I wouldn't need to.
> >>>>
> >>>> Well, I'm not sure if that is the problem, but it's something I found with made me suspicious. And I remember that I tried something by hand (after the curl-to-shell had failed) that show me some errors expecting some ruby PATH I didn't have, but I don't remember now, sorry.
> >>>> If I get some info in that matter again, I'll post it here.
> >>>
> >>> That would be great. Because the curl => shell approach cannot assume that Bundler is available on the installer host, the bootstrap script does a lot of the same work that Bundler does. But when you run the installer straight from source, you need to do it through Bundler so that you get the same environment. I'll note that in the README as well.
> >>>
> >>>>
> >>>>
> >>>> Glad to have the feedback. I hope we can get you up and running!
> >>>>
> >>>> I hope so :-)
> >>>> Thanks again for your help!
> >>>>
> >>>> --
> >>>> Juanje
> >>>>
> >>>> http://about.me/juanje
> >>>
> >>>
> >>> _______________________________________________
> >>> users mailing list
> >>> users lists openshift redhat com
> >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> >>
> >
> >
> >
> >
> > --
> > Juanje
> >
> > http://about.me/juanje
> > _______________________________________________
> > users mailing list
> > users lists openshift redhat com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>
>
> --
> Juanje
>
> http://about.me/juanje


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

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




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




--
Juanje

http://about.me/juanje



--
Juanje

http://about.me/juanje

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