[Katello 2.3] el6 client applying errata fails after trying to have el7 package applied

Support
1

When trying to apply errata to a el6 client, the task fails with the
following message:

InstallError: 1:java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el7_1.x86_64: No
package(s) available to install

The package name changes depending on the errata I'm trying to apply, but
the gist remains the same (katello agent trying to install el7 package on
el6 client)

This bug is also reported
here: https://bugzilla.redhat.com/show_bug.cgi?id=1198191

2

> When trying to apply errata to a el6 client, the task fails with the
> following message:
>
> >
> InstallError:1:java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el7_1.x86_64:Nopackage(s)available
> to install
> >
>
> The package name changes depending on the errata I'm trying to apply,
> but the gist remains the same (katello agent trying to install el7
> package on el6 client)
>
> This bug is also reported
> here: https://bugzilla.redhat.com/show_bug.cgi?id=1198191
Odd, we don't use bugzilla anymore for katello, we've moved to redmine.
Issues - Katello - Foreman

Anyways, this is a known pulp bug:

https://pulp.plan.io/issues/770

That was fixed in 2.6.1. I'll see about pulling in the newest 2.6.X
release in a day or so. If you really want to try it out ahead of time,
you can try from the upstream pulp repos here:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/7Server/x86_64/

I've also opened Bug #10673: Upgrade pulp to 2.6.2 - Packaging - Foreman to help
track the upgrade if you are interested in keeping up.

-Justin

··· On 06/01/2015 04:53 PM, Francois Herbert wrote:

–
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.

3

After updating to pulp 2.6.1 and checking the foreman ‘about’ page I see a ‘500 Internal Server error’ next to pulp_auth under Backend System Status.

The foreman log shows:

[ERROR 2015-06-03 06:39:19 pulp_rest #46571] RestClient.get "https://foreman.domain.com/pulp/api/v2/users/", "Accept"=>"/; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Authorization"=>"OAuth oauth_consumer_key="katello", oauth_nonce=\”blahblahblahblahP6CI", oauth_signature=\”blahblahblahblahhBQ%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1433270359", oauth_version="1.0"", "accept"=>"application/json", "content_type"=>"application/json", "pulp-user"=>”me-56b9dbe6"
> \n# => 500 InternalServerError | text/html 531 bytes

2015-06-03 06:39:19 [W] 500 Internal Server Error

Checking /etc/pulp/server.conf looks the same as pre-upgrade (timestamp indicates it hasn’t changed)

Rolling back the yum upgrade back to pulp-server 2.6.0 resolves this, but leaves me with my initial issue. Any ideas on how to fix the pulp_auth error?

··· On 2/06/2015, at 3:46 pm, Justin Sherrill wrote:

On 06/01/2015 04:53 PM, Francois Herbert wrote:

When trying to apply errata to a el6 client, the task fails with the following message:

InstallError: 1:java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el7_1.x86_64: No package(s) available to install

The package name changes depending on the errata I’m trying to apply, but the gist remains the same (katello agent trying to install el7 package on el6 client)

This bug is also reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1198191
Odd, we don’t use bugzilla anymore for katello, we’ve moved to redmine. Issues - Katello - Foreman

Anyways, this is a known pulp bug:

https://pulp.plan.io/issues/770

That was fixed in 2.6.1. I’ll see about pulling in the newest 2.6.X release in a day or so. If you really want to try it out ahead of time, you can try from the upstream pulp repos here:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/7Server/x86_64/

I’ve also opened Bug #10673: Upgrade pulp to 2.6.2 - Packaging - Foreman to help track the upgrade if you are interested in keeping up.

-Justin

–
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 a topic in the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Qe5mP00JCW8/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.

4

Looking in the logs, the following error appears after upgrading
pulp-server : pulp.server.webservices.application:ERROR: (64644-85952)
InitializationException: The database has not been migrated to the current
version. Run pulp-manage-db and restart the application.

So I've run 'sudo -u apache pulp-manage-db' and this has the pulp_auth
(pup-server 2.6.1) running as expected.

··· On Wed, Jun 3, 2015 at 6:53 AM, Francois Herbert wrote:

After updating to pulp 2.6.1 and checking the foreman ‘about’ page I see a
‘500 Internal Server error’ next to pulp_auth under Backend System Status.

The foreman log shows:

[ERROR 2015-06-03 06:39:19 pulp_rest #46571] RestClient.get “
https://foreman.domain.com/pulp/api/v2/users/”, “Accept”=>"/; q=0.5,
application/xml", “Accept-Encoding”=>“gzip, deflate”,
“Authorization”=>“OAuth oauth_consumer_key=“katello”,
oauth_nonce=\”blahblahblahblahP6CI”,
oauth_signature=\”blahblahblahblahhBQ%3D",
oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1433270359”,
oauth_version=“1.0"”, “accept”=>“application/json”,
“content_type”=>“application/json”, “pulp-user”=>”me-56b9dbe6"

\n# => 500 InternalServerError | text/html 531 bytes

2015-06-03 06:39:19 [W] 500 Internal Server Error

Checking /etc/pulp/server.conf looks the same as pre-upgrade (timestamp
indicates it hasn’t changed)

Rolling back the yum upgrade back to pulp-server 2.6.0 resolves this, but
leaves me with my initial issue. Any ideas on how to fix the pulp_auth
error?

On 2/06/2015, at 3:46 pm, Justin Sherrill jsherril@redhat.com wrote:

On 06/01/2015 04:53 PM, Francois Herbert wrote:

When trying to apply errata to a el6 client, the task fails with the
following message:

InstallError: 1:java-1.6.0-openjdk-1.6.0.35-1.13.7.1.el7_1.x86_64: No
package(s) available to install

The package name changes depending on the errata I’m trying to apply, but
the gist remains the same (katello agent trying to install el7 package on
el6 client)

This bug is also reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1198191

Odd, we don’t use bugzilla anymore for katello, we’ve moved to redmine.
Issues - Katello - Foreman

Anyways, this is a known pulp bug:

https://pulp.plan.io/issues/770

That was fixed in 2.6.1. I’ll see about pulling in the newest 2.6.X
release in a day or so. If you really want to try it out ahead of time,
you can try from the upstream pulp repos here:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/7Server/x86_64/

I’ve also opened Bug #10673: Upgrade pulp to 2.6.2 - Packaging - Foreman to help
track the upgrade if you are interested in keeping up.

-Justin

–
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 a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/Qe5mP00JCW8/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.