[Katello] Katello Installer Alpha Testing

ehelms · January 22, 2014, 11:23pm

Howdy!

We are proud to announce that the Katello installer work has finally
reached an alpha stage that is ready for user testing. This installer takes
the enginification work of Katello and installs it alongside Foreman to
bring the full seamless experience of Foreman+Katello. We ask for anyone
willing to jump in and test to do so. Please record feedback and issues
either:

Redmine - http://projects.theforeman.org/projects/katello/issues/new
Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer

Installation is available for RHEL6 and CentOS 6 and requires EPEL and the
SCL to be enabled. Our recommended approach is a set of scripts available
in our deployment repository. Instructions can be found in the deployment
repository's README at:

https://github.com/Katello/katello-deploy

This repository provides methods for installation on an existing VM or
using Vagrant with libvirt to deploy to CentOS.

The installer git repository is located at:

https://github.com/Katello/katello-installer

And available in our nightly RHEL6 repo:

http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/

Thanks to inecas, jsherrill, mccun934, jmontleon and all those that
contributed module work, RPM work, puppet knowledge or early user testing.

Happy testing!
Eric

eliran_shlomo1 · January 22, 2014, 11:46pm

Hi,
Wonderful news and great job.

But there's a conflict with ruby193-ruby-wrapper

Transaction Check Error:
file /usr/bin/ruby193-ruby from install of
ruby193-ruby-wrapper-0.0.2-4.el6.noarch conflicts with file from package
ruby193-ruby-1.9.3.327-29.el6.x86_64
file /usr/bin/ruby193-rake from install of
ruby193-ruby-wrapper-0.0.2-4.el6.noarch conflicts with file from package
ruby193-rubygem-rake-0.9.2.2-29.el6.noarch

···

On Thursday, January 23, 2014 1:23:50 AM UTC+2, Eric Helms wrote: > > Howdy! > > We are proud to announce that the Katello installer work has finally > reached an alpha stage that is ready for user testing. This installer takes > the enginification work of Katello and installs it alongside Foreman to > bring the full seamless experience of Foreman+Katello. We ask for anyone > willing to jump in and test to do so. Please record feedback and issues > either: > > Redmine - http://projects.theforeman.org/projects/katello/issues/new > Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer > > Installation is available for RHEL6 and CentOS 6 and requires EPEL and the > SCL to be enabled. Our recommended approach is a set of scripts available > in our deployment repository. Instructions can be found in the deployment > repository's README at: > > https://github.com/Katello/katello-deploy > > This repository provides methods for installation on an existing VM or > using Vagrant with libvirt to deploy to CentOS. > > The installer git repository is located at: > > https://github.com/Katello/katello-installer > > And available in our nightly RHEL6 repo: > > > http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ > > Thanks to inecas, jsherrill, mccun934, jmontleon and all those that > contributed module work, RPM work, puppet knowledge or early user testing. > > Happy testing! > Eric >

Gavin_Williams · January 23, 2014, 10:02am

Morning all

Thought I'd give this a spin…

Created a fresh Centos 6 install using Vagrant and Vbox on Windows 7.

First stage of bootstrap process worked fine, with yum installing 344
packages.
However got a failure when running "katello-installer -v -d".

Failure was:

Complete!
> Could not get default values, check log file at
> /var/log/katello/katello-install/katello-install.log for more information
> inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
>

/var/log/katello/katello-install/katello-install.log contains:

[ INFO 2014-01-23 09:51:07 main] Parsing default values from puppet
> modules…
> [DEBUG 2014-01-23 09:51:07 main] echo
> '$kafo_config_file="/etc/katello-installer/katello_installer.yaml"
> $kafo_add_progress=true include foreman::params include puppet::params
> include katello::params include certs::params
> dump_values(foreman::params::repo,foreman::params::configure_scl_repo,foreman::params::selinux,foreman::params::user,foreman::params::group,foreman::params::ssl,foreman::params::configure_epel_repo,foreman::params::version,foreman::params::user_groups,foreman::params::server_ssl_ca,foreman::params::authentication,foreman::params::use_vhost,foreman::params::organizations_enabled,foreman::params::puppet_home,foreman::params::locations_enabled,foreman::params::passenger_interface,foreman::params::server_ssl_cert,foreman::params::server_ssl_key,foreman::params::oauth_consumer_key,foreman::params::db_manage,foreman::params::oauth_active,foreman::params::passenger,foreman::params::db_username,foreman::params::app_root,foreman::params::passenger_scl,foreman::params::environment,foreman::params::apache_conf_dir,foreman::params::oauth_map_users,foreman::params::foreman_url,foreman::params::unattended,foreman::params::custom_repo,foreman::params::gpgcheck,foreman::params::db_password,foreman::params::db_type,foreman::params::oauth_consumer_secret,puppet::params::user,puppet::params::group,puppet::params::listen,puppet::params::agent_template,puppet::params::port,puppet::params::server_service_fallback,puppet::params::server_passenger_max_pool,puppet::params::server_app_root,puppet::params::server_package,puppet::params::version,puppet::params::port,puppet::params::classfile,puppet::params::server_ca,puppet::params::server_git_repo_path,puppet::params::server_git_branch_map,foreman::params::client_ssl_ca,puppet::params::dir,puppet::params::cron_cmd,puppet::params::auth_template,puppet::params::group,puppet::params::server_git_repo,puppet::params::server_common_modules_path,puppet::params::splay,puppet::params::server_vardir,puppet::params::server_passenger,puppet::params::server_post_hook_name,foreman::params::facts,foreman::params::puppet_basedir,puppet::params::nsauth_template,puppet::params::server,puppet::params::server_external_nodes,puppet::params::server_environments,puppet::params::server_post_hook_content,puppet::params::server_storeconfigs_backend,foreman::params::client_ssl_key,puppet::params::pluginsync,puppet::params::dir,puppet::params::server_enc_api,foreman::params::client_ssl_cert,puppet::params::ca_server,puppet::params::server_template,puppet::params::runinterval,puppet::params::server_httpd_service,puppet::params::server_environments_owner,puppet::params::server_envs_dir,puppet::params::show_diff,puppet::params::server_reports,puppet::params::server_manifest_path,puppet::params::server_ssl_dir,puppet::params::server_certname,foreman::params::puppet_home,puppet::params::runmode,puppet::params::configtimeout,puppet::params::client_package,puppet::params::agent,puppet::params::server_dynamic_environments,puppet::params::agent_noop,puppet::params::main_template,puppet::params::user,puppet::params::server_config_version,puppet::params::server_report_api,foreman::params::foreman_url,katello::params::user,katello::params::group,katello::params::user_groups,katello::params::oauth_secret,katello::params::oauth_key,katello::params::log_dir,certs::params::regenerate_ca,certs::params::expiration,certs::params::node_fqdn,certs::params::generate,certs::params::regenerate,certs::params::org,certs::params::ca_common_name,certs::params::city,certs::params::log_dir,certs::params::org_unit,certs::params::country,certs::params::state,certs::params::deploy,certs::params::ca_expiration)'
> > RUBYLIB=/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/lib/kafo/…/…//modules:
> puppet apply --modulepath
> /usr/share/katello-installer/modules:/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/modules
> 2>&1
> [DEBUG 2014-01-23 09:51:08 main] Generating new random seed in
> /etc/katello/oauth_token-file
> ^[[1;31mError: custom functions must be called with a single array that
> contains the arguments. For example, function_example([1]) instead of
> function_example(1) at
> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node
> katello.dt0388.test
> Wrapped exception:
> custom functions must be called with a single array that contains the
> arguments. For example, function_example([1]) instead of
> function_example(1)^[[0m
> ^[[1;31mError: custom functions must be called with a single array that
> contains the arguments. For example, function_example([1]) instead of
> function_example(1) at
> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node
> katello.dt0388.test^[[0m
>
> [ERROR 2014-01-23 09:51:08 main] Could not get default values, cannot
> continue
>

This is with Puppet 3.4.2…

Let me know if you need any more info…

Gav

···

On Wednesday, 22 January 2014 23:23:50 UTC, Eric Helms wrote: > > Howdy! > > We are proud to announce that the Katello installer work has finally > reached an alpha stage that is ready for user testing. This installer takes > the enginification work of Katello and installs it alongside Foreman to > bring the full seamless experience of Foreman+Katello. We ask for anyone > willing to jump in and test to do so. Please record feedback and issues > either: > > Redmine - http://projects.theforeman.org/projects/katello/issues/new > Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer > > Installation is available for RHEL6 and CentOS 6 and requires EPEL and the > SCL to be enabled. Our recommended approach is a set of scripts available > in our deployment repository. Instructions can be found in the deployment > repository's README at: > > https://github.com/Katello/katello-deploy > > This repository provides methods for installation on an existing VM or > using Vagrant with libvirt to deploy to CentOS. > > The installer git repository is located at: > > https://github.com/Katello/katello-installer > > And available in our nightly RHEL6 repo: > > > http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ > > Thanks to inecas, jsherrill, mccun934, jmontleon and all those that > contributed module work, RPM work, puppet knowledge or early user testing. > > Happy testing! > Eric >

Bryan_Kearney · January 23, 2014, 1:29pm

RHEL 6.4 minimal install gets me this:

Complete!
Could not get default values, check log file at
/var/log/katello/katello-install/katello-install.log for more information
inet 192.168.100.163/24 brd 192.168.100.255 scope global eth0
[root@sat6 katello-deploy]# vi
/var/log/katello/katello-install/katello-install.log
[root@sat6 katello-deploy]# rpm -qa | grep puppet
puppet-2.7.23-1.el6.noarch
python-pulp-puppet-common-2.3.1-1.el6.noarch
pulp-puppet-plugins-2.3.1-1.el6.noarch
[root@sat6 katello-deploy]#

– bk

···

On 01/22/2014 06:23 PM, Eric D Helms wrote: > Howdy! > > We are proud to announce that the Katello installer work has finally > reached an alpha stage that is ready for user testing. This installer > takes the enginification work of Katello and installs it alongside > Foreman to bring the full seamless experience of Foreman+Katello. We ask > for anyone willing to jump in and test to do so. Please record feedback > and issues either: > > Redmine - http://projects.theforeman.org/projects/katello/issues/new > Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer > > Installation is available for RHEL6 and CentOS 6 and requires EPEL and > the SCL to be enabled. Our recommended approach is a set of scripts > available in our deployment repository. Instructions can be found in the > deployment repository's README at: > > https://github.com/Katello/katello-deploy > > This repository provides methods for installation on an existing VM or > using Vagrant with libvirt to deploy to CentOS. > > The installer git repository is located at: > > https://github.com/Katello/katello-installer > > And available in our nightly RHEL6 repo: > > http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ > > Thanks to inecas, jsherrill, mccun934, jmontleon and all those that > contributed module work, RPM work, puppet knowledge or early user testing. > > Happy testing! > Eric > > -- > You received this message because you are subscribed to the Google > Groups "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out.

Dominic_Cleal1 · January 23, 2014, 8:43am

I think it's built on top of the Foreman nightly repos, which means you
need to use RHSCL or equivalent rebuild rather than the ruby193 builds
from Foreman 1.3 and older.

Check you have RHSCL enabled (see
Foreman :: Manual) and a
newer version of ruby193-rubygem-rake should be available to resolve
this issue.

···

On 22/01/14 23:46, eliran shlomo wrote: > Hi, > Wonderful news and great job. > > But there's a conflict with ruby193-ruby-wrapper > > Transaction Check Error: > file /usr/bin/ruby193-ruby from install of > ruby193-ruby-wrapper-0.0.2-4.el6.noarch conflicts with file from package > ruby193-ruby-1.9.3.327-29.el6.x86_64 > file /usr/bin/ruby193-rake from install of > ruby193-ruby-wrapper-0.0.2-4.el6.noarch conflicts with file from package > ruby193-rubygem-rake-0.9.2.2-29.el6.noarch

–
Dominic Cleal
Red Hat Engineering

Gavin_Williams · January 23, 2014, 10:07am

Thought I'd see if it would continue with fixing that error in the
manifest…

However hit the same error again on a different manifest:

[DEBUG 2014-01-23 10:02:18 main] Generating new random seed in
> /etc/katello/keystore_password-file
> ^[[1;31mError: custom functions must be called with a single array that
> contains the arguments. For example, function_example([1]) instead of
> function_example(1) at
> /usr/share/katello-installer/modules/certs/manifests/params.pp:58 on node
> katello.dt0388.test
> Wrapped exception:
> custom functions must be called with a single array that contains the
> arguments. For example, function_example([1]) instead of
> function_example(1)^[[0m
> ^[[1;31mError: custom functions must be called with a single array that
> contains the arguments. For example, function_example([1]) instead of
> function_example(1) at
> /usr/share/katello-installer/modules/certs/manifests/params.pp:58 on node
> katello.dt0388.test^[[0m
>
>
After fixing that, I get:

[DEBUG 2014-01-23 10:02:47 main] ^[[1;31mError: can't convert Array into
> String at
> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node
> katello.dt0388.test
> Wrapped exception:
> can't convert Array into String^[[0m
> ^[[1;31mError: can't convert Array into String at
> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node
> katello.dt0388.test^[[0m
>
> [ERROR 2014-01-23 10:02:47 main] Could not get default values, cannot
> continue
>
>
Will look at that one next…

Gav

···

On Thursday, 23 January 2014 10:02:09 UTC, Gavin Williams wrote: > > Morning all > > Thought I'd give this a spin... > > Created a fresh Centos 6 install using Vagrant and Vbox on Windows 7. > > First stage of bootstrap process worked fine, with yum installing 344 > packages. > However got a failure when running "*katello-installer -v -d*". > > Failure was: > > Complete! >> Could not get default values, check log file at >> /var/log/katello/katello-install/katello-install.log for more information >> inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0 >> > > /var/log/katello/katello-install/katello-install.log contains: > > [ INFO 2014-01-23 09:51:07 main] Parsing default values from puppet >> modules... >> [DEBUG 2014-01-23 09:51:07 main] echo >> '$kafo_config_file="/etc/katello-installer/katello_installer.yaml" >> $kafo_add_progress=true include foreman::params include puppet::params >> include katello::params include certs::params >> dump_values(foreman::params::repo,foreman::params::configure_scl_repo,foreman::params::selinux,foreman::params::user,foreman::params::group,foreman::params::ssl,foreman::params::configure_epel_repo,foreman::params::version,foreman::params::user_groups,foreman::params::server_ssl_ca,foreman::params::authentication,foreman::params::use_vhost,foreman::params::organizations_enabled,foreman::params::puppet_home,foreman::params::locations_enabled,foreman::params::passenger_interface,foreman::params::server_ssl_cert,foreman::params::server_ssl_key,foreman::params::oauth_consumer_key,foreman::params::db_manage,foreman::params::oauth_active,foreman::params::passenger,foreman::params::db_username,foreman::params::app_root,foreman::params::passenger_scl,foreman::params::environment,foreman::params::apache_conf_dir,foreman::params::oauth_map_users,foreman::params::foreman_url,foreman::params::unattended,foreman::params::custom_repo,foreman::params::gpgcheck,foreman::params::db_password,foreman::params::db_type,foreman::params::oauth_consumer_secret,puppet::params::user,puppet::params::group,puppet::params::listen,puppet::params::agent_template,puppet::params::port,puppet::params::server_service_fallback,puppet::params::server_passenger_max_pool,puppet::params::server_app_root,puppet::params::server_package,puppet::params::version,puppet::params::port,puppet::params::classfile,puppet::params::server_ca,puppet::params::server_git_repo_path,puppet::params::server_git_branch_map,foreman::params::client_ssl_ca,puppet::params::dir,puppet::params::cron_cmd,puppet::params::auth_template,puppet::params::group,puppet::params::server_git_repo,puppet::params::server_common_modules_path,puppet::params::splay,puppet::params::server_vardir,puppet::params::server_passenger,puppet::params::server_post_hook_name,foreman::params::facts,foreman::params::puppet_basedir,puppet::params::nsauth_template,puppet::params::server,puppet::params::server_external_nodes,puppet::params::server_environments,puppet::params::server_post_hook_content,puppet::params::server_storeconfigs_backend,foreman::params::client_ssl_key,puppet::params::pluginsync,puppet::params::dir,puppet::params::server_enc_api,foreman::params::client_ssl_cert,puppet::params::ca_server,puppet::params::server_template,puppet::params::runinterval,puppet::params::server_httpd_service,puppet::params::server_environments_owner,puppet::params::server_envs_dir,puppet::params::show_diff,puppet::params::server_reports,puppet::params::server_manifest_path,puppet::params::server_ssl_dir,puppet::params::server_certname,foreman::params::puppet_home,puppet::params::runmode,puppet::params::configtimeout,puppet::params::client_package,puppet::params::agent,puppet::params::server_dynamic_environments,puppet::params::agent_noop,puppet::params::main_template,puppet::params::user,puppet::params::server_config_version,puppet::params::server_report_api,foreman::params::foreman_url,katello::params::user,katello::params::group,katello::params::user_groups,katello::params::oauth_secret,katello::params::oauth_key,katello::params::log_dir,certs::params::regenerate_ca,certs::params::expiration,certs::params::node_fqdn,certs::params::generate,certs::params::regenerate,certs::params::org,certs::params::ca_common_name,certs::params::city,certs::params::log_dir,certs::params::org_unit,certs::params::country,certs::params::state,certs::params::deploy,certs::params::ca_expiration)' >> > RUBYLIB=/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/lib/kafo/../..//modules: >> puppet apply --modulepath >> /usr/share/katello-installer/modules:/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/modules >> 2>&1 >> [DEBUG 2014-01-23 09:51:08 main] Generating new random seed in >> /etc/katello/oauth_token-file >> ^[[1;31mError: custom functions must be called with a single array that >> contains the arguments. For example, function_example([1]) instead of >> function_example(1) at >> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node >> katello.dt0388.test >> Wrapped exception: >> custom functions must be called with a single array that contains the >> arguments. For example, function_example([1]) instead of >> function_example(1)^[[0m >> ^[[1;31mError: custom functions must be called with a single array that >> contains the arguments. For example, function_example([1]) instead of >> function_example(1) at >> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node >> katello.dt0388.test^[[0m >> >> [ERROR 2014-01-23 09:51:08 main] Could not get default values, cannot >> continue >> > > This is with Puppet 3.4.2... > > Let me know if you need any more info... > > Gav > > On Wednesday, 22 January 2014 23:23:50 UTC, Eric Helms wrote: >> >> Howdy! >> >> We are proud to announce that the Katello installer work has finally >> reached an alpha stage that is ready for user testing. This installer takes >> the enginification work of Katello and installs it alongside Foreman to >> bring the full seamless experience of Foreman+Katello. We ask for anyone >> willing to jump in and test to do so. Please record feedback and issues >> either: >> >> Redmine - http://projects.theforeman.org/projects/katello/issues/new >> Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer >> >> Installation is available for RHEL6 and CentOS 6 and requires EPEL and >> the SCL to be enabled. Our recommended approach is a set of scripts >> available in our deployment repository. Instructions can be found in the >> deployment repository's README at: >> >> https://github.com/Katello/katello-deploy >> >> This repository provides methods for installation on an existing VM or >> using Vagrant with libvirt to deploy to CentOS. >> >> The installer git repository is located at: >> >> https://github.com/Katello/katello-installer >> >> And available in our nightly RHEL6 repo: >> >> >> http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ >> >> Thanks to inecas, jsherrill, mccun934, jmontleon and all those that >> contributed module work, RPM work, puppet knowledge or early user testing. >> >> Happy testing! >> Eric >> >

ehelms · January 23, 2014, 12:00pm

>
> > Hi,
> > Wonderful news and great job.
> >
> > But there's a conflict with ruby193-ruby-wrapper
> >
> > Transaction Check Error:
> > file /usr/bin/ruby193-ruby from install of
> > ruby193-ruby-wrapper-0.0.2-4.el6.noarch conflicts with file from package
> > ruby193-ruby-1.9.3.327-29.el6.x86_64
> > file /usr/bin/ruby193-rake from install of
> > ruby193-ruby-wrapper-0.0.2-4.el6.noarch conflicts with file from package
> > ruby193-rubygem-rake-0.9.2.2-29.el6.noarch
>
> I think it's built on top of the Foreman nightly repos, which means you
> need to use RHSCL or equivalent rebuild rather than the ruby193 builds
> from Foreman 1.3 and older.
>

Correct. The installer and engine are built against bleeding edge Foreman.
I should also clarify that this is currently not meant to be used alongside
or after the foreman-installer. The Katello installer is stand alone and
handles setup of both.

Eric

> Check you have RHSCL enabled (see
> Foreman :: Manual) and a
> newer version of ruby193-rubygem-rake should be available to resolve
> this issue.
>
> –
> Dominic Cleal
> Red Hat Engineering
>
> –
> You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.

···

On Jan 23, 2014 3:44 AM, "Dominic Cleal" wrote: > On 22/01/14 23:46, eliran shlomo wrote: > For more options, visit https://groups.google.com/groups/opt_out.

Bryan_Kearney · January 23, 2014, 2:34pm

ok… once I got passed the fqdn error it installed fine. Couple of
comments so far:

Would be nice to have a check for FQDN.
Would be nice to report some success or message when done… saying
"You can log in at XXXX"
Is it a security problem defaulting the user password?

– bk

···

On 01/23/2014 08:29 AM, Bryan Kearney wrote: > On 01/22/2014 06:23 PM, Eric D Helms wrote: >> Howdy! >> >> We are proud to announce that the Katello installer work has finally >> reached an alpha stage that is ready for user testing. This installer >> takes the enginification work of Katello and installs it alongside >> Foreman to bring the full seamless experience of Foreman+Katello. We ask >> for anyone willing to jump in and test to do so. Please record feedback >> and issues either: >> >> Redmine - http://projects.theforeman.org/projects/katello/issues/new >> Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer >> >> Installation is available for RHEL6 and CentOS 6 and requires EPEL and >> the SCL to be enabled. Our recommended approach is a set of scripts >> available in our deployment repository. Instructions can be found in the >> deployment repository's README at: >> >> https://github.com/Katello/katello-deploy >> >> This repository provides methods for installation on an existing VM or >> using Vagrant with libvirt to deploy to CentOS. >> >> The installer git repository is located at: >> >> https://github.com/Katello/katello-installer >> >> And available in our nightly RHEL6 repo: >> >> http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ >> >> >> Thanks to inecas, jsherrill, mccun934, jmontleon and all those that >> contributed module work, RPM work, puppet knowledge or early user >> testing. >> >> Happy testing! >> Eric >> >> -- >> You received this message because you are subscribed to the Google >> Groups "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to foreman-dev+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > RHEL 6.4 minimal install gets me this: > > Complete! > Could not get default values, check log file at > /var/log/katello/katello-install/katello-install.log for more information > inet 192.168.100.163/24 brd 192.168.100.255 scope global eth0 > [root@sat6 katello-deploy]# vi > /var/log/katello/katello-install/katello-install.log > [root@sat6 katello-deploy]# rpm -qa | grep puppet > puppet-2.7.23-1.el6.noarch > python-pulp-puppet-common-2.3.1-1.el6.noarch > pulp-puppet-plugins-2.3.1-1.el6.noarch > [root@sat6 katello-deploy]# > > > -- bk >

ehelms · January 23, 2014, 11:57am

Gavin - I know the issue you speak of and will fix today. Stems from our
testing originally on puppet 2.7 and not 3+. You can install 2.7 with just
'yum install puppet' in the meantime while we work on a fix.

Eric

···

On Jan 23, 2014 5:07 AM, "Gavin Williams" wrote:

Thought I’d see if it would continue with fixing that error in the
manifest…

However hit the same error again on a different manifest:

[DEBUG 2014-01-23 10:02:18 main] Generating new random seed in

/etc/katello/keystore_password-file
^[[1;31mError: custom functions must be called with a single array that
contains the arguments. For example, function_example([1]) instead of
function_example(1) at
/usr/share/katello-installer/modules/certs/manifests/params.pp:58 on node
katello.dt0388.test
Wrapped exception:
custom functions must be called with a single array that contains the
arguments. For example, function_example([1]) instead of
function_example(1)^[[0m
^[[1;31mError: custom functions must be called with a single array that
contains the arguments. For example, function_example([1]) instead of
function_example(1) at
/usr/share/katello-installer/modules/certs/manifests/params.pp:58 on node
katello.dt0388.test^[[0m

After fixing that, I get:

[DEBUG 2014-01-23 10:02:47 main] ^[[1;31mError: can’t convert Array into

String at
/usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node
katello.dt0388.test
Wrapped exception:
can’t convert Array into String^[[0m
^[[1;31mError: can’t convert Array into String at
/usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node
katello.dt0388.test^[[0m

[ERROR 2014-01-23 10:02:47 main] Could not get default values, cannot
continue

Will look at that one next…

Gav

On Thursday, 23 January 2014 10:02:09 UTC, Gavin Williams wrote:

Morning all

Thought I’d give this a spin…

Created a fresh Centos 6 install using Vagrant and Vbox on Windows 7.

First stage of bootstrap process worked fine, with yum installing 344
packages.
However got a failure when running “katello-installer -v -d”.

Failure was:

Complete!

Could not get default values, check log file at /var/log/katello/katello-install/katello-install.log
for more information
inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0

/var/log/katello/katello-install/katello-install.log contains:

[ INFO 2014-01-23 09:51:07 main] Parsing default values from puppet

modules…
[DEBUG 2014-01-23 09:51:07 main] echo ‘$kafo_config_file="/etc/
katello-installer/katello_installer.yaml" $kafo_add_progress=true
include foreman::params include puppet::params include katello::params
include certs::params dump_values(foreman::params::
repo,foreman::params::configure_scl_repo,foreman::
params::selinux,foreman::params::user,foreman::params::
group,foreman::params::ssl,foreman::params::configure_
epel_repo,foreman::params::version,foreman::params::user_
groups,foreman::params::server_ssl_ca,foreman::params:
:authentication,foreman::params::use_vhost,foreman::
params::organizations_enabled,foreman::params::puppet_home,
foreman::params::locations_enabled,foreman::params::
passenger_interface,foreman::params::server_ssl_cert,
foreman::params::server_ssl_key,foreman::params::oauth_
consumer_key,foreman::params::db_manage,foreman::params::
oauth_active,foreman::params::passenger,foreman::params::db_
username,foreman::params::app_root,foreman::params::
passenger_scl,foreman::params::environment,foreman::params::
apache_conf_dir,foreman::params::oauth_map_users,
foreman::params::foreman_url,foreman::params::unattended,
foreman::params::custom_repo,foreman::params::gpgcheck,
foreman::params::db_password,foreman::params::db_type,
foreman::params::oauth_consumer_secret,puppet::
params::user,puppet::params::group,puppet::params::listen,
puppet::params::agent_template,puppet::params::port,
puppet::params::server_service_fallback,puppet::
params::server_passenger_max_pool,puppet::params::server_
app_root,puppet::params::server_package,puppet::params:
:version,puppet::params::port,puppet::params::classfile,
puppet::params::server_ca,puppet::params::server_git_
repo_path,puppet::params::server_git_branch_map,foreman:
:params::client_ssl_ca,puppet::params::dir,puppet::params::
cron_cmd,puppet::params::auth_template,puppet::params::
group,puppet::params::server_git_repo,puppet::params::
server_common_modules_path,puppet::params::splay,puppet::
params::server_vardir,puppet::params::server_passenger,
puppet::params::server_post_hook_name,foreman::params::
facts,foreman::params::puppet_basedir,puppet::params::
nsauth_template,puppet::params::server,puppet::params:
:server_external_nodes,puppet::params::server_environments,
puppet::params::server_post_hook_content,puppet::params::
server_storeconfigs_backend,foreman::params::client_ssl_
key,puppet::params::pluginsync,puppet::params::
dir,puppet::params::server_enc_api,foreman::params::
client_ssl_cert,puppet::params::ca_server,puppet::
params::server_template,puppet::params::runinterval,
puppet::params::server_httpd_service,puppet::params::
server_environments_owner,puppet::params::server_envs_
dir,puppet::params::show_diff,puppet::params::server_
reports,puppet::params::server_manifest_path,puppet::
params::server_ssl_dir,puppet::params::server_certname,
foreman::params::puppet_home,puppet::params::runmode,
puppet::params::configtimeout,puppet::params::client_
package,puppet::params::agent,puppet::params::server_
dynamic_environments,puppet::params::agent_noop,puppet::
params::main_template,puppet::params::user,puppet::params::
server_config_version,puppet::params::server_report_api,
foreman::params::foreman_url,katello::params::user,katello:
:params::group,katello::params::user_groups,katello::
params::oauth_secret,katello::params::oauth_key,katello::
params::log_dir,certs::params::regenerate_ca,certs::params::
expiration,certs::params::node_fqdn,certs::params::
generate,certs::params::regenerate,certs::params::org,
certs::params::ca_common_name,certs::params::city,certs::
params::log_dir,certs::params::org_unit,certs::params::
country,certs::params::state,certs::params::deploy,certs::params::ca_expiration)’

RUBYLIB=/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/lib/kafo/…/…//modules:
puppet apply --modulepath /usr/share/katello-installer/
modules:/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/modules 2>&1
[DEBUG 2014-01-23 09:51:08 main] Generating new random seed in
/etc/katello/oauth_token-file
^[[1;31mError: custom functions must be called with a single array that
contains the arguments. For example, function_example([1]) instead of
function_example(1) at /usr/share/katello-installer/
modules/katello/manifests/params.pp:80 on node katello.dt0388.test
Wrapped exception:
custom functions must be called with a single array that contains the
arguments. For example, function_example([1]) instead of
function_example(1)^[[0m
^[[1;31mError: custom functions must be called with a single array that
contains the arguments. For example, function_example([1]) instead of
function_example(1) at /usr/share/katello-installer/
modules/katello/manifests/params.pp:80 on node katello.dt0388.test^[[0m

[ERROR 2014-01-23 09:51:08 main] Could not get default values, cannot
continue

This is with Puppet 3.4.2…

Let me know if you need any more info…

Gav

On Wednesday, 22 January 2014 23:23:50 UTC, Eric Helms wrote:

Howdy!

We are proud to announce that the Katello installer work has finally
reached an alpha stage that is ready for user testing. This installer takes
the enginification work of Katello and installs it alongside Foreman to
bring the full seamless experience of Foreman+Katello. We ask for anyone
willing to jump in and test to do so. Please record feedback and issues
either:

Redmine - Foreman
Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer

Installation is available for RHEL6 and CentOS 6 and requires EPEL and
the SCL to be enabled. Our recommended approach is a set of scripts
available in our deployment repository. Instructions can be found in the
deployment repository’s README at:

https://github.com/Katello/katello-deploy

This repository provides methods for installation on an existing VM or
using Vagrant with libvirt to deploy to CentOS.

The installer git repository is located at:

https://github.com/Katello/katello-installer

And available in our nightly RHEL6 repo:

http://fedorapeople.org/groups/katello/releases/yum/
nightly/RHEL/6Server/x86_64/

Thanks to inecas, jsherrill, mccun934, jmontleon and all those that
contributed module work, RPM work, puppet knowledge or early user testing.

Happy testing!
Eric

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

ekohl · January 23, 2014, 2:38pm

> >>Howdy!
> >>
> >>We are proud to announce that the Katello installer work has finally
> >>reached an alpha stage that is ready for user testing. This installer
> >>takes the enginification work of Katello and installs it alongside
> >>Foreman to bring the full seamless experience of Foreman+Katello. We ask
> >>for anyone willing to jump in and test to do so. Please record feedback
> >>and issues either:
> >>
> >>Redmine - Foreman
> >>Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer
> >>
> >>Installation is available for RHEL6 and CentOS 6 and requires EPEL and
> >>the SCL to be enabled. Our recommended approach is a set of scripts
> >>available in our deployment repository. Instructions can be found in the
> >>deployment repository's README at:
> >>
> >>https://github.com/Katello/katello-deploy
> >>
> >>This repository provides methods for installation on an existing VM or
> >>using Vagrant with libvirt to deploy to CentOS.
> >>
> >>The installer git repository is located at:
> >>
> >>https://github.com/Katello/katello-installer
> >>
> >>And available in our nightly RHEL6 repo:
> >>
> >>http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/
> >>
> >>
> >>Thanks to inecas, jsherrill, mccun934, jmontleon and all those that
> >>contributed module work, RPM work, puppet knowledge or early user
> >>testing.
> >
> >RHEL 6.4 minimal install gets me this:
> >
> >Complete!
> >Could not get default values, check log file at
> >/var/log/katello/katello-install/katello-install.log for more information
> > inet 192.168.100.163/24 brd 192.168.100.255 scope global eth0
> >[root@sat6 katello-deploy]# vi
> >/var/log/katello/katello-install/katello-install.log
> >[root@sat6 katello-deploy]# rpm -qa | grep puppet
> >puppet-2.7.23-1.el6.noarch
> >python-pulp-puppet-common-2.3.1-1.el6.noarch
> >pulp-puppet-plugins-2.3.1-1.el6.noarch
> >[root@sat6 katello-deploy]#
> >
> ok… once I got passed the fqdn error it installed fine. Couple of
> comments so far:
>
> 1) Would be nice to have a check for FQDN.

github.com

theforeman/foreman-installer/blob/develop/checks/hostname.rb

#!/usr/bin/env ruby

BASE = %q(If needed, change the hostname permanently via the
'hostname' or 'hostnamectl set-hostname' command 
and editing the appropriate configuration file.
(e.g. on Red Hat systems /etc/sysconfig/network, 
on Debian based systems /etc/hostname).

If 'hostname -f' still returns an unexpected result, check /etc/hosts and put
the hostname entry in the correct order, for example:
 
  1.2.3.4 full.hostname.com full
 
The fully qualified hostname must be the first entry on the line)

DIFFERENT = %q(Output of 'facter fqdn' is different from 'hostname -f'
 
Make sure above command gives the same output. )

INVALID = %q(Output of 'hostname -f' does not seems to be valid FQDN

This file has been truncated. show original

> 2) Would be nice to report some success or message when done…
> saying "You can log in at XXXX"

github.com

theforeman/foreman-installer/blob/develop/bin/foreman-installer#L69-L73


#!/usr/bin/env ruby
require 'rubygems'
require 'kafo'


CONFIG_DIR = 'config/'


# Run the install
@result = Kafo::KafoConfigure.run


# handle exit code when help was invoked or installer ended with '2' (success in puppet)
if @result.nil? || (!@result.config.app[:detailed_exitcodes] && @result.exit_code == 2)
exit(0)
else
exit(@result.exit_code)
end

> 3) Is it a security problem defaulting the user password?

It is something we would like to solve in foreman-installer as well, but
haven't gotten around to. Patches welcome

···

On Thu, Jan 23, 2014 at 09:34:43AM -0500, Bryan Kearney wrote: > On 01/23/2014 08:29 AM, Bryan Kearney wrote: > >On 01/22/2014 06:23 PM, Eric D Helms wrote:

Gavin_Williams · January 23, 2014, 12:00pm

Eric

Puppet 3.4.2 was installed using Yum:
[vagrant@katello katello-deploy]$ rpm -qa |grep puppet
puppet-3.4.2-1.el6.noarch
pulp-puppet-plugins-2.3.1-1.el6.noarch
puppetlabs-release-6-7.noarch
python-pulp-puppet-common-2.3.1-1.el6.noarch

Will wait for your fix before going any further

Cheers
Gavin

···

On Thursday, 23 January 2014 11:57:38 UTC, Eric Helms wrote: > > Gavin - I know the issue you speak of and will fix today. Stems from our > testing originally on puppet 2.7 and not 3+. You can install 2.7 with just > 'yum install puppet' in the meantime while we work on a fix. > > Eric > On Jan 23, 2014 5:07 AM, "Gavin Williams" <fatm...@gmail.com > > wrote: > >> Thought I'd see if it would continue with fixing that error in the >> manifest... >> >> However hit the same error again on a different manifest: >> >> [DEBUG 2014-01-23 10:02:18 main] Generating new random seed in >>> /etc/katello/keystore_password-file >>> ^[[1;31mError: custom functions must be called with a single array that >>> contains the arguments. For example, function_example([1]) instead of >>> function_example(1) at >>> /usr/share/katello-installer/modules/certs/manifests/params.pp:58 on node >>> katello.dt0388.test >>> Wrapped exception: >>> custom functions must be called with a single array that contains the >>> arguments. For example, function_example([1]) instead of >>> function_example(1)^[[0m >>> ^[[1;31mError: custom functions must be called with a single array that >>> contains the arguments. For example, function_example([1]) instead of >>> function_example(1) at >>> /usr/share/katello-installer/modules/certs/manifests/params.pp:58 on node >>> katello.dt0388.test^[[0m >>> >>> >> After fixing that, I get: >> >> [DEBUG 2014-01-23 10:02:47 main] ^[[1;31mError: can't convert Array into >>> String at >>> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node >>> katello.dt0388.test >>> Wrapped exception: >>> can't convert Array into String^[[0m >>> ^[[1;31mError: can't convert Array into String at >>> /usr/share/katello-installer/modules/katello/manifests/params.pp:80 on node >>> katello.dt0388.test^[[0m >>> >>> [ERROR 2014-01-23 10:02:47 main] Could not get default values, cannot >>> continue >>> >>> >> Will look at that one next... :) >> >> Gav >> >> On Thursday, 23 January 2014 10:02:09 UTC, Gavin Williams wrote: >>> >>> Morning all >>> >>> Thought I'd give this a spin... >>> >>> Created a fresh Centos 6 install using Vagrant and Vbox on Windows 7. >>> >>> First stage of bootstrap process worked fine, with yum installing 344 >>> packages. >>> However got a failure when running "*katello-installer -v -d*". >>> >>> Failure was: >>> >>> Complete! >>>> Could not get default values, check log file at >>>> /var/log/katello/katello-install/katello-install.log for more >>>> information >>>> inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0 >>>> >>> >>> /var/log/katello/katello-install/katello-install.log contains: >>> >>> [ INFO 2014-01-23 09:51:07 main] Parsing default values from puppet >>>> modules... >>>> [DEBUG 2014-01-23 09:51:07 main] echo '$kafo_config_file="/etc/ >>>> katello-installer/katello_installer.yaml" $kafo_add_progress=true >>>> include foreman::params include puppet::params include katello::params >>>> include certs::params dump_values(foreman::params:: >>>> repo,foreman::params::configure_scl_repo,foreman:: >>>> params::selinux,foreman::params::user,foreman::params:: >>>> group,foreman::params::ssl,foreman::params::configure_ >>>> epel_repo,foreman::params::version,foreman::params::user_ >>>> groups,foreman::params::server_ssl_ca,foreman::params: >>>> :authentication,foreman::params::use_vhost,foreman:: >>>> params::organizations_enabled,foreman::params::puppet_home, >>>> foreman::params::locations_enabled,foreman::params:: >>>> passenger_interface,foreman::params::server_ssl_cert, >>>> foreman::params::server_ssl_key,foreman::params::oauth_ >>>> consumer_key,foreman::params::db_manage,foreman::params:: >>>> oauth_active,foreman::params::passenger,foreman::params::db_ >>>> username,foreman::params::app_root,foreman::params:: >>>> passenger_scl,foreman::params::environment,foreman::params:: >>>> apache_conf_dir,foreman::params::oauth_map_users, >>>> foreman::params::foreman_url,foreman::params::unattended, >>>> foreman::params::custom_repo,foreman::params::gpgcheck, >>>> foreman::params::db_password,foreman::params::db_type, >>>> foreman::params::oauth_consumer_secret,puppet:: >>>> params::user,puppet::params::group,puppet::params::listen, >>>> puppet::params::agent_template,puppet::params::port, >>>> puppet::params::server_service_fallback,puppet:: >>>> params::server_passenger_max_pool,puppet::params::server_ >>>> app_root,puppet::params::server_package,puppet::params: >>>> :version,puppet::params::port,puppet::params::classfile, >>>> puppet::params::server_ca,puppet::params::server_git_ >>>> repo_path,puppet::params::server_git_branch_map,foreman: >>>> :params::client_ssl_ca,puppet::params::dir,puppet::params:: >>>> cron_cmd,puppet::params::auth_template,puppet::params:: >>>> group,puppet::params::server_git_repo,puppet::params:: >>>> server_common_modules_path,puppet::params::splay,puppet:: >>>> params::server_vardir,puppet::params::server_passenger, >>>> puppet::params::server_post_hook_name,foreman::params:: >>>> facts,foreman::params::puppet_basedir,puppet::params:: >>>> nsauth_template,puppet::params::server,puppet::params: >>>> :server_external_nodes,puppet::params::server_environments, >>>> puppet::params::server_post_hook_content,puppet::params:: >>>> server_storeconfigs_backend,foreman::params::client_ssl_ >>>> key,puppet::params::pluginsync,puppet::params:: >>>> dir,puppet::params::server_enc_api,foreman::params:: >>>> client_ssl_cert,puppet::params::ca_server,puppet:: >>>> params::server_template,puppet::params::runinterval, >>>> puppet::params::server_httpd_service,puppet::params:: >>>> server_environments_owner,puppet::params::server_envs_ >>>> dir,puppet::params::show_diff,puppet::params::server_ >>>> reports,puppet::params::server_manifest_path,puppet:: >>>> params::server_ssl_dir,puppet::params::server_certname, >>>> foreman::params::puppet_home,puppet::params::runmode, >>>> puppet::params::configtimeout,puppet::params::client_ >>>> package,puppet::params::agent,puppet::params::server_ >>>> dynamic_environments,puppet::params::agent_noop,puppet:: >>>> params::main_template,puppet::params::user,puppet::params:: >>>> server_config_version,puppet::params::server_report_api, >>>> foreman::params::foreman_url,katello::params::user,katello: >>>> :params::group,katello::params::user_groups,katello:: >>>> params::oauth_secret,katello::params::oauth_key,katello:: >>>> params::log_dir,certs::params::regenerate_ca,certs::params:: >>>> expiration,certs::params::node_fqdn,certs::params:: >>>> generate,certs::params::regenerate,certs::params::org, >>>> certs::params::ca_common_name,certs::params::city,certs:: >>>> params::log_dir,certs::params::org_unit,certs::params:: >>>> country,certs::params::state,certs::params::deploy,certs::params::ca_expiration)' >>>> > RUBYLIB=/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/lib/kafo/../..//modules: >>>> puppet apply --modulepath /usr/share/katello-installer/ >>>> modules:/usr/lib/ruby/gems/1.8/gems/kafo-0.3.7/modules 2>&1 >>>> [DEBUG 2014-01-23 09:51:08 main] Generating new random seed in >>>> /etc/katello/oauth_token-file >>>> ^[[1;31mError: custom functions must be called with a single array that >>>> contains the arguments. For example, function_example([1]) instead of >>>> function_example(1) at /usr/share/katello-installer/ >>>> modules/katello/manifests/params.pp:80 on node katello.dt0388.test >>>> Wrapped exception: >>>> custom functions must be called with a single array that contains the >>>> arguments. For example, function_example([1]) instead of >>>> function_example(1)^[[0m >>>> ^[[1;31mError: custom functions must be called with a single array that >>>> contains the arguments. For example, function_example([1]) instead of >>>> function_example(1) at /usr/share/katello-installer/ >>>> modules/katello/manifests/params.pp:80 on node katello.dt0388.test^[[0m >>>> >>>> [ERROR 2014-01-23 09:51:08 main] Could not get default values, cannot >>>> continue >>>> >>> >>> This is with Puppet 3.4.2... >>> >>> Let me know if you need any more info... >>> >>> Gav >>> >>> On Wednesday, 22 January 2014 23:23:50 UTC, Eric Helms wrote: >>>> >>>> Howdy! >>>> >>>> We are proud to announce that the Katello installer work has finally >>>> reached an alpha stage that is ready for user testing. This installer takes >>>> the enginification work of Katello and installs it alongside Foreman to >>>> bring the full seamless experience of Foreman+Katello. We ask for anyone >>>> willing to jump in and test to do so. Please record feedback and issues >>>> either: >>>> >>>> Redmine - http://projects.theforeman.org/projects/katello/issues/new >>>> Public Etherpad - http://pad-katello.rhcloud.com/p/katello-installer >>>> >>>> Installation is available for RHEL6 and CentOS 6 and requires EPEL and >>>> the SCL to be enabled. Our recommended approach is a set of scripts >>>> available in our deployment repository. Instructions can be found in the >>>> deployment repository's README at: >>>> >>>> https://github.com/Katello/katello-deploy >>>> >>>> This repository provides methods for installation on an existing VM or >>>> using Vagrant with libvirt to deploy to CentOS. >>>> >>>> The installer git repository is located at: >>>> >>>> https://github.com/Katello/katello-installer >>>> >>>> And available in our nightly RHEL6 repo: >>>> >>>> http://fedorapeople.org/groups/katello/releases/yum/ >>>> nightly/RHEL/6Server/x86_64/ >>>> >>>> Thanks to inecas, jsherrill, mccun934, jmontleon and all those that >>>> contributed module work, RPM work, puppet knowledge or early user testing. >>>> >>>> Happy testing! >>>> Eric >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >

Dominic_Cleal1 · January 23, 2014, 2:43pm

I've started working on this via
Feature #3272: Separate internal admin account from user admin accounts - Foreman. It's pretty functional so far.

Mostly I've been getting rid of the "admin" account usage internally so
when Foreman does anonymous-type actions as an admin, they run under
another hidden account. This means we can then initialise an account of
the user's choice from the installer via the seed script.

···

On 23/01/14 14:38, Ewoud Kohl van Wijngaarden wrote: >> 3) Is it a security problem defaulting the user password? > It is something we would like to solve in foreman-installer as well, but > haven't gotten around to. Patches welcome :)

–
Dominic Cleal
Red Hat Engineering

ehelms · January 24, 2014, 12:39pm

The nightly Katello installer should now contain a fix for Puppet 3+.
Thanks to all those who are testing!

Eric

···

On Thu, Jan 23, 2014 at 9:43 AM, Dominic Cleal wrote:

On 23/01/14 14:38, Ewoud Kohl van Wijngaarden wrote:

Is it a security problem defaulting the user password?
It is something we would like to solve in foreman-installer as well, but
haven’t gotten around to. Patches welcome

I’ve started working on this via
Feature #3272: Separate internal admin account from user admin accounts - Foreman. It’s pretty functional so
far.

Mostly I’ve been getting rid of the “admin” account usage internally so
when Foreman does anonymous-type actions as an admin, they run under
another hidden account. This means we can then initialise an account of
the user’s choice from the installer via the seed script.

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Gavin_Williams · January 27, 2014, 10:16am

Eric

Can confirm that my install ran through without error after using the
latest installer.

However when I login using the admin account, I am unable to access any of
the Katello screens… I get a '403 - Permission denied' response. Is this
to be expected?

Cheers
Gavin

···

On Friday, 24 January 2014 12:39:14 UTC, Eric Helms wrote: > > The nightly Katello installer should now contain a fix for Puppet 3+. > Thanks to all those who are testing! > > Eric > > > On Thu, Jan 23, 2014 at 9:43 AM, Dominic Cleal <dcl...@redhat.com > > wrote: > >> On 23/01/14 14:38, Ewoud Kohl van Wijngaarden wrote: >> >> 3) Is it a security problem defaulting the user password? >> > It is something we would like to solve in foreman-installer as well, but >> > haven't gotten around to. Patches welcome :) >> >> I've started working on this via >> http://projects.theforeman.org/issues/3272. It's pretty functional so >> far. >> >> Mostly I've been getting rid of the "admin" account usage internally so >> when Foreman does anonymous-type actions as an admin, they run under >> another hidden account. This means we can then initialise an account of >> the user's choice from the installer via the seed script. >> >> -- >> Dominic Cleal >> Red Hat Engineering >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >

ohadlevy · January 27, 2014, 11:51am

> Eric
>
> Can confirm that my install ran through without error after using the
> latest installer.
>
> However when I login using the admin account, I am unable to access any of
> the Katello screens… I get a '403 - Permission denied' response. Is this
> to be expected?
>

it seems you need to be in an org first (any context wont work atm).

Ohad

···

On Mon, Jan 27, 2014 at 12:16 PM, Gavin Williams wrote:

Cheers
Gavin

On Friday, 24 January 2014 12:39:14 UTC, Eric Helms wrote:

The nightly Katello installer should now contain a fix for Puppet 3+.
Thanks to all those who are testing!

Eric

On Thu, Jan 23, 2014 at 9:43 AM, Dominic Cleal dcl...@redhat.com wrote:

On 23/01/14 14:38, Ewoud Kohl van Wijngaarden wrote:

Is it a security problem defaulting the user password?
It is something we would like to solve in foreman-installer as well,
but
haven’t gotten around to. Patches welcome

I’ve started working on this via
Feature #3272: Separate internal admin account from user admin accounts - Foreman. It’s pretty functional so
far.

Mostly I’ve been getting rid of the “admin” account usage internally so
when Foreman does anonymous-type actions as an admin, they run under
another hidden account. This means we can then initialise an account of
the user’s choice from the installer via the seed script.

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Gavin_Williams · January 27, 2014, 2:36pm

Cool, selecting 'ACME_Corporation' gives me access to the Katello
screens…

Now to work out how this is supposed to work

Cheers
Gav

···

On Monday, 27 January 2014 11:51:37 UTC, ohadlevy wrote: > > > > > On Mon, Jan 27, 2014 at 12:16 PM, Gavin Williams <fatm...@gmail.com > > wrote: > >> Eric >> >> Can confirm that my install ran through without error after using the >> latest installer. >> >> However when I login using the admin account, I am unable to access any >> of the Katello screens... I get a '403 - Permission denied' response. Is >> this to be expected? >> > > it seems you need to be in an org first (any context wont work atm). > > Ohad > >> >> Cheers >> Gavin >> >> On Friday, 24 January 2014 12:39:14 UTC, Eric Helms wrote: >> >>> The nightly Katello installer should now contain a fix for Puppet 3+. >>> Thanks to all those who are testing! >>> >>> Eric >>> >>> >>> On Thu, Jan 23, 2014 at 9:43 AM, Dominic Cleal wrote: >>> >>>> On 23/01/14 14:38, Ewoud Kohl van Wijngaarden wrote: >>>> >> 3) Is it a security problem defaulting the user password? >>>> > It is something we would like to solve in foreman-installer as well, >>>> but >>>> > haven't gotten around to. Patches welcome :) >>>> >>>> I've started working on this via >>>> http://projects.theforeman.org/issues/3272. It's pretty functional so >>>> far. >>>> >>>> Mostly I've been getting rid of the "admin" account usage internally so >>>> when Foreman does anonymous-type actions as an admin, they run under >>>> another hidden account. This means we can then initialise an account of >>>> the user's choice from the installer via the seed script. >>>> >>>> -- >>>> Dominic Cleal >>>> Red Hat Engineering >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "foreman-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to foreman-dev...@googlegroups.com. >>>> >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> > >