Following closely on the heels of 2.1, we are happy to announce the first
release candidate for 2.2. This marks the first attempt to release Katello
in nearly lock step with Foreman.
All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.
···
================
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
···
On Friday, March 13, 2015 at 2:38:28 AM UTC+8, Eric Helms wrote:
>
> Following closely on the heels of 2.1, we are happy to announce the first
> release candidate for 2.2. This marks the first attempt to release Katello
> in nearly lock step with Foreman.
>
> 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
>
>
>
Eric,
Is there a list of known issues for this RC anywhere? Wondering about
things like SELinux that had to be disabled for 2.1 installs. Or specific
issues/areas that you'd like tested for this release?
On Friday, March 13, 2015 at 2:38:28 AM UTC+8, Eric Helms wrote:
Following closely on the heels of 2.1, we are happy to announce the first
release candidate for 2.2. This marks the first attempt to release Katello
in nearly lock step with Foreman.
All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.
Ahh yes, that is a great thought. Selinux should be working for 2.2 and
would be awesome to test out.
There is currently an issue with qpid and listening to Candlepin events
that can lead to lots of tasks showing up as well as some users have
reported it blocking other functionality, see http://projects.theforeman.org/issues/9068
Things to test would be:
selinux
upgrades
incremental updates
capsule isolation
Eric
···
On Fri, Mar 13, 2015 at 11:56 AM, Duncan Innes wrote:
Eric,
Is there a list of known issues for this RC anywhere? Wondering about
things like SELinux that had to be disabled for 2.1 installs. Or specific
issues/areas that you’d like tested for this release?
···
On Friday, March 13, 2015 at 8:38:07 PM UTC+8, Eric Helms wrote:
>
> Does the epel repo have a higher priority? You can see here
> https://fedorapeople.org/groups/katello/releases/yum/2.2/pulp/RHEL/6Server/x86_64/
> that the python-gofer package we are expecting to get pulled in is
> available.
>
> Eric
>
> On Fri, Mar 13, 2015 at 4:47 AM, Peter Santiago > wrote:
>
>> installing using katello-deploy: ./setup.rb --version 2.2
>> --skip-installer
>>
>> Error: Package: pulp-server-2.6.0-0.7.beta.el6.noarch (katello-pulp)
>> Requires: python-gofer >= 2.5
>> Available: python-gofer-0.74-1.el6.noarch (epel)
>> python-gofer = 0.74-1.el6
>> Error: Package: python-gofer-qpid-2.5.3-1.el6.noarch (katello-pulp)
>> Requires: python-gofer = 2.5.3
>> Available: python-gofer-0.74-1.el6.noarch (epel)
>> python-gofer = 0.74-1.el6
>>
>> Where to get the required oython-gofer packages?
>>
>>
>> On Friday, March 13, 2015 at 2:38:28 AM UTC+8, Eric Helms wrote:
>>>
>>> Following closely on the heels of 2.1, we are happy to announce the
>>> first release candidate for 2.2. This marks the first attempt to release
>>> Katello in nearly lock step with Foreman.
>>>
>>> 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
>>>
>>>
>>> --
>> 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
Oops… seems that the katello-deploy script is reinstalling epel-release
package… overwriting the priority line in epel.repo and the rest…
···
On Friday, March 13, 2015 at 8:53:59 PM UTC+8, Peter Santiago wrote:
>
> Neat... Thanks for the pointer...
>
> On Friday, March 13, 2015 at 8:38:07 PM UTC+8, Eric Helms wrote:
>>
>> Does the epel repo have a higher priority? You can see here
>> https://fedorapeople.org/groups/katello/releases/yum/2.2/pulp/RHEL/6Server/x86_64/
>> that the python-gofer package we are expecting to get pulled in is
>> available.
>>
>> Eric
>>
>> On Fri, Mar 13, 2015 at 4:47 AM, Peter Santiago >> wrote:
>>
>>> installing using katello-deploy: ./setup.rb --version 2.2
>>> --skip-installer
>>>
>>> Error: Package: pulp-server-2.6.0-0.7.beta.el6.noarch (katello-pulp)
>>> Requires: python-gofer >= 2.5
>>> Available: python-gofer-0.74-1.el6.noarch (epel)
>>> python-gofer = 0.74-1.el6
>>> Error: Package: python-gofer-qpid-2.5.3-1.el6.noarch (katello-pulp)
>>> Requires: python-gofer = 2.5.3
>>> Available: python-gofer-0.74-1.el6.noarch (epel)
>>> python-gofer = 0.74-1.el6
>>>
>>> Where to get the required oython-gofer packages?
>>>
>>>
>>> On Friday, March 13, 2015 at 2:38:28 AM UTC+8, Eric Helms wrote:
>>>>
>>>> Following closely on the heels of 2.1, we are happy to announce the
>>>> first release candidate for 2.2. This marks the first attempt to release
>>>> Katello in nearly lock step with Foreman.
>>>>
>>>> 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
>>>>
>>>>
>>>> --
>>> 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-user...@googlegroups.com.
>>> To post to this group, send email to forema...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
Will look into SELinux then. Forgot to change it back to Enforcing (my
Katello 2.2 kickstart) from Disabled (my Katello 2.1 kickstart) when I ran
my first install. Rebuilding the guest again now to see if it comes
through clean in Enforcing mode.
