Katello 2.2 RC3

This marks the third release candidate for the 2.2 release. This release
includes missing installer changes that enable the qpid dispatch router,
issues with org destroy, sync plan fixes and a few other fixes reported by
users during the previous release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

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

··· ================ 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

For those testing upgrades, please use the instructions below and file any
issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html

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.

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

One caveat I found just after sending this, if you install a capsule you
may find the Apache fails to start. This is due to the installer not
requiring the katello-debug package (which I have opened an issue to fix).
You can manually install this package, however, on your capsule and then
re-run the installer (or run it for the first time).

Eric

··· On Tue, Apr 7, 2015 at 9:25 AM, Eric D Helms wrote:

This marks the third release candidate for the 2.2 release. This release
includes missing installer changes that enable the qpid dispatch router,
issues with org destroy, sync plan fixes and a few other fixes reported by
users during the previous release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

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

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

For those testing upgrades, please use the instructions below and file any
issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html

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.

Foreman

Just reinstalled from scratch…

Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Security] error
Rejected un-encrypted connection.
Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Protocol] error
Connection qpid.127.0.0.1:5672-127.0.0.1:39501 closed by error:
connection-forced: Connection must be encrypted.(320)

How do I fix this? I mean how to make an encrypted connection???

··· On Tuesday, April 7, 2015 at 9:25:53 PM UTC+8, Eric Helms wrote: > > This marks the third release candidate for the 2.2 release. This release > includes missing installer changes that enable the qpid dispatch router, > issues with org destroy, sync plan fixes and a few other fixes reported by > users during the previous release candidates. > > All help is appreciated to ensure our dot-zero release is solid, either > installing a new instance or upgrading a test server. > > 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 > ================ > 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 > > For those testing upgrades, please use the instructions below and file any > issues you encounter. Please note that there are separate upgrade > instructions for the Katello server and Capsules > Server: http://www.katello.org/docs/2.2/upgrade/index.html > Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html > > > 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. > > http://projects.theforeman.org/projects/katello/issues/new >

Just a comment that the installer still writes a "config_version = {blank}"
to the [master] section of /etc/puppet/puppet.conf. It causes deprecation
warnings on every Puppet run on the server.

Still working on testing other functionality.

HTH!

/Mike

··· On Tuesday, 7 April 2015 09:25:53 UTC-4, Eric Helms wrote: > > This marks the third release candidate for the 2.2 release. This release > includes missing installer changes that enable the qpid dispatch router, > issues with org destroy, sync plan fixes and a few other fixes reported by > users during the previous release candidates. > > All help is appreciated to ensure our dot-zero release is solid, either > installing a new instance or upgrading a test server. > > 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 > ================ > 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 > > For those testing upgrades, please use the instructions below and file any > issues you encounter. Please note that there are separate upgrade > instructions for the Katello server and Capsules > Server: http://www.katello.org/docs/2.2/upgrade/index.html > Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html > > > 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. > > http://projects.theforeman.org/projects/katello/issues/new >

At this time, we don't do any RC to RC upgrade testing ourselves. On a box
I had setup with RC2 I did the following after releasing RC3:

yum update ruby193-rubygem-katello katello-installer
katello-installer

My instance appears to be fine at the moment (without extensive testing) so
please do give upgrading a try and report any issues you encounter.

Eric

··· On Tue, Apr 7, 2015 at 11:02 AM, Andrew Lau wrote:

Does this guide apply for upgrading from RC2?
http://www.katello.org/docs/2.2/upgrade/index.html

On Wednesday, 8 April 2015 00:06:16 UTC+10, Eric Helms wrote:

One caveat I found just after sending this, if you install a capsule you
may find the Apache fails to start. This is due to the installer not
requiring the katello-debug package (which I have opened an issue to fix).
You can manually install this package, however, on your capsule and then
re-run the installer (or run it for the first time).

Eric

On Tue, Apr 7, 2015 at 9:25 AM, Eric D Helms ericd...@gmail.com wrote:

This marks the third release candidate for the 2.2 release. This release
includes missing installer changes that enable the qpid dispatch router,
issues with org destroy, sync plan fixes and a few other fixes reported by
users during the previous release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

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

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

For those testing upgrades, please use the instructions below and file
any issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html

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.

Foreman


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.

I have a similar bug report open for that,
http://projects.theforeman.org/issues/9983

··· On 8 April 2015 at 23:11, Peter Santiago wrote:

Just reinstalled from scratch…

Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Security] error
Rejected un-encrypted connection.
Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Protocol] error
Connection qpid.127.0.0.1:5672-127.0.0.1:39501 closed by error:
connection-forced: Connection must be encrypted.(320)

How do I fix this? I mean how to make an encrypted connection???

On Tuesday, April 7, 2015 at 9:25:53 PM UTC+8, Eric Helms wrote:

This marks the third release candidate for the 2.2 release. This release
includes missing installer changes that enable the qpid dispatch router,
issues with org destroy, sync plan fixes and a few other fixes reported by
users during the previous release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

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

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

For those testing upgrades, please use the instructions below and file
any issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html

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.

Foreman


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/vl0enJ8Q1z4/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.

Hi Eric and all others,

first of all thanks for the fast reaction to provide RC3, my regards to all
team members! BTW I followed the offical Upgrade Procedure and so far no
problems…
Even better my issue with Docker Provisioning is solved as well. I can
confirm that Package Push to Clients (TCP5647) is working well…(I will
keep on testing the rest)

THANKS - TODA RABA

Hi Eric,

please be so kind and have a look at
https://groups.google.com/forum/#!topic/foreman-users/_7syhWel0GQ ,in case
you have some free time, maybe you know something…

thanks,
Christian

Andrew and Peter, could you add to the issue (
Bug #9983: qpid rejected un-encrypted connection - Katello - Foreman) your setup (OS, version, etc.)
and steps you took to install (repositories included, whether you used
katello-deploy etc.) to help me generate a reproducer?

··· On Wed, Apr 8, 2015 at 9:13 AM, Andrew Lau wrote:

I have a similar bug report open for that,
Bug #9983: qpid rejected un-encrypted connection - Katello - Foreman

On 8 April 2015 at 23:11, Peter Santiago vanyell2001@gmail.com wrote:

Just reinstalled from scratch…

Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Security]
error Rejected un-encrypted connection.
Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Protocol]
error Connection qpid.127.0.0.1:5672-127.0.0.1:39501 closed by error:
connection-forced: Connection must be encrypted.(320)

How do I fix this? I mean how to make an encrypted connection???

On Tuesday, April 7, 2015 at 9:25:53 PM UTC+8, Eric Helms wrote:

This marks the third release candidate for the 2.2 release. This release
includes missing installer changes that enable the qpid dispatch router,
issues with org destroy, sync plan fixes and a few other fixes reported by
users during the previous release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

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

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

For those testing upgrades, please use the instructions below and file
any issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html

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.

Foreman


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/vl0enJ8Q1z4/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.


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.

All,

I have pushed out a package update to qpid-dispatch and a minor update to
the katello package as part of RC3. The katello change is to include
qdrouterd in the katello-service list and the qdrouterd updates are to
address potential segfault issues that have been found in the older
version. Updating should be as simple as:

yum update katello
katello-service restart

A big thanks to all who are testing the RCs and reporting issues. Your
feedback is highly appreciated!

Eric

··· On Wed, Apr 8, 2015 at 9:47 AM, Eric D Helms wrote:

Andrew and Peter, could you add to the issue (
Bug #9983: qpid rejected un-encrypted connection - Katello - Foreman) your setup (OS, version,
etc.) and steps you took to install (repositories included, whether you
used katello-deploy etc.) to help me generate a reproducer?

On Wed, Apr 8, 2015 at 9:13 AM, Andrew Lau andrew@andrewklau.com wrote:

I have a similar bug report open for that,
Bug #9983: qpid rejected un-encrypted connection - Katello - Foreman

On 8 April 2015 at 23:11, Peter Santiago vanyell2001@gmail.com wrote:

Just reinstalled from scratch…

Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Security]
error Rejected un-encrypted connection.
Apr 8 07:52:58 llin417 qpidd[39741]: 2015-04-08 07:52:58 [Protocol]
error Connection qpid.127.0.0.1:5672-127.0.0.1:39501 closed by error:
connection-forced: Connection must be encrypted.(320)

How do I fix this? I mean how to make an encrypted connection???

On Tuesday, April 7, 2015 at 9:25:53 PM UTC+8, Eric Helms wrote:

This marks the third release candidate for the 2.2 release. This
release includes missing installer changes that enable the qpid dispatch
router, issues with org destroy, sync plan fixes and a few other fixes
reported by users during the previous release candidates.

All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.

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

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

For those testing upgrades, please use the instructions below and file
any issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules
Server: http://www.katello.org/docs/2.2/upgrade/index.html
Capsule: http://www.katello.org/docs/2.2/upgrade/capsule.html

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.

Foreman


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/vl0enJ8Q1z4/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.


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.

With katello 2.2 RC3, getting errors now publishing content views. Tried to
remove the failed views and now I've got an inconsistent state, pulp repo
removed but still exists in katello.

··· On Wednesday, 8 April 2015 16:17:53 UTC+10, ehar...@gmail.com wrote: > > Hi Eric, > > please be so kind and have a look at > https://groups.google.com/forum/#!topic/foreman-users/_7syhWel0GQ ,in > case you have some free time, maybe you know something... > > thanks, > Christian > > >