Katello 2.2.2 Released

Katello 2.2.2 has been officially released and includes a number of bug
fixes. See below for links to installation and upgrade instructions. A big
thanks to all our users and testers.

Notable Fixes:

  • Product content tabs on Content Hosts and Activation Keys should now work
  • Content view promotion and repository sync won't error out on mail
    notifications
  • Capsule syncs will now timeout if the Capsule is unreachable
  • Puppet environments will no longer be generated for content views that
    do not contain puppet modules
  • Custom certs will not cause errors due to mis-configuration

A full list of the changes in Katello 2.2 is in our release notes:
http://www.katello.org/docs/2.2/release_notes/release_notes.html

Installation or Upgrade

··· ================ Please be sure to check out the new client installation and upgrade documentation that was added for this release.

For installation, please see the instructions at:
Server: http://www.katello.org/docs/2.2/installation/index.html
Capsule: http://www.katello.org/docs/2.2/installation/capsule.html
Clients: http://www.katello.org/docs/2.2/installation/clients.html
http://www.katello.org/docs/2.2/installation/capsule.html

Please note that there are separate upgrade instructions for
the Katello server, Capsules and Clients.
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html
Capsule: http://www.katello.org/docs/2.2/upgrade/clients.html
http://www.katello.org/docs/2.2/upgrade/capsule.html

The GPG key used for RPMs and tarballs has the following fingerprint:
9989 7EB9 7C93 C5A6 A193 3C45 082D 4CD3 BC62 D13F

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello that you’re using in the report and set
the release to 2.2.2

Some issues are still waiting more information or are actively being worked
on for 2.2.2

http://projects.theforeman.org/projects/katello/issues/new

Thanks again to all our users and testers!


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

Eric,

I get a complaint during http://www.katello.org/docs/2.2/upgrade/index.html

  • "Step 4 - Update Packages", yum -y update:

(45/46): ruby193-rubygem-katello-2.2.2-2.el7.noarch.rpm
> 2.7 MB 00:00:13
(46/46): kernel-3.10.0-229.7.2.el7.x86_64.rpm

··· > 31 MB 00:00:22 ------------------------------------------------------------------------------------------------------------------------- Total 1.9 MB/s | 48 MB 00:00:25

Package ruby193-rubygem-katello-2.2.2-2.el7.noarch.rpm is not signed
[root@foreman ~]#

and there’s also a complaint during the download part of the yum command:

(33/46): gnutls-utils-3.3.8-12.el7_1.1.x86_64.rpm
> 228 kB 00:00:00
Package katello-installer-2.2.2-1.el7.noarch.rpm is not signed=======
] 1.6 MB/s | 11 MB 00:00:23 ETA
(34/46): katello-installer-2.2.2-1.el7.noarch.rpm
> 31 kB 00:00:03

Fixed with a yum -y --nogpgcheck update, but thought I’d mention it.

Question: If I already upgraded to Foreman 1.8.2, will this cause issues
upgrading to Katello 2.2.2?

My upgrade was to a system that had previously had the Foreman 1.8.2
updates. Apart from having to use --nogpgcheck for the yum updates, the
upgrade was very smooth.

D

··· On Thursday, 25 June 2015 15:24:04 UTC+1, lawre wrote: > > Question: If I already upgraded to Foreman 1.8.2, will this cause issues > upgrading to Katello 2.2.2? >

Thanks for letting us know about the unsigned packages, we'll get that
fixed.

The upgrade process shouldn't affect the previously upgraded Foreman bits.

··· On Jun 25, 2015 10:24 AM, "lawre" wrote:

Question: If I already upgraded to Foreman 1.8.2, will this cause issues
upgrading to Katello 2.2.2?


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/d/optout.

This should now be resolved, let me know if you see any packages that
may have missed signing.
Thanks,
-Justin

··· On 06/25/2015 06:47 AM, Duncan Innes wrote: > Eric, > > I get a complaint > during http://www.katello.org/docs/2.2/upgrade/index.html - "Step 4 - > Update Packages", yum -y update: > > (45/46): ruby193-rubygem-katello-2.2.2-2.el7.noarch.rpm > > 2.7 MB 00:00:13 > (46/46): kernel-3.10.0-229.7.2.el7.x86_64.rpm > > 31 MB 00:00:22 > ------------------------------------------------------------------------------------------------------------------------- > Total 1.9 MB/s | 48 MB 00:00:25 > > Package ruby193-rubygem-katello-2.2.2-2.el7.noarch.rpm is not signed > [root@foreman ~]# > > and there's also a complaint during the download part of the yum command: > > (33/46): gnutls-utils-3.3.8-12.el7_1.1.x86_64.rpm > > 228 kB 00:00:00 > Package katello-installer-2.2.2-1.el7.noarch.rpm is not signed======= > ] 1.6 MB/s | 11 MB 00:00:23 ETA > (34/46): katello-installer-2.2.2-1.el7.noarch.rpm > > 31 kB 00:00:03 > > Fixed with a `yum -y --nogpgcheck update`, but thought I'd mention it. > > -- > 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/d/optout.

Although I get a successful result, there is a task blocking the
upgrade. The installer should break otherwise someone not paying
attention will break things. At least display the task I need to
resume/unlock.

Even better, it would be nice if the installer would check this at the
start and abort upgrading until the task gets unlocked.

Katello upgrade completed!
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:104:in
`error': wrong number of arguments (11 for 1) (ArgumentError)
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:104:in `send'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:104:in
`dump_buffer'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:104:in `each'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:104:in
`dump_buffer'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:103:in `each'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:103:in
`dump_buffer'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:94:in
`dump_errors'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/logger.rb:99:in
`dump_errors'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/exit_handler.rb:26:in `exit'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/kafo_configure.rb:124:in
`exit'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/kafo_configure.rb:341:in
`run_installation'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/kafo_configure.rb:111:in
`execute'
    from
/usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:68:in `run'
    from
/usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:126:in
`run'
    from
/usr/lib/ruby/gems/1.8/gems/kafo-0.6.6/lib/kafo/kafo_configure.rb:118:in
`run'
    from /usr/sbin/katello-installer:46

From the log:

[ INFO 2015-06-26 12:55:07 main] Upgrade Step: Update repositories
to specify metadata_expire (this may take a while)...
[ERROR 2015-06-26 12:56:33 main] rake aborted!
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.

Required lock: read
Conflicts with tasks:
··· On 06/25/2015 05:22 PM, Duncan Innes wrote: > My upgrade was to a system that had previously had the Foreman 1.8.2 > updates. Apart from having to use --nogpgcheck for the yum updates, > the upgrade was very smooth. > > D > > On Thursday, 25 June 2015 15:24:04 UTC+1, lawre wrote: > > Question: If I already upgraded to Foreman 1.8.2, will this cause > issues upgrading to Katello 2.2.2? > >
-
https://katello.netbulae.test/foreman_tasks/tasks/1774780d-18cb-4a6a-b711-f1c608d73da4

Tasks: TOP => katello:upgrades:2.2:update_metadata_expire
(See full trace by running task with --trace)

[DEBUG 2015-06-26 12:56:33 main] Hook
/usr/share/katello-installer/hooks/post/30-upgrade.rb returned
[<Logging::Logger:0x3ff16a0b5a68 name="main">,
<Logging::Logger:0x3ff16a09ce64 name="fatal">]
[ INFO 2015-06-26 12:56:33 main] All hooks in group post finished
[DEBUG 2015-06-26 12:56:33 main] Exit with status code: 2 (signal was 2)
[ERROR 2015-06-26 12:56:33 main] Repeating errors encountered during
run:
[ERROR 2015-06-26 12:56:33 main] <NilClass> nil

For the rest, thanks for the update, it is a really nice piece of software!

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts


Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

Hi Justin,

··· Am 26.06.2015 um 19:08 schrieb Justin Sherrill: > On 06/25/2015 06:47 AM, Duncan Innes wrote: >> Eric, >> >> I get a complaint >> during http://www.katello.org/docs/2.2/upgrade/index.html - "Step 4 - >> Update Packages", yum -y update: >> >> (45/46): ruby193-rubygem-katello-2.2.2-2.el7.noarch.rpm >> > 2.7 MB 00:00:13 >> (46/46): kernel-3.10.0-229.7.2.el7.x86_64.rpm >> > 31 MB 00:00:22 >> ------------------------------------------------------------------------------------------------------------------------- >> Total >> 1.9 MB/s | 48 MB 00:00:25 >> >> Package ruby193-rubygem-katello-2.2.2-2.el7.noarch.rpm is not signed >> [root@foreman ~]# >> >> and there's also a complaint during the download part of the yum command: >> >> (33/46): gnutls-utils-3.3.8-12.el7_1.1.x86_64.rpm >> > 228 kB 00:00:00 >> Package katello-installer-2.2.2-1.el7.noarch.rpm is not signed======= >> ] 1.6 MB/s | 11 MB 00:00:23 ETA >> (34/46): katello-installer-2.2.2-1.el7.noarch.rpm >> > 31 kB 00:00:03 >> >> Fixed with a `yum -y --nogpgcheck update`, but thought I'd mention it. >> >> > This should now be resolved, let me know if you see any packages that > may have missed signing. > Thanks, > -Justin

https://fedorapeople.org/groups/katello/releases/yum/2.2/katello/RHEL/7Server/x86_64/katello-utils-2.2.0-1.el7.noarch.rpm
isn’t signed, too.

Regards
Andreas