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

Re: oo-install requeriments



Can you please compress and send me your /var/log/openshift/ and /var/log/mcollective.log files.

—Kr

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

Thanks a lot Jason, that works ....

I can go to the settings page now. However /console/application_types seems to be broken now (clicking on "create your first application now"). I'm getting an error page with 

An error has occurred

You can try refreshing the page, if the problem is temporary.

You can also try the following:

Reference #41309618faf3cdb9715197e37cae17cb



On Tue, Oct 29, 2013 at 2:03 PM, N. Harrison Ripps <hripps redhat com> wrote:

On Oct 29, 2013, at 16:58 , Jason DeTiberus <jdetiber redhat com> wrote:

> I found a couple of issues with the resulting configs, the following
> commands should get you a working console:
>
> # sed -i s/^CONSOLE_SECURITY=.*/CONSOLE_SECURITY=remote_user/ /etc/openshift/console.conf
> # mv /var/www/openshift/console/httpd/conf.d/openshift-origin-auth-remote-user-basic.conf.sample \ /var/www/openshift/console/httpd/conf.d/openshift-origin-auth-remote-user-basic.conf
> # service openshift-console restart

Thanks, Jason!

Arunabha, Jason's instructions above will sort out your existing Origin deployment. We're working on replacing the copy of our puppet module on puppetlabs so that this is no longer a problem.

--Harrison

>
> --
> Jason DeTiberus
>
> On 29/10/13 12:07 -0700, Arunabha Ghosh wrote:
>>  Thank you. If you need any logs etc, please let me know.
>>
>>  On Tue, Oct 29, 2013 at 11:09 AM, N. Harrison Ripps
>>  <[1]hripps redhat com> wrote:
>>
>>    Hey there--
>>
>>  On Oct 29, 2013, at 13:26 , Arunabha Ghosh <[2]arunabha gh gmail com>
>>  wrote:
>>  > Really hoping someone can help me out with this, its so frustrating
>>  to have a working OpenShift installation and not be able to use it.
>>  >
>>  > Something is definitely wrong with the install. I created a new
>>  htpasswd file with a new account using htpasswd -c
>>  /etc/openshift/htpasswd demo
>>  >
>>  > I can login to the console with the demo acocunt but it does not work
>>  on the auth dialog boxes that pop up when any link in the console is
>>  clicked.
>>
>>    Krishna and I are looking into this. Hopefully we will have an
>>    answer for you soon.
>>    --Harrison
>>
>>  >
>>  >
>>  > On Mon, Oct 28, 2013 at 6:24 PM, Arunabha Ghosh
>>  <[3]arunabha gh gmail com> wrote:
>>  > Yep, I'm in the same boat, no username/password combination seems to
>>  work. Sigh !!
>>  >
>>  >
>>  > On Mon, Oct 28, 2013 at 6:22 PM, Juanje Ojeda Croissier
>>  <[4]juanje ojeda gmail com> wrote:
>>  > Well, it seems like I talk too soon. I had some issues.
>>  >
>>  > Arunabha, I login into the /console with admin/admin (I'm not sure
>>  why this worked in the first place...), but when I try to go to
>>  Settings or /broker it ask me the user/pass again.
>>  > Then admin/admin doesn't work anymore. I tried demo/changeme, but
>>  nothing.
>>  >
>>  > If I go directly to [5]http://broker.example.com/broker it ask me the
>>  user/pass and If I login with demo/changeme, it seems to work but I got
>>  a HTTP 500 error.
>>  > Here is the error I found at the log
>>  /var/log/openshift/broker/httpd/error_log:
>>  > [6]https://paste.fedoraproject.org/50083/
>>  >
>>  > btw, I also found a weird /etc/hosts content. My file after the
>>  installation was looking like this:
>>  >
>>  > 127.0.0.1   [7]broker.example.com broker [8]broker.example.com broker
>>  [9]broker.example.com broker localhost localhost.localdomain localhost4
>>  localhost4.localdomain4
>>  > ::1         localhost localhost.localdomain localhost6
>>  localhost6.localdomain6
>>  >
>>  > As you can see the configured hostname is repeated a few times.
>>  >
>>  >
>>  > On Mon, Oct 28, 2013 at 11:30 PM, Arunabha Ghosh
>>  <[10]arunabha gh gmail com> wrote:
>>  > Juanje, what username/password are you using ?
>>  >
>>  >
>>  > On Mon, Oct 28, 2013 at 4:27 PM, Juanje Ojeda Croissier
>>  <[11]juanje ojeda gmail com> wrote:
>>  > 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
>>  <[12]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
>>  <[13]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
>>  <[14]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
>>  <[15]kraman gmail com> wrote:
>>  >>
>>  >> On Oct 28, 2013, at 2:39 PM, Arunabha Ghosh
>>  <[16]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]/enabl
>>  e: 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
>>  <[17]hripps redhat com> wrote:
>>  >>>
>>  >>> On Oct 28, 2013, at 17:20 , Juanje Ojeda Croissier
>>  <[18]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
>>  <[19]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
>>  <[20]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
>>  <[21]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
>>  <[22]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
>>  <[23]hripps redhat com> wrote:
>>  >>> > >>
>>  >>> > >>>
>>  >>> > >>> On Oct 28, 2013, at 4:46 , Juanje Ojeda Croissier
>>  <[24]juanje ojeda gmail com> wrote:
>>  >>> > >>>
>>  >>> > >>>> Hi Harrison, thanks for your answer :-)
>>  >>> > >>>>
>>  >>> > >>>> On Mon, Oct 28, 2013 at 1:10 AM, N. Harrison Ripps
>>  <[25]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
>>  [26]https://nodeload.github.com/openshift/puppet-openshift_origin/legac
>>  y.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
>>  [27]https://mirror.openshift.com/pub/vagrant/boxes/fedora-sphericalcow.
>>  box
>>  >>> > >>>> --2013-10-28 08:13:41--
>>  [28]https://mirror.openshift.com/pub/vagrant/boxes/fedora-sphericalcow.
>>  box
>>  >>> > >>>> Resolving [29]mirror.openshift.com
>>  ([30]mirror.openshift.com)... [31]184.72.214.144
>>  >>> > >>>> Connecting to [32]mirror.openshift.com
>>  ([33]mirror.openshift.com)|[34]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:
>>  [35]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? [36]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 [37]http://oo-install.rhcloud.com/)
>>  >>> > >>>>
>>  >>> > >>>> Here is the output:
>>  >>> > >>>> [38]https://paste.fedoraproject.org/49848/
>>  >>> > >>>>
>>  >>> > >>>> Then I ran the curl again and I got less Puppet errors:
>>  >>> > >>>> [39]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
>>  >>> > >>>>
>>  >>> > >>>> [40]http://about.me/juanje
>>  >>> > >>>
>>  >>> > >>>
>>  >>> > >>> _______________________________________________
>>  >>> > >>> users mailing list
>>  >>> > >>> [41]users lists openshift redhat com
>>  >>> > >>>
>>  [42]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>  >>> > >>
>>  >>> > >
>>  >>> > >
>>  >>> > >
>>  >>> > >
>>  >>> > > --
>>  >>> > > Juanje
>>  >>> > >
>>  >>> > > [43]http://about.me/juanje
>>  >>> > > _______________________________________________
>>  >>> > > users mailing list
>>  >>> > > [44]users lists openshift redhat com
>>  >>> > >
>>  [45]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>  >>> >
>>  >>> >
>>  >>> >
>>  >>> >
>>  >>> > --
>>  >>> > Juanje
>>  >>> >
>>  >>> > [46]http://about.me/juanje
>>  >>>
>>  >>>
>>  >>> _______________________________________________
>>  >>> users mailing list
>>  >>> [47]users lists openshift redhat com
>>  >>> [48]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>  >>>
>>  >>> _______________________________________________
>>  >>> users mailing list
>>  >>> [49]users lists openshift redhat com
>>  >>> [50]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>  >>
>>  >>
>>  >
>>  >
>>  > _______________________________________________
>>  > users mailing list
>>  > [51]users lists openshift redhat com
>>  > [52]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>  >
>>  >
>>  >
>>  >
>>  > --
>>  > Juanje
>>  >
>>  > [53]http://about.me/juanje
>>  >
>>  >
>>  >
>>  > --
>>  > Juanje
>>  >
>>  > [54]http://about.me/juanje
>>  >
>>  > _______________________________________________
>>  > users mailing list
>>  > [55]users lists openshift redhat com
>>  > [56]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>  >
>>  >
>>  >
>>  >
>>  >
>>  > --
>>  > Juanje
>>  >
>>  > [57]http://about.me/juanje
>>  >
>>  >
>>  > _______________________________________________
>>  > users mailing list
>>  > [58]users lists openshift redhat com
>>  > [59]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>> References
>>
>>  1. mailto:hripps redhat com
>>  2. mailto:arunabha gh gmail com
>>  3. mailto:arunabha gh gmail com
>>  4. mailto:juanje ojeda gmail com
>>  5. http://broker.example.com/broker
>>  6. https://paste.fedoraproject.org/50083/
>>  7. http://broker.example.com/
>>  8. http://broker.example.com/
>>  9. http://broker.example.com/
>> 10. mailto:arunabha gh gmail com
>> 11. mailto:juanje ojeda gmail com
>> 12. mailto:juanje ojeda gmail com
>> 13. mailto:kraman gmail com
>> 14. mailto:arunabha gh gmail com
>> 15. mailto:kraman gmail com
>> 16. mailto:arunabha gh gmail com
>> 17. mailto:hripps redhat com
>> 18. mailto:juanje ojeda gmail com
>> 19. mailto:hripps redhat com
>> 20. mailto:juanje ojeda gmail com
>> 21. mailto:kraman gmail com
>> 22. mailto:kraman gmail com
>> 23. mailto:hripps redhat com
>> 24. mailto:juanje ojeda gmail com
>> 25. mailto:hripps redhat com
>> 26. https://nodeload.github.com/openshift/puppet-openshift_origin/legacy.tar.gz/master
>> 27. https://mirror.openshift.com/pub/vagrant/boxes/fedora-sphericalcow.box
>> 28. https://mirror.openshift.com/pub/vagrant/boxes/fedora-sphericalcow.box
>> 29. http://mirror.openshift.com/
>> 30. http://mirror.openshift.com/
>> 31. tel:184.72.214.144
>> 32. http://mirror.openshift.com/
>> 33. http://mirror.openshift.com/
>> 34. tel:184.72.214.144
>> 35. https://mirror.openshift.com/pub/vagrant/boxes/fedora-19.box
>> 36. https://paste.fedoraproject.org/
>> 37. http://oo-install.rhcloud.com/
>> 38. https://paste.fedoraproject.org/49848/
>> 39. https://paste.fedoraproject.org/49852/
>> 40. http://about.me/juanje
>> 41. mailto:users lists openshift redhat com
>> 42. http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> 43. http://about.me/juanje
>> 44. mailto:users lists openshift redhat com
>> 45. http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> 46. http://about.me/juanje
>> 47. mailto:users lists openshift redhat com
>> 48. http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> 49. mailto:users lists openshift redhat com
>> 50. http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> 51. mailto:users lists openshift redhat com
>> 52. http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> 53. http://about.me/juanje
>> 54. http://about.me/juanje
>> 55. mailto:users lists openshift redhat com
>> 56. http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> 57. http://about.me/juanje
>> 58. mailto:users lists openshift redhat com
>> 59. 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


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