Foreman 1.3 RC4 is ready for testing

Release Announcements
1

Hello all,

Foreman 1.3 RC4 has been released today. This is the last Release
Candidate, if there are no bugs, final version is announced later this
week.

Please read BEFORE YOU UPGRADE section bellow first.

Key features:

  • Foreman CLI
  • Bare metal migration
  • Installer auto-registers smart-proxy
  • Compute resources and VNC/Spice
  • LDAP filtering
  • Host IP updating
  • New foreman-rake command
  • Plugins as RPM packages
  • API v2 improvements

Full release notes:
http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3

==== BEFORE YOU UPGRADE ====

Big changes are coming in the 1.3 release and due to introduction of foreign
keys in Foreman database, we urgue you to backup your instance prior upgrading.
The migration process will delete all orphaned records!

Also, the way facts and reports are uploaded was changed. Specifically, Foreman
itself now uses a JSON format, and the ENC (node.rb) and Puppet report
processor (foreman.rb) have been updated to handle changing Puppet-specific
data into JSON. Existing ENC/Reports scripts will need a change to the latest
version, which can be found in the installer git repository:

  • external_node_v2.rb.erb
  • foreman-report_v2.rb.erb

If reporting is being used, please update these scripts during the upgrade.

==== Packages ====

Package repos are available here:
http://yum.theforeman.org/rc/el6/x86_64/
http://yum.theforeman.org/rc/f18/x86_64/
http://yum.theforeman.org/rc/f19/x86_64/
http://deb.theforeman.org/ ("rc" component)

Quickstart instructions are here:
http://theforeman.org/manuals/1.3/index.html#2.Quickstart

Tarballs available here:
http://projects.theforeman.org/projects/foreman/files

==== Installation ====

There is a new installer for Foreman 1.3, it has many new options that are
taken directly from puppet class parameters. Check the help screen or install
with default options directly:

foreman-installer

Our new installer now provides many configuration options, or you can still
use interactive mode. Use --help for more info.

==== Known issues ====

** Proxy registration happens before Apache is started **

You may encounter failure during proxy registration (Foreman_smartproxy puppet
class). In that case if you see 404 error while registering proxy, please
re-run the installer and the error should disappear.

http://projects.theforeman.org/issues/3083

==== Reporting issues ====

Please report issues found in Foreman 1.3 in redmine.

Foreman: Foreman
Proxy: Foreman
Installer: Foreman

Existing bug reports are listed here:
http://projects.theforeman.org/projects/foreman/issues?query_id=24

The new foreman-debug script can be used to collect and provide information
about your setup, and the result attached to bug reports.

Thanks for using Foreman and please do spread the word.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

2

Hi,

Using the RC4 installer modules in my environment, I get :

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at /etc/puppet/envs/dev/puppet/mysql/manifests/db.pp:76 on node xxxx
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Commenting out the "provider" argument in the mysql/manifests/db.pp at each occurrence gets rid of the issue.

My puppet master is :

rpm -q puppet-server

puppet-server-3.2.4-1.el6.noarch

My agent :

rpm -q puppet

puppet-3.3.0-1.el6.noarch

I realize my agent on that node is newer than the master version (it's in a staging environment), so this might be the cause, but I will in fact upgrade the master only when this specific node is configured and correctly upgraded to foreman 1.3…

(I'm configuring the foreman/puppetmaster using a puppetmaster and calling the foreman/foreman_proxy modules)

Regard

··· > -----Message d'origine----- > De : foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] De la part de Lukas Zapletal > Envoyé : mardi 8 octobre 2013 13:58 > À : foreman-announce@googlegroups.com; foreman-users@googlegroups.com > Objet : [foreman-users] Foreman 1.3 RC4 is ready for testing > > Hello all, > > Foreman 1.3 RC4 has been released today. This is the last Release > Candidate, if there are no bugs, final version is announced later this > week. > > Please read BEFORE YOU UPGRADE section bellow first. > > Key features: > > * Foreman CLI > * Bare metal migration > * Installer auto-registers smart-proxy > * Compute resources and VNC/Spice > * LDAP filtering > * Host IP updating > * New foreman-rake command > * Plugins as RPM packages > * API v2 improvements > > Full release notes: > http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3 > > ==== BEFORE YOU UPGRADE ==== > > Big changes are coming in the 1.3 release and due to introduction of foreign > keys in Foreman database, we urgue you to backup your instance prior upgrading. > The migration process *will delete* all orphaned records! > > Also, the way facts and reports are uploaded was changed. Specifically, Foreman > itself now uses a JSON format, and the ENC (node.rb) and Puppet report > processor (foreman.rb) have been updated to handle changing Puppet-specific > data into JSON. Existing ENC/Reports scripts will need a change to the latest > version, which can be found in the installer git repository: > > - external_node_v2.rb.erb > - foreman-report_v2.rb.erb > > If reporting is being used, please update these scripts during the upgrade. > > ==== Packages ==== > > Package repos are available here: > http://yum.theforeman.org/rc/el6/x86_64/ > http://yum.theforeman.org/rc/f18/x86_64/ > http://yum.theforeman.org/rc/f19/x86_64/ > http://deb.theforeman.org/ ("rc" component) > > Quickstart instructions are here: > http://theforeman.org/manuals/1.3/index.html#2.Quickstart > > Tarballs available here: > http://projects.theforeman.org/projects/foreman/files > > ==== Installation ==== > > There is a new installer for Foreman 1.3, it has many new options that are > taken directly from puppet class parameters. Check the help screen or install > with default options directly: > > foreman-installer > > Our new installer now provides many configuration options, or you can still > use interactive mode. Use --help for more info. > > ==== Known issues ==== > > ** Proxy registration happens before Apache is started ** > > You may encounter failure during proxy registration (Foreman_smartproxy puppet > class). In that case if you see 404 error while registering proxy, please > re-run the installer and the error should disappear. > > http://projects.theforeman.org/issues/3083 > > ==== Reporting issues ==== > > Please report issues found in Foreman 1.3 in redmine. > > Foreman: http://projects.theforeman.org/projects/foreman/issues/new > Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new > Installer: http://projects.theforeman.org/projects/kafo/issues/new > > Existing bug reports are listed here: > http://projects.theforeman.org/projects/foreman/issues?query_id=24 > > The new foreman-debug script can be used to collect and provide information > about your setup, and the result attached to bug reports. > > Thanks for using Foreman and please do spread the word. > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.
3

This usually indicates a problem with provider pluginsyncing and
multiple environments in Puppet.

Try adding the MySQL module at least to the environment your master is
in and then run the agent on the master so the plugins get synced to
the master's own /var/lib/puppet/lib.

See also: http://projects.puppetlabs.com/issues/17814

··· On 09/10/13 16:37, SCHAER Frederic wrote: > Hi, > > Using the RC4 installer modules in my environment, I get : > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at /etc/puppet/envs/dev/puppet/mysql/manifests/db.pp:76 on node xxxx > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > > Commenting out the "provider" argument in the mysql/manifests/db.pp at each occurrence gets rid of the issue. > > My puppet master is : > # rpm -q puppet-server > puppet-server-3.2.4-1.el6.noarch > > My agent : > # rpm -q puppet > puppet-3.3.0-1.el6.noarch > > I realize my agent on that node is newer than the master version (it's in a staging environment), so this might be the cause, but I will in fact upgrade the master only when this specific node is configured and correctly upgraded to foreman 1.3... > > (I'm configuring the foreman/puppetmaster using a puppetmaster and calling the foreman/foreman_proxy modules)

–
Dominic Cleal
Red Hat Engineering

4

> -----Message d'origine-----
> De : foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] De la part de Dominic Cleal
> Envoyé : mercredi 9 octobre 2013 18:13
> À : foreman-users@googlegroups.com
> Objet : Re: [foreman-users] Foreman 1.3 RC4 is ready for testing
>
> > Hi,
> >
> > Using the RC4 installer modules in my environment, I get :
> >
> > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at
> /etc/puppet/envs/dev/puppet/mysql/manifests/db.pp:76 on node xxxx
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> >
> > Commenting out the "provider" argument in the mysql/manifests/db.pp at each occurrence gets rid of the issue.
> >
> > My puppet master is :
> > # rpm -q puppet-server
> > puppet-server-3.2.4-1.el6.noarch
> >
> > My agent :
> > # rpm -q puppet
> > puppet-3.3.0-1.el6.noarch
> >
> > I realize my agent on that node is newer than the master version (it's in a staging environment), so this might be the
> cause, but I will in fact upgrade the master only when this specific node is configured and correctly upgraded to foreman
> 1.3…
> >
> > (I'm configuring the foreman/puppetmaster using a puppetmaster and calling the foreman/foreman_proxy modules)
>
> This usually indicates a problem with provider pluginsyncing and
> multiple environments in Puppet.
>
> Try adding the MySQL module at least to the environment your master is
> in and then run the agent on the master so the plugins get synced to
> the master's own /var/lib/puppet/lib.
>
> See also: http://projects.puppetlabs.com/issues/17814
>
> –
> Dominic Cleal
> Red Hat Engineering
>

Hi,

Thanks for the link && quick answer . It really looks like a pluginsync issue indeed - now I have issues with other foreman modules that I did upgrade (in dev), and worse, puppet seems to be completely lost and scans hundreds of thousands of times for the same files in the ruby directory : it is attempting to lookup each of my classes as a classname::subname.rb in every gem subdir… possibly multiple times as I lost the strace counts. Odd behavior.

Well actually I can't include the new mysql module in production, since the old mysql module is already included in my main puppetmaster classes…
I guess I'll have to finish my "foreman installer" upgrade with "puppet apply" and push that upgrade to the main puppetmaster before I go on with trying the RC4

Regards

··· > On 09/10/13 16:37, SCHAER Frederic wrote: