Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can't be resolved.
This (the amqp prob notably) results in not being able to do remote package
management on an EL5 client from within katello.
So I'm wondering if anybody uses EL5 clients with katello and got the
remote package management working?
I'm using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at least
5.7 before registering with the Satellite. This is done by getting the
Satellite to expose it's 5Server repo directory via http and pointing the
client at that yum repo. Once patched up to this point, we can register to
the Satellite in the normal manner and everything works from that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We take
them all the way up to the latest available packages (5.11) at the moment.
I know that older versions couldn't run katello-agent due to dependency
issues.
D
···
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
>
> Hi all,
>
> I created a bug report concerning katello (I think it's the pulp-part) and
> EL5:
>
> http://projects.theforeman.org/issues/13377
>
> Next to the doc being a bit wrong, it seems the EL5 packages are
> incorrectly signed (v4 gpg key) and there is a package dependency for
> python-gofer-amqp that can't be resolved.
> This (the amqp prob notably) results in not being able to do remote
> package management on an EL5 client from within katello.
> So I'm wondering if anybody uses EL5 clients with katello and got the
> remote package management working?
>
> Franky
>
all our test clients are centos 5.11 and subscription-manager works fine,
as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can't find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for "waiting for pulp to start the task" (well, I think
it is because of this, restarting the katello services didn't change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I'm inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn't have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
···
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We take
them all the way up to the latest available packages (5.11) at the moment.
I know that older versions couldn’t run katello-agent due to dependency
issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
all our test clients are centos 5.11 and subscription-manager works fine,
as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can't find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for "waiting for pulp to start the task" (well, I think
it is because of this, restarting the katello services didn't change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I'm inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn't have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
···
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We take
them all the way up to the latest available packages (5.11) at the moment.
I know that older versions couldn’t run katello-agent due to dependency
issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
Given the age of EL5, we don't do much testing on it and rely on the small
crop of users that do use it to tell us when something broke. All that is
to say, we'll look into it. Is this with Katello 2.4?
···
On Fri, Jan 29, 2016 at 4:58 AM, Franky Van Liedekerke < franky.van.liedekerke@gmail.com> wrote:
Hi,
all our test clients are centos 5.11 and subscription-manager works fine,
as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can’t find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for “waiting for pulp to start the task” (well, I think
it is because of this, restarting the katello services didn’t change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I’m inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn’t have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes duncan@innes.net wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We take
them all the way up to the latest available packages (5.11) at the moment.
I know that older versions couldn’t run katello-agent due to dependency
issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
yes, this is with katello 2.4. But the problem is not new, it's there for
over a year it seems.
If you look at the koji build: http://koji.katello.org/koji/rpminfo?rpmID=110224
It seems that somebody is/was able to build python-gofer-amqp on el5 with
the python-amqp dependency resolved, although the buildroot mentioned in
that link nowhere mentions python-amqp.
The python-amqp dependency problem exists also in the 2.2 agent, with the
difference being that there the rpm's are correctly signed …
Franky
···
On Sat, Jan 30, 2016 at 4:00 PM, Eric D Helms wrote:
Howdy,
Given the age of EL5, we don’t do much testing on it and rely on the small
crop of users that do use it to tell us when something broke. All that is
to say, we’ll look into it. Is this with Katello 2.4?
all our test clients are centos 5.11 and subscription-manager works fine,
as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can’t find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for “waiting for pulp to start the task” (well, I think
it is because of this, restarting the katello services didn’t change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I’m inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn’t have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes duncan@innes.net wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We
take them all the way up to the latest available packages (5.11) at the
moment. I know that older versions couldn’t run katello-agent due to
dependency issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
(I replied with a wrong address, apparently it didn't got through so here
goes again):
Hi,
yes, this is with katello 2.4. But the problem is not new, it's there for
over a year it seems.
If you look at the koji build: http://koji.katello.org/koji/rpminfo?rpmID=110224
It seems that somebody is/was able to build python-gofer-amqp on el5 with
the python-amqp dependency resolved, although the buildroot mentioned in
that link nowhere mentions python-amqp.
The python-amqp dependency problem exists also in the 2.2 agent, with the
difference being that there the rpm's are correctly signed …
Franky
···
On Sat, Jan 30, 2016 at 4:00 PM, Eric D Helms wrote:
Howdy,
Given the age of EL5, we don’t do much testing on it and rely on the small
crop of users that do use it to tell us when something broke. All that is
to say, we’ll look into it. Is this with Katello 2.4?
all our test clients are centos 5.11 and subscription-manager works fine,
as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can’t find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for “waiting for pulp to start the task” (well, I think
it is because of this, restarting the katello services didn’t change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I’m inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn’t have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes duncan@innes.net wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We
take them all the way up to the latest available packages (5.11) at the
moment. I know that older versions couldn’t run katello-agent due to
dependency issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
···
On Sun, Jan 31, 2016 at 2:16 PM, Franky Van Liedekerke wrote:
Hi,
yes, this is with katello 2.4. But the problem is not new, it’s there for
over a year it seems.
If you look at the koji build: http://koji.katello.org/koji/rpminfo?rpmID=110224
It seems that somebody is/was able to build python-gofer-amqp on el5 with
the python-amqp dependency resolved, although the buildroot mentioned in
that link nowhere mentions python-amqp.
The python-amqp dependency problem exists also in the 2.2 agent, with the
difference being that there the rpm’s are correctly signed …
Given the age of EL5, we don’t do much testing on it and rely on the
small crop of users that do use it to tell us when something broke. All
that is to say, we’ll look into it. Is this with Katello 2.4?
all our test clients are centos 5.11 and subscription-manager works
fine, as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can’t find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for “waiting for pulp to start the task” (well, I think
it is because of this, restarting the katello services didn’t change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I’m inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn’t have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes duncan@innes.net wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We
take them all the way up to the latest available packages (5.11) at the
moment. I know that older versions couldn’t run katello-agent due to
dependency issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
Apologies, we've been too heads down lately. We'll take a look at this
ticket today.
···
On Tue, Feb 9, 2016 at 7:12 AM, Franky Van Liedekerke < franky.van.liedekerke@gmail.com> wrote:
(I replied with a wrong address, apparently it didn’t got through so here
goes again):
Hi,
yes, this is with katello 2.4. But the problem is not new, it’s there for
over a year it seems.
If you look at the koji build: http://koji.katello.org/koji/rpminfo?rpmID=110224
It seems that somebody is/was able to build python-gofer-amqp on el5 with
the python-amqp dependency resolved, although the buildroot mentioned in
that link nowhere mentions python-amqp.
The python-amqp dependency problem exists also in the 2.2 agent, with the
difference being that there the rpm’s are correctly signed …
Given the age of EL5, we don’t do much testing on it and rely on the
small crop of users that do use it to tell us when something broke. All
that is to say, we’ll look into it. Is this with Katello 2.4?
all our test clients are centos 5.11 and subscription-manager works
fine, as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can’t find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for “waiting for pulp to start the task” (well, I think
it is because of this, restarting the katello services didn’t change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I’m inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn’t have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes duncan@innes.net wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We
take them all the way up to the latest available packages (5.11) at the
moment. I know that older versions couldn’t run katello-agent due to
dependency issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the pulp-part)
and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
(I replied with a wrong address, apparently it didn’t got through so here
goes again):
Hi,
yes, this is with katello 2.4. But the problem is not new, it’s there for
over a year it seems.
If you look at the koji build: http://koji.katello.org/koji/rpminfo?rpmID=110224
It seems that somebody is/was able to build python-gofer-amqp on el5 with
the python-amqp dependency resolved, although the buildroot mentioned in
that link nowhere mentions python-amqp.
The python-amqp dependency problem exists also in the 2.2 agent, with the
difference being that there the rpm’s are correctly signed …
Given the age of EL5, we don’t do much testing on it and rely on the
small crop of users that do use it to tell us when something broke. All
that is to say, we’ll look into it. Is this with Katello 2.4?
all our test clients are centos 5.11 and subscription-manager works
fine, as does the goferd agent, but just not the goferd-amqp plugin, since
python-amqp is a dependency for gofer-plugin-amqp and I can’t find that rpm
nowhere. Because of this every package install/remove task I start in
katello just hangs for “waiting for pulp to start the task” (well, I think
it is because of this, restarting the katello services didn’t change
anything). EL6 clients work just fine though, since there the rpm
python-amqp exist, so I’m inclined to think the reason is the missing
python-amqp rpm (and the fact that the packages are in fact signed wrong).
Maybe the satellite-version for gofer-plugin-amqp doesn’t have that
dependency?
And I assume your packages are signed in a more correct way too?
Franky
On Fri, Jan 29, 2016 at 10:38 AM, Duncan Innes duncan@innes.net >>>> wrote:
I’m using Satellite 6.1.6 with RHEL 5 clients if that helps?
In our case, the clients are RHEL 5.5, so need to be patched up to at
least 5.7 before registering with the Satellite. This is done by getting
the Satellite to expose it’s 5Server repo directory via http and pointing
the client at that yum repo. Once patched up to this point, we can
register to the Satellite in the normal manner and everything works from
that point.
The key for us was to get the RHEL 5 client patched up from 5.5. We
take them all the way up to the latest available packages (5.11) at the
moment. I know that older versions couldn’t run katello-agent due to
dependency issues.
D
On Friday, 29 January 2016 09:07:16 UTC, Franky Van Liedekerke wrote:
Hi all,
I created a bug report concerning katello (I think it’s the
pulp-part) and EL5:
Next to the doc being a bit wrong, it seems the EL5 packages are
incorrectly signed (v4 gpg key) and there is a package dependency for
python-gofer-amqp that can’t be resolved.
This (the amqp prob notably) results in not being able to do remote
package management on an EL5 client from within katello.
So I’m wondering if anybody uses EL5 clients with katello and got the
remote package management working?
