Katello 2.1.1 Released

Hi All,

A minor update to Katello 2.1 has been released.

Highlighted fixes include:

  • el7 installation issues on slower systems
  • upgrade issues related with errata importing
  • Content View Deletion errors

For a full change log see:

Upgrading from 2.1.0:

··· ================

To update to the new packages:

  • yum update
  • katello-service restart

Thanks to all the uses and developers for filing and fixing issues and
making 2.1.1 a possibility!

Katello 2.1.2

There is not a scheduled 2.1.2 release currently, but we have opened up
a project version in redmine to track issues for it. The issues found
and their severity will determine when and if a 2.1.2 release occurs.
When filing issues please assign them to the 2.1.2 release if you would
like to see them considered for that release.

> Hi All,
>
> A minor update to Katello 2.1 has been released.
>
> Highlighted fixes include:
>
> * el7 installation issues on slower systems
> * upgrade issues related with errata importing
> * Content View Deletion errors
>
> For a full change log see:
>
> https://github.com/Katello/katello/blob/KATELLO-2.1/CHANGELOG.md
>
> Upgrading from 2.1.0:
> ================
>
> To update to the new packages:
>
> * yum update
> * katello-service restart
I noticed a couple of changes in
"/etc/katello-installer/katello-installer.yaml.rpmnew" since 2.1.0. I
merged them. Should I run installer again?

> Thanks to all the uses and developers for filing and fixing issues and
> making 2.1.1 a possibility!
>
> Katello 2.1.2
> =========
> There is not a scheduled 2.1.2 release currently, but we have opened
> up a project version in redmine to track issues for it. The issues
> found and their severity will determine when and if a 2.1.2 release
> occurs. When filing issues please assign them to the 2.1.2 release if
> you would like to see them considered for that release.
>

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

··· On 02/19/2015 06:59 PM, Justin Sherrill wrote:
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 All,
>
> A minor update to Katello 2.1 has been released.
>
> Highlighted fixes include:
>
> * el7 installation issues on slower systems
> * upgrade issues related with errata importing
> * Content View Deletion errors
>
> For a full change log see:
>
> https://github.com/Katello/katello/blob/KATELLO-2.1/CHANGELOG.md
>
> Upgrading from 2.1.0:
> ================
>
> To update to the new packages:
>
> * yum update
> * katello-service restart
I noticed a couple of changes in
"/etc/katello-installer/katello-installer.yaml.rpmnew" since 2.1.0. I
merged them. Should I run installer again?

> Thanks to all the uses and developers for filing and fixing issues and
> making 2.1.1 a possibility!
>
> Katello 2.1.2
> =========
> There is not a scheduled 2.1.2 release currently, but we have opened
> up a project version in redmine to track issues for it. The issues
> found and their severity will determine when and if a 2.1.2 release
> occurs. When filing issues please assign them to the 2.1.2 release if
> you would like to see them considered for that release.
>

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

··· On 02/19/2015 06:59 PM, Justin Sherrill wrote:
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

> Here are my notes on my 2.0 -> 2.1.1 upgrade experience on EL7. Hopefully
>> this might be useful for somebody else.
>
>
>> 1. MongoDB PID file path problems. I had previously downgraded MongoDB
>> to work around this issue ( Bug #8478: MongoDB fails to start with a RHEL 7 system - Katello - Foreman ) so
>> when I did the pre-upgrade "yum upgrade". It updated to a version of
>> mongodb that wouldn't start. This left mongodb in a stopped state for the
>> rest of the upgrade. The fix for that was to update the pidfilepath in
>> etc/mongodb.conf - see /etc/mongodb.conf.rpmnew for the correct new path.
>> Then start mongodb before proceeding with the katello-installer --upgrade
>> step.
>
>
>> 2. Pulp index bug ( https://bugzilla.redhat.com/show_bug.cgi?id=1175616
>> ). katello-installer --upgrade ran successfully up to the db:seed step
>> which blew up. The fix for is dropping an index - see the BZ for details.
>> After you drop the index you can do # sudo -u apache pulp-manage-db to
>> complete the Pulp DB migrations that failed the first time. Then do a
>> katello-service restart.
>
>
>> 3. I re-reran katello-installer --upgrade after fixing the MongoDB index
>> to make sure everything ran without error. This was critical to getting
>> pulp back to normal.
>
>
>> 4. My yum_importer pulp proxy was wiped out during the uprade so I had to
>> redefine it. Is there an upgrade proof way to define this?
>
>
I want to say thanks to the developers and in particular jsherril and
stbenjam who helped me get through the upgrade!

>
> > Hi All,
> >
> > A minor update to Katello 2.1 has been released.
> >
> > Highlighted fixes include:
> >
> > * el7 installation issues on slower systems
> > * upgrade issues related with errata importing
> > * Content View Deletion errors
> >
> > For a full change log see:
> >
> > https://github.com/Katello/katello/blob/KATELLO-2.1/CHANGELOG.md
> >
> > Upgrading from 2.1.0:
> > ================
> >
> > To update to the new packages:
> >
> > * yum update
> > * katello-service restart
> I noticed a couple of changes in
> "/etc/katello-installer/katello-installer.yaml.rpmnew" since 2.1.0. I
> merged them. Should I run installer again?

which specific changes did you see? Its possible that the change is
simply because the installer ran before and changed config values (and
the rpm is laying down a 'default' config).

-Justin

··· On 02/20/2015 05:17 AM, Jorick Astrego wrote: > On 02/19/2015 06:59 PM, Justin Sherrill wrote:

Thanks to all the uses and developers for filing and fixing issues and
making 2.1.1 a possibility!

Katello 2.1.2

There is not a scheduled 2.1.2 release currently, but we have opened
up a project version in redmine to track issues for it. The issues
found and their severity will determine when and if a 2.1.2 release
occurs. When filing issues please assign them to the 2.1.2 release if
you would like to see them considered for that release.

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



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
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto: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 All,
>> >
>> > A minor update to Katello 2.1 has been released.
>> >
>> > Highlighted fixes include:
>> >
>> > * el7 installation issues on slower systems
>> > * upgrade issues related with errata importing
>> > * Content View Deletion errors
>> >
>> > For a full change log see:
>> >
>> > https://github.com/Katello/katello/blob/KATELLO-2.1/CHANGELOG.md
>> >
>> > Upgrading from 2.1.0:
>> > ================
>> >
>> > To update to the new packages:
>> >
>> > * yum update
>> > * katello-service restart
>> I noticed a couple of changes in
>> "/etc/katello-installer/katello-installer.yaml.rpmnew" since 2.1.0. I
>> merged them. Should I run installer again?
>
> which specific changes did you see? Its possible that the change is
> simply because the installer ran before and changed config values (and
> the rpm is laying down a 'default' config).
>
> -Justin
>

Ah dang, I overwrote it without saving the original.

When I did a diff, I noticed:

 :installer_dir: /usr/share/katello-installer

was something like /etc/katello-installer before

and

:hook_dirs: ["/usr/share/katello-installer/hooks"]

was empty in the original (:hook_dirs: [""])

Also some of the plugin mappings changed order but that doesn't bother me.

I can redeploy one next week to make sure.

>>
>>
>> > Thanks to all the uses and developers for filing and fixing issues and
>> > making 2.1.1 a possibility!
>> >
>> > Katello 2.1.2
>> > =========
>> > There is not a scheduled 2.1.2 release currently, but we have opened
>> > up a project version in redmine to track issues for it. The issues
>> > found and their severity will determine when and if a 2.1.2 release
>> > occurs. When filing issues please assign them to the 2.1.2 release if
>> > you would like to see them considered for that release.
>> >
>>
>>
>>
>
>>
>> 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
>>
>>
>> ------------------------------------------------------------------------
>>
>> –
>> 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
>> <mailto:foreman-users+unsubscribe@googlegroups.com>.
>> To post to this group, send email to foreman-users@googlegroups.com
>> <mailto: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
> <mailto:foreman-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to foreman-users@googlegroups.com
> <mailto: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.

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

··· On 02/20/2015 03:04 PM, Justin Sherrill wrote: > On 02/20/2015 05:17 AM, Jorick Astrego wrote: >> On 02/19/2015 06:59 PM, Justin Sherrill wrote:
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

Great jobs guys, there were a few changes in this release I badly needed.
Thanks!

··· On Fri, Feb 20, 2015 at 5:36 PM, Jorick Astrego wrote:

On 02/20/2015 03:04 PM, Justin Sherrill wrote:

On 02/20/2015 05:17 AM, Jorick Astrego wrote:

On 02/19/2015 06:59 PM, Justin Sherrill wrote:

Hi All,

A minor update to Katello 2.1 has been released.

Highlighted fixes include:

  • el7 installation issues on slower systems
  • upgrade issues related with errata importing
  • Content View Deletion errors

For a full change log see:

https://github.com/Katello/katello/blob/KATELLO-2.1/CHANGELOG.md

Upgrading from 2.1.0:

To update to the new packages:

  • yum update
  • katello-service restart
    I noticed a couple of changes in
    "/etc/katello-installer/katello-installer.yaml.rpmnew" since 2.1.0. I
    merged them. Should I run installer again?

which specific changes did you see? Its possible that the change is
simply because the installer ran before and changed config values (and the
rpm is laying down a ‘default’ config).

-Justin

Ah dang, I overwrote it without saving the original.

When I did a diff, I noticed:

:installer_dir: /usr/share/katello-installer

was something like /etc/katello-installer before

and

:hook_dirs: ["/usr/share/katello-installer/hooks"]

was empty in the original (:hook_dirs: [""])

Also some of the plugin mappings changed order but that doesn’t bother me.

I can redeploy one next week to make sure.

Thanks to all the uses and developers for filing and fixing issues and
making 2.1.1 a possibility!

Katello 2.1.2

There is not a scheduled 2.1.2 release currently, but we have opened
up a project version in redmine to track issues for it. The issues
found and their severity will determine when and if a 2.1.2 release
occurs. When filing issues please assign them to the 2.1.2 release if
you would like to see them considered for that release.

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


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.


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.

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


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.


Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30