Marek,
Thanks for your note, but die the same applies for CentOS 6? Both links seem to refer to CentOS 7.
IB
···
- Ignacio Bravo LTG Federal Mb: (571) 224-6046On Aug 22, 2014, at 11:46 AM, Marek Hulan mhulan@redhat.com wrote:
Hello,
since CentOS is not supported, noone noticed that it stopped working on
CentOS. I made a fix on both installer and staypuft side today. You’ll have to
update and rerun the installer (0.3.2 should get to nightly tomorrow) to
precreate staypuft OS v 7. Staypuft fix was not yet merged but you can apply it
manually, see [1] for the patch.Before creating new deploy you must also fix one issue with CentOS installation
media. For some reason, CentOS 7.0 mirror does not follow standard path so as
a workaround you have to navigate to Hosts -> Installation Media -> CentOS
Mirror and update path to http://mirror.centos.org/centos/$major/os/$arch.
More information at [2].Fixes should get in and be packaged in the beginning of next week. I’d be
happy if you tested them and shared your results.[1] https://github.com/theforeman/staypuft/pull/271
[2] Bug #6884: Centos mirror in "Installation Media" doesn't work for versions without $minor - ForemanOn Thursday 21 of August 2014 17:49:52 Marek Hulan wrote:
I was able to reproduce it. I’ll look have a look at it tomorrow and will
let you know.After downloading images I rerun installer and he told me that everything
success:Starting configuration…
Starting to seed provisioning data
Use ‘base_CentOS_6’ hostgroup for provisioningSuccess!
Foreman is running at https://openstack-core.cloud
Initial credentials are admin / df4Rauujuwxdede6
Foreman Proxy is running at https://openstack-core.cloud:8443
Puppetmaster is running at port 8140
The full log is at /var/log/foreman-installer/foreman-installer.logBut UI told me same "missing Operatingsystem"
and in foreman/production.log same error:Started GET “/deployments/new” for 10.10.10.1 at 2014-08-21 17:14:12 +0300
Processing by Staypuft::DeploymentsController#new as HTML
Operation FAILED: missing OperatingsystemRendered common/500.html.erb within staypuft/layouts/staypuft (3.8ms)
Rendered layouts/base.html.erb (0.9ms)
Rendered /opt/rh/ruby193/root/usr/share/gems/gems/staypuft-0.1.20/app/views/staypuft/layouts/application.html.erb (1.2ms)
Completed 500 Internal Server Error in 79ms (Views: 6.7ms | ActiveRecord:
13.4ms)On Thursday, August 21, 2014 5:01:15 PM UTC+3, Marek Hulan wrote:
There seems to be some ordering issue with discovery images, target
directory
did not exist yet. When there appears an error during installation,
configuration won’t continue. Your staypuft installation resulted in
being
installed but not configured.Now when you fixed discovery images issue, can you rerun installer once
more?
Until it shows that you can use some hostgroup for provisioning you
can’t
consider staypuft to be ready. But if discovery images was the only
issue
it
should pass now.On Thursday 21 of August 2014 03:20:15 Nomnom Fuser wrote:
Ok. Yet another fresh install. Centos 6.5 x86_64
repos:base
CentOS-6 - Base
epel
Extra Packages for Enterprise Linux 6 - x86_64
extras
CentOS-6 - Extras
foreman
Foreman nightly
foreman-plugins
Foreman plugins nightly
scl
CentOS-6 - SCL
updates
CentOS-6 - Updates
rpm -qa | grep foreman
foreman-selinux-1.7.0-0.develop.201408202047gitd5e80cf.el6.noarch
foreman-installer-staypuft-0.3.0-1.el6.noarch
foreman-release-1.7.0-0.develop.201408201145git87a42cb.el6.noarch
rubygem-foreman_api-0.1.11-1.el6.noarch
foreman-installer-1.7.0-0.develop.201408210326git3551ee3.el6.noarchFirst install with "staypuft-installer
–foreman-configure-epel-repo=true
–foreman-plugin-discovery-install-images=true" :
[ INFO 2014-08-21 13:06:14 main] Executing hooks in group post
[DEBUG 2014-08-21 13:06:14 main] Hook/usr/share/foreman-installer/hooks/
post/10-setup_provisioning.rb returned false
[ INFO 2014-08-21 13:06:14 main] All hooks in group post finished
[DEBUG 2014-08-21 13:06:14 main] Exit with status code: 6 (signal was
6)
[ERROR 2014-08-21 13:06:14 main] Repeating errors encountered duringrun:
[ERROR 2014-08-21 13:06:14 main]
/Stage[main]/Foreman::Plugin::Discovery/
Foreman::Remote_file[/var/lib/tftpboot/boot/foreman-discovery-image-late
st
.el6.iso-vmlinuz]/Exec[retrieve_/var/lib/tftpboot/boot/foreman-discovery-> > > >
image-latest.el6.iso-vmlinuz]/returns: change from notrun to 0 failed:
/usr/bin/curl -s
http://downloads.theforeman.org/discovery/releases/latest/foreman-discov
er
y-image-latest.el6.iso-vmlinuz -o
/var/lib/tftpboot/boot/foreman-discovery-image-latest.el6.iso-vmlinuz
returned 23 instead of one of [0] at
/usr/share/foreman-installer/modules/foreman/manifests/remote_file.pp:
6
[ERROR 2014-08-21 13:06:14 main]/Stage[main]/Foreman::Plugin::Discovery/
Foreman::Remote_file[/var/lib/tftpboot/boot/foreman-discovery-image-late
st
.el6.iso-img]/Exec[retrieve_/var/lib/tftpboot/boot/foreman-discovery-imag
e-> > > latest.el6.iso-img]/returns: change from notrun to 0 failed:
/usr/bin/curl> >-s
http://downloads.theforeman.org/discovery/releases/latest/foreman-discov
er
y-image-latest.el6.iso-img -o
/var/lib/tftpboot/boot/foreman-discovery-image-latest.el6.iso-imgreturned
23 instead of one of [0] at
/usr/share/foreman-installer/modules/foreman/manifests/remote_file.pp:Ok, I download images manually using same curl command.
Second run with same options. Seems ok. “Success!”Login to UI, go to new deployment of openstack, aaaannnndddd…
Started GET “/deployments/new” for 10.10.10.1 at 2014-08-21 13:14:11
+0300
Processing by Staypuft::DeploymentsController#new as HTML
Operation FAILED: missing OperatingsystemRendered common/500.html.erb within staypuft/layouts/staypuft
(7.9ms)
Rendered layouts/base.html.erb (2.0ms)
Rendered
/opt/rh/ruby193/root/usr/share/gems/gems/staypuft-0.1.20/app/views/staypuft/layouts/application.html.erb (3.6ms)
Completed 500 Internal Server Error in 508ms (Views: 16.6ms |ActiveRecord:
34.1ms)
after installer:
rpm -qa | grep foreman
foreman-installer-staypuft-0.3.0-1.el6.noarch
ruby193-rubygem-foreman-tasks-0.6.4-1.el6.noarch
foreman-postgresql-1.7.0-0.develop.201408201145git87a42cb.el6.noarch
foreman-release-1.7.0-0.develop.201408201145git87a42cb.el6.noarch
rubygem-foreman_api-0.1.11-1.el6.noarch
foreman-installer-1.7.0-0.develop.201408210326git3551ee3.el6.noarch
foreman-1.7.0-0.develop.201408201145git87a42cb.el6.noarch
foreman-proxy-1.7.0-0.develop.201408191935git7124635.el6.noarch
foreman-selinux-1.7.0-0.develop.201408202047gitd5e80cf.el6.noarch
ruby193-rubygem-foreman_discovery-1.3.0-1.el6.noarchSeems like I need install openstack manually from source or using rdo
without provisioning %(On Thursday, August 21, 2014 10:33:16 AM UTC+3, Marek Hulan wrote:
Hello,This error would indicate that installer did not finish all steps
successfully.
Could you rerun the installer and try again?–
Marek–
You received this message because you are subscribed to a topic in the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/MUM5iAwwVUc/unsubscribe.
To unsubscribe from this group and all its topics, 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.