error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
BAD, key ID d5a88496
Installing : katello-ca-consumer-myhostname.mydomain
Non-fatal POSTIN scriptlet failure in rpm package
katello-ca-myhostname.mydomain-1.0-1.noarch
error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
scriptlet failed, exit status 1
Being non-fatal, it does install, but it's not as satisfying as I'd like. Using
my best investigative skills (lots of google searches), the common theme is
selinux, but I have this in permissive mode (well I do now).
Looking at the rpm, the postinstall section should just exit when it
doesn't find rhsm.conf (this is a CentOS 5 host):
RHSM_V="rpm -q --queryformat='%{VERSION}' subscription-manager 2> /dev/null | tr . ' '"
if test $? != 0 ; then
RHSM_V="0 0 0"
fi
declare -a RHSM_VERSION=($RHSM_V)
exit on non-RHEL systems or when rhsm.conf is not found
test -f $CFG || exit
Anyone seen this before? The CentOS 6 test clients didn't have a problem.
···
On 05/21/2015 10:21 AM, JC wrote:
> error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
> BAD, key ID d5a88496
> Installing : katello-ca-consumer-myhostname.mydomain
> Non-fatal POSTIN scriptlet failure in rpm package
> katello-ca-myhostname.mydomain-1.0-1.noarch
> error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
> scriptlet failed, exit status 1
>
> Being non-fatal, it does install, but it's not as satisfying as I'd
> like. Using my best investigative skills (lots of google searches), the
> common theme is selinux, but I have this in permissive mode (well I do now).
>
> Looking at the rpm, the postinstallsection should just exit when it
> doesn't find rhsm.conf(this is a CentOS 5 host):
>
> postinstall scriptlet (using /bin/sh):
> #!/bin/bash
> < snip >
> KATELLO_SERVER=myhostname.mydomain
> PORT=443
> BASEURL=https://$KATELLO_SERVER/pulp/repos
>
> PREFIX=/rhsm
> *CFG=/etc/rhsm/rhsm.conf*
> CFG_BACKUP=$CFG.kat-backup
>
> # Get version of RHSM
> RHSM_V="`rpm -q --queryformat='%{VERSION}' subscription-manager 2>
> /dev/null | tr . ' '`"
> if test $? != 0 ; then
> RHSM_V="0 0 0"
> fi
> declare -a RHSM_VERSION=($RHSM_V)
>
> # exit on non-RHEL systems or when rhsm.conf is not found
> *test -f $CFG || exit*
> *
> *
> Anyone seen this before? The CentOS 6 test clients didn't have a problem.
>
> --
> 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.
error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
BAD, key ID d5a88496
Installing : katello-ca-consumer-myhostname.mydomain
Non-fatal POSTIN scriptlet failure in rpm package
katello-ca-myhostname.mydomain-1.0-1.noarch
error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
scriptlet failed, exit status 1
Being non-fatal, it does install, but it’s not as satisfying as I’d
like. Using my best investigative skills (lots of google searches), the
common theme is selinux, but I have this in permissive mode (well I do
now).
Looking at the rpm, the postinstallsection should just exit when it
doesn’t find rhsm.conf(this is a CentOS 5 host):
RHSM_V="rpm -q --queryformat='%{VERSION}' subscription-manager 2> /dev/null | tr . ' '"
if test $? != 0 ; then
RHSM_V="0 0 0"
fi
declare -a RHSM_VERSION=($RHSM_V)
exit on non-RHEL systems or when rhsm.conf is not found
test -f $CFG || exit
*
*
Anyone seen this before? The CentOS 6 test clients didn’t have a problem.
error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
BAD, key ID d5a88496
Installing : katello-ca-consumer-myhostname.mydomain
Non-fatal POSTIN scriptlet failure in rpm package
katello-ca-myhostname.mydomain-1.0-1.noarch
error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
scriptlet failed, exit status 1
Being non-fatal, it does install, but it’s not as satisfying as I’d
like. Using my best investigative skills (lots of google searches), the
common theme is selinux, but I have this in permissive mode (well I do
now).
Looking at the rpm, the postinstallsection should just exit when it
doesn’t find rhsm.conf(this is a CentOS 5 host):
RHSM_V="rpm -q --queryformat='%{VERSION}' subscription-manager 2> /dev/null | tr . ' '"
if test $? != 0 ; then
RHSM_V="0 0 0"
fi
declare -a RHSM_VERSION=($RHSM_V)
exit on non-RHEL systems or when rhsm.conf is not found
test -f $CFG || exit
*
*
Anyone seen this before? The CentOS 6 test clients didn’t have a
problem.
This sounds familiar to another issue we hit with EL5 for another package.
Everything completes successfully though? Mind filing an issue with this
information ?
···
On Thu, May 21, 2015 at 10:57 AM, Jamie Caldwell < mr.jamie.caldwell@gmail.com> wrote:
error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
BAD, key ID d5a88496
Installing : katello-ca-consumer-myhostname.mydomain
Non-fatal POSTIN scriptlet failure in rpm package
katello-ca-myhostname.mydomain-1.0-1.noarch
error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
scriptlet failed, exit status 1
Being non-fatal, it does install, but it’s not as satisfying as I’d
like. Using my best investigative skills (lots of google searches), the
common theme is selinux, but I have this in permissive mode (well I do
now).
Looking at the rpm, the postinstallsection should just exit when it
doesn’t find rhsm.conf(this is a CentOS 5 host):
RHSM_V="rpm -q --queryformat='%{VERSION}' subscription-manager 2> /dev/null | tr . ' '"
if test $? != 0 ; then
RHSM_V="0 0 0"
fi
declare -a RHSM_VERSION=($RHSM_V)
exit on non-RHEL systems or when rhsm.conf is not found
test -f $CFG || exit
*
*
Anyone seen this before? The CentOS 6 test clients didn’t have a
problem.
Before I do, so as to check I'm not putting in (extra) duff info, I believe
the issue may be with the subscription-manager package, rather than my
server cert rpm. Despite yum telling me subscription-manager has been
successfully installed (when I install the cert), it isn't. yum also tells
me subscription-manager was installed successfully, when tried on its own,
but again it isn't.
Following something I read on an old blog, which may have since been
addressed, I'm wondering whether:
rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
subscription-manager-1.11.3-11.el5.x86_64.rpm:
Header V4 RSA/SHA1 signature: BAD, key ID d5a88496
Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
V4 RSA/SHA1 signature: BAD, key ID d5a88496
MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
V4 should be V3? I'm using --nogpgcheck, but I wondered whether this was
still a factor?
This sounds familiar to another issue we hit with EL5 for another package.
Everything completes successfully though? Mind filing an issue with this
information ?
error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
signature:
BAD, key ID d5a88496
Installing : katello-ca-consumer-myhostname.mydomain
Non-fatal POSTIN scriptlet failure in rpm package
katello-ca-myhostname.mydomain-1.0-1.noarch
error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
scriptlet failed, exit status 1
Being non-fatal, it does install, but it’s not as satisfying as I’d
like. Using my best investigative skills (lots of google searches), the
common theme is selinux, but I have this in permissive mode (well I do
now).
Looking at the rpm, the postinstallsection should just exit when it
doesn’t find rhsm.conf(this is a CentOS 5 host):
RHSM_V="rpm -q --queryformat='%{VERSION}' subscription-manager 2> /dev/null | tr . ' '"
if test $? != 0 ; then
RHSM_V="0 0 0"
fi
declare -a RHSM_VERSION=($RHSM_V)
exit on non-RHEL systems or when rhsm.conf is not found
test -f $CFG || exit
*
*
Anyone seen this before? The CentOS 6 test clients didn’t have a
problem.
···
On Fri, May 22, 2015 at 5:38 AM, Jamie Caldwell wrote:
Yes, will do Eric, not a problem.
Before I do, so as to check I’m not putting in (extra) duff info, I
believe the issue may be with the subscription-manager package, rather than
my server cert rpm. Despite yum telling me subscription-manager has been
successfully installed (when I install the cert), it isn’t. yum also tells
me subscription-manager was installed successfully, when tried on its own,
but again it isn’t.
Following something I read on an old blog, which may have since been
addressed, I’m wondering whether:
rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
subscription-manager-1.11.3-11.el5.x86_64.rpm:
Header V4 RSA/SHA1 signature: BAD, key ID d5a88496
Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
V4 RSA/SHA1 signature: BAD, key ID d5a88496
MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
V4 should be V3? I’m using --nogpgcheck, but I wondered whether this was
still a factor?
# yum install --nogpgcheck subscription-manager
Installing:
subscription-manager x86_64
1.11.3-11.el5 katello-agent 1.1 M
Transaction Test Succeeded
Running Transaction
*error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
BAD, key ID d5a88496*
Installed:
subscription-manager.x86_64 0:1.11.3-11.el5*
Complete! # rpm -qa --last | head -1
python-uuid-1.30-3.el5 Fri 22 May 2015 09:56:48 BST
This sounds familiar to another issue we hit with EL5 for another
package. Everything completes successfully though? Mind filing an issue
with this information ?
error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
signature:
BAD, key ID d5a88496
Installing : katello-ca-consumer-myhostname.mydomain
Non-fatal POSTIN scriptlet failure in rpm package
katello-ca-myhostname.mydomain-1.0-1.noarch
error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
scriptlet failed, exit status 1
Being non-fatal, it does install, but it’s not as satisfying as I’d
like. Using my best investigative skills (lots of google searches),
the
common theme is selinux, but I have this in permissive mode (well I
do now).
Looking at the rpm, the postinstallsection should just exit when it
doesn’t find rhsm.conf(this is a CentOS 5 host):
RHSM_V="rpm -q --queryformat='%{VERSION}' subscription-manager 2> /dev/null | tr . ' '"
if test $? != 0 ; then
RHSM_V="0 0 0"
fi
declare -a RHSM_VERSION=($RHSM_V)
exit on non-RHEL systems or when rhsm.conf is not found
test -f $CFG || exit
*
*
Anyone seen this before? The CentOS 6 test clients didn’t have a
problem.
···
On Wednesday, 10 June 2015 18:44:46 UTC+1, Eric Helms wrote:
>
> We found that the EL5 client repositories for 2.2 were signed incorrectly
> and have updated and tested them. I have set
> http://projects.theforeman.org/issues/10608 to resolved. Please let us
> know if you hit further issues.
>
>
> Eric
>
> On Fri, May 22, 2015 at 5:38 AM, Jamie Caldwell > wrote:
>
>> Yes, will do Eric, not a problem.
>>
>> Before I do, so as to check I'm not putting in (extra) duff info, I
>> believe the issue may be with the subscription-manager package, rather than
>> my server cert rpm. Despite yum telling me subscription-manager has been
>> successfully installed (when I install the cert), it isn't. yum also tells
>> me subscription-manager was installed successfully, when tried on its own,
>> but again it isn't.
>>
>> Following something I read on an old blog, which may have since been
>> addressed, I'm wondering whether:
>>
>> rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
>> subscription-manager-1.11.3-11.el5.x86_64.rpm:
>> Header *V4* RSA/SHA1 signature: BAD, key ID d5a88496
>> Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
>> V4 RSA/SHA1 signature: BAD, key ID d5a88496
>> MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
>>
>> V4 should be V3? I'm using --nogpgcheck, but I wondered whether this was
>> still a factor?
>>
>> *# yum install --nogpgcheck subscription-manager*
>>
>> Installing:
>> subscription-manager x86_64
>> 1.11.3-11.el5 katello-agent 1.1 M
>>
>>
>> Transaction Test Succeeded
>> Running Transaction
>> *error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
>> BAD, key ID d5a88496*
>>
>> *Installed:*
>> * subscription-manager.x86_64 0:1.11.3-11.el5*
>>
>> Complete!
>> *# rpm -qa --last | head -1*
>> python-uuid-1.30-3.el5 Fri 22 May 2015 09:56:48 BST
>>
>> And, could the same magic be applied to
>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/*6*/x86_64/,
>> as I'm similarly relying on
>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/x86_64/
>> for subscription-manager and python-rhsm. Much appreciated.
>>
>> On 21 May 2015 at 16:08, Eric D Helms <ericd...@gmail.com > >> wrote:
>>
>>> This sounds familiar to another issue we hit with EL5 for another
>>> package. Everything completes successfully though? Mind filing an issue
>>> with this information ?
>>>
>>> On Thu, May 21, 2015 at 10:57 AM, Jamie Caldwell >> > wrote:
>>>
>>>> Yes, this was installing
>>>> http://katello/pub/katello-ca-consumer-latest.noarch.rpm (having first
>>>> collected it with wget).
>>>>
>>>> On 21 May 2015 at 15:49, Eric D Helms <ericd...@gmail.com >>>> > wrote:
>>>>
>>>>> I don't think its the same issue. JC -- you are seeing this issue on
>>>>> EL5 clients after trying to install the bootstrap RPM?
>>>>>
>>>>> On Thu, May 21, 2015 at 10:35 AM, Bryan Kearney >>>> > wrote:
>>>>>
>>>>>> This was fixed downstream, can someone pull the newwer package in
>>>>>> upstream?
>>>>>>
>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1203580
>>>>>>
>>>>>> -- bk
>>>>>>
>>>>>>
>>>>>> On 05/21/2015 10:21 AM, JC wrote:
>>>>>>
>>>>>>> error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>>>>>> signature:
>>>>>>> BAD, key ID d5a88496
>>>>>>> Installing : katello-ca-consumer-myhostname.mydomain
>>>>>>> Non-fatal POSTIN scriptlet failure in rpm package
>>>>>>> katello-ca-myhostname.mydomain-1.0-1.noarch
>>>>>>> error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
>>>>>>> scriptlet failed, exit status 1
>>>>>>>
>>>>>>> Being non-fatal, it does install, but it's not as satisfying as I'd
>>>>>>> like. Using my best investigative skills (lots of google searches),
>>>>>>> the
>>>>>>> common theme is selinux, but I have this in permissive mode (well I
>>>>>>> do now).
>>>>>>>
>>>>>>> Looking at the rpm, the postinstallsection should just exit when it
>>>>>>> doesn't find rhsm.conf(this is a CentOS 5 host):
>>>>>>>
>>>>>>> postinstall scriptlet (using /bin/sh):
>>>>>>> #!/bin/bash
>>>>>>> < snip >
>>>>>>> KATELLO_SERVER=myhostname.mydomain
>>>>>>> PORT=443
>>>>>>> BASEURL=https://$KATELLO_SERVER/pulp/repos
>>>>>>>
>>>>>>> PREFIX=/rhsm
>>>>>>> *CFG=/etc/rhsm/rhsm.conf*
>>>>>>> CFG_BACKUP=$CFG.kat-backup
>>>>>>>
>>>>>>> # Get version of RHSM
>>>>>>> RHSM_V="`rpm -q --queryformat='%{VERSION}' subscription-manager 2>
>>>>>>> /dev/null | tr . ' '`"
>>>>>>> if test $? != 0 ; then
>>>>>>> RHSM_V="0 0 0"
>>>>>>> fi
>>>>>>> declare -a RHSM_VERSION=($RHSM_V)
>>>>>>>
>>>>>>> # exit on non-RHEL systems or when rhsm.conf is not found
>>>>>>> *test -f $CFG || exit*
>>>>>>> *
>>>>>>> *
>>>>>>> Anyone seen this before? The CentOS 6 test clients didn't have a
>>>>>>> problem.
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>>> <mailto:foreman-users+unsubscribe@googlegroups.com >.
>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>>
>>>>>>> <mailto:forema...@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-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.
>>>>>>
>>>>>
>>>>> --
>>>>> 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/jZrMa8c-X1c/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, 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.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jamie.
>>>>
>>>> --
>>>> 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.
>>>>
>>>
>>> --
>>> 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/jZrMa8c-X1c/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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.
>>>
>>
>>
>>
>> --
>> Jamie.
>>
>> --
>> 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.
>>
>
>
I suppose I should've actually responded to your post as opposed to
Nathan's, but in summary, it appears the issues originally outlined here
for Katello 2.2 EL5 client repositories are equally applicable to the
Katello 2.4 ones just as well. In the event that you ultimately wind up
being the assignee, self-appointed or otherwise, thanks in advance for your
assistance and efforts!
···
On Wednesday, June 10, 2015 at 12:44:46 PM UTC-5, Eric Helms wrote:
>
> We found that the EL5 client repositories for 2.2 were signed incorrectly
> and have updated and tested them. I have set
> http://projects.theforeman.org/issues/10608 to resolved. Please let us
> know if you hit further issues.
>
>
> Eric
>
> On Fri, May 22, 2015 at 5:38 AM, Jamie Caldwell > wrote:
>
>> Yes, will do Eric, not a problem.
>>
>> Before I do, so as to check I'm not putting in (extra) duff info, I
>> believe the issue may be with the subscription-manager package, rather than
>> my server cert rpm. Despite yum telling me subscription-manager has been
>> successfully installed (when I install the cert), it isn't. yum also tells
>> me subscription-manager was installed successfully, when tried on its own,
>> but again it isn't.
>>
>> Following something I read on an old blog, which may have since been
>> addressed, I'm wondering whether:
>>
>> rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
>> subscription-manager-1.11.3-11.el5.x86_64.rpm:
>> Header *V4* RSA/SHA1 signature: BAD, key ID d5a88496
>> Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
>> V4 RSA/SHA1 signature: BAD, key ID d5a88496
>> MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
>>
>> V4 should be V3? I'm using --nogpgcheck, but I wondered whether this was
>> still a factor?
>>
>> *# yum install --nogpgcheck subscription-manager*
>>
>> Installing:
>> subscription-manager x86_64
>> 1.11.3-11.el5 katello-agent 1.1 M
>>
>>
>> Transaction Test Succeeded
>> Running Transaction
>> *error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1 signature:
>> BAD, key ID d5a88496*
>>
>> *Installed:*
>> * subscription-manager.x86_64 0:1.11.3-11.el5*
>>
>> Complete!
>> *# rpm -qa --last | head -1*
>> python-uuid-1.30-3.el5 Fri 22 May 2015 09:56:48 BST
>>
>> And, could the same magic be applied to
>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/*6*/x86_64/,
>> as I'm similarly relying on
>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/x86_64/
>> for subscription-manager and python-rhsm. Much appreciated.
>>
>> On 21 May 2015 at 16:08, Eric D Helms <ericd...@gmail.com > >> wrote:
>>
>>> This sounds familiar to another issue we hit with EL5 for another
>>> package. Everything completes successfully though? Mind filing an issue
>>> with this information ?
>>>
>>> On Thu, May 21, 2015 at 10:57 AM, Jamie Caldwell >> > wrote:
>>>
>>>> Yes, this was installing
>>>> http://katello/pub/katello-ca-consumer-latest.noarch.rpm (having first
>>>> collected it with wget).
>>>>
>>>> On 21 May 2015 at 15:49, Eric D Helms <ericd...@gmail.com >>>> > wrote:
>>>>
>>>>> I don't think its the same issue. JC -- you are seeing this issue on
>>>>> EL5 clients after trying to install the bootstrap RPM?
>>>>>
>>>>> On Thu, May 21, 2015 at 10:35 AM, Bryan Kearney >>>> > wrote:
>>>>>
>>>>>> This was fixed downstream, can someone pull the newwer package in
>>>>>> upstream?
>>>>>>
>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1203580
>>>>>>
>>>>>> -- bk
>>>>>>
>>>>>>
>>>>>> On 05/21/2015 10:21 AM, JC wrote:
>>>>>>
>>>>>>> error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>>>>>> signature:
>>>>>>> BAD, key ID d5a88496
>>>>>>> Installing : katello-ca-consumer-myhostname.mydomain
>>>>>>> Non-fatal POSTIN scriptlet failure in rpm package
>>>>>>> katello-ca-myhostname.mydomain-1.0-1.noarch
>>>>>>> error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
>>>>>>> scriptlet failed, exit status 1
>>>>>>>
>>>>>>> Being non-fatal, it does install, but it's not as satisfying as I'd
>>>>>>> like. Using my best investigative skills (lots of google searches),
>>>>>>> the
>>>>>>> common theme is selinux, but I have this in permissive mode (well I
>>>>>>> do now).
>>>>>>>
>>>>>>> Looking at the rpm, the postinstallsection should just exit when it
>>>>>>> doesn't find rhsm.conf(this is a CentOS 5 host):
>>>>>>>
>>>>>>> postinstall scriptlet (using /bin/sh):
>>>>>>> #!/bin/bash
>>>>>>> < snip >
>>>>>>> KATELLO_SERVER=myhostname.mydomain
>>>>>>> PORT=443
>>>>>>> BASEURL=https://$KATELLO_SERVER/pulp/repos
>>>>>>>
>>>>>>> PREFIX=/rhsm
>>>>>>> *CFG=/etc/rhsm/rhsm.conf*
>>>>>>> CFG_BACKUP=$CFG.kat-backup
>>>>>>>
>>>>>>> # Get version of RHSM
>>>>>>> RHSM_V="`rpm -q --queryformat='%{VERSION}' subscription-manager 2>
>>>>>>> /dev/null | tr . ' '`"
>>>>>>> if test $? != 0 ; then
>>>>>>> RHSM_V="0 0 0"
>>>>>>> fi
>>>>>>> declare -a RHSM_VERSION=($RHSM_V)
>>>>>>>
>>>>>>> # exit on non-RHEL systems or when rhsm.conf is not found
>>>>>>> *test -f $CFG || exit*
>>>>>>> *
>>>>>>> *
>>>>>>> Anyone seen this before? The CentOS 6 test clients didn't have a
>>>>>>> problem.
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>>> <mailto:foreman-users+unsubscribe@googlegroups.com >.
>>>>>>> To post to this group, send email to forema...@googlegroups.com
>>>>>>>
>>>>>>> <mailto:forema...@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-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.
>>>>>>
>>>>>
>>>>> --
>>>>> 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/jZrMa8c-X1c/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, 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.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jamie.
>>>>
>>>> --
>>>> 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.
>>>>
>>>
>>> --
>>> 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/jZrMa8c-X1c/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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.
>>>
>>
>>
>>
>> --
>> Jamie.
>>
>> --
>> 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.
>>
>
>
Hmmm that will teach me, I should have actually tried to use it before
posting.
Traceback (most recent call last):
File "/usr/sbin/subscription-manager", line 58, in ?
from subscription_manager.injectioninit import init_dep_injection
File "/usr/share/rhsm/subscription_manager/injectioninit.py", line 17, in
?
from subscription_manager.cache import ProductStatusCache,
EntitlementStatusCache,
File "/usr/share/rhsm/subscription_manager/cache.py", line 32, in ?
from subscription_manager.certlib import ConsumerIdentity, DataLib
File "/usr/share/rhsm/subscription_manager/certlib.py", line 28, in ?
from subscription_manager import rhelentbranding
File "/usr/share/rhsm/subscription_manager/rhelentbranding.py", line 22,
in ?
from subscription_manager import entbranding
File "/usr/share/rhsm/subscription_manager/entbranding.py", line 173
with open(self.path, 'w') as brand_file:
^
SyntaxError: invalid syntax
OK, the older version it is…
···
On Thursday, 19 November 2015 11:55:46 UTC, JC wrote:
>
> Folks,
>
> subscription-manager in
> https://fedorapeople.org/groups/katello/releases/yum/2.4/client/RHEL/5/x86_64/
>
> has the same problem - V4 rather than V3.
>
> The newer version in
> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-5/x86_64/
> is fine, for those looking for a workaround.
>
> On Wednesday, 10 June 2015 18:44:46 UTC+1, Eric Helms wrote:
>>
>> We found that the EL5 client repositories for 2.2 were signed incorrectly
>> and have updated and tested them. I have set
>> http://projects.theforeman.org/issues/10608 to resolved. Please let us
>> know if you hit further issues.
>>
>>
>> Eric
>>
>> On Fri, May 22, 2015 at 5:38 AM, Jamie Caldwell >> wrote:
>>
>>> Yes, will do Eric, not a problem.
>>>
>>> Before I do, so as to check I'm not putting in (extra) duff info, I
>>> believe the issue may be with the subscription-manager package, rather than
>>> my server cert rpm. Despite yum telling me subscription-manager has been
>>> successfully installed (when I install the cert), it isn't. yum also tells
>>> me subscription-manager was installed successfully, when tried on its own,
>>> but again it isn't.
>>>
>>> Following something I read on an old blog, which may have since been
>>> addressed, I'm wondering whether:
>>>
>>> rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
>>> subscription-manager-1.11.3-11.el5.x86_64.rpm:
>>> Header *V4* RSA/SHA1 signature: BAD, key ID d5a88496
>>> Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
>>> V4 RSA/SHA1 signature: BAD, key ID d5a88496
>>> MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
>>>
>>> V4 should be V3? I'm using --nogpgcheck, but I wondered whether this
>>> was still a factor?
>>>
>>> *# yum install --nogpgcheck subscription-manager*
>>>
>>> Installing:
>>> subscription-manager x86_64
>>> 1.11.3-11.el5 katello-agent 1.1 M
>>>
>>>
>>> Transaction Test Succeeded
>>> Running Transaction
>>> *error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>> signature: BAD, key ID d5a88496*
>>>
>>> *Installed:*
>>> * subscription-manager.x86_64 0:1.11.3-11.el5*
>>>
>>> Complete!
>>> *# rpm -qa --last | head -1*
>>> python-uuid-1.30-3.el5 Fri 22 May 2015 09:56:48
>>> BST
>>>
>>> And, could the same magic be applied to
>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/*6*/x86_64/,
>>> as I'm similarly relying on
>>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/x86_64/
>>> for subscription-manager and python-rhsm. Much appreciated.
>>>
>>> On 21 May 2015 at 16:08, Eric D Helms wrote:
>>>
>>>> This sounds familiar to another issue we hit with EL5 for another
>>>> package. Everything completes successfully though? Mind filing an issue
>>>> with this information ?
>>>>
>>>> On Thu, May 21, 2015 at 10:57 AM, Jamie Caldwell >>> > wrote:
>>>>
>>>>> Yes, this was installing
>>>>> http://katello/pub/katello-ca-consumer-latest.noarch.rpm (having
>>>>> first collected it with wget).
>>>>>
>>>>> On 21 May 2015 at 15:49, Eric D Helms wrote:
>>>>>
>>>>>> I don't think its the same issue. JC -- you are seeing this issue on
>>>>>> EL5 clients after trying to install the bootstrap RPM?
>>>>>>
>>>>>> On Thu, May 21, 2015 at 10:35 AM, Bryan Kearney >>>>>> wrote:
>>>>>>
>>>>>>> This was fixed downstream, can someone pull the newwer package in
>>>>>>> upstream?
>>>>>>>
>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1203580
>>>>>>>
>>>>>>> -- bk
>>>>>>>
>>>>>>>
>>>>>>> On 05/21/2015 10:21 AM, JC wrote:
>>>>>>>
>>>>>>>> error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>>>>>>> signature:
>>>>>>>> BAD, key ID d5a88496
>>>>>>>> Installing : katello-ca-consumer-myhostname.mydomain
>>>>>>>> Non-fatal POSTIN scriptlet failure in rpm package
>>>>>>>> katello-ca-myhostname.mydomain-1.0-1.noarch
>>>>>>>> error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
>>>>>>>> scriptlet failed, exit status 1
>>>>>>>>
>>>>>>>> Being non-fatal, it does install, but it's not as satisfying as I'd
>>>>>>>> like. Using my best investigative skills (lots of google searches),
>>>>>>>> the
>>>>>>>> common theme is selinux, but I have this in permissive mode (well I
>>>>>>>> do now).
>>>>>>>>
>>>>>>>> Looking at the rpm, the postinstallsection should just exit when it
>>>>>>>> doesn't find rhsm.conf(this is a CentOS 5 host):
>>>>>>>>
>>>>>>>> postinstall scriptlet (using /bin/sh):
>>>>>>>> #!/bin/bash
>>>>>>>> < snip >
>>>>>>>> KATELLO_SERVER=myhostname.mydomain
>>>>>>>> PORT=443
>>>>>>>> BASEURL=https://$KATELLO_SERVER/pulp/repos
>>>>>>>>
>>>>>>>> PREFIX=/rhsm
>>>>>>>> *CFG=/etc/rhsm/rhsm.conf*
>>>>>>>> CFG_BACKUP=$CFG.kat-backup
>>>>>>>>
>>>>>>>> # Get version of RHSM
>>>>>>>> RHSM_V="`rpm -q --queryformat='%{VERSION}' subscription-manager 2>
>>>>>>>> /dev/null | tr . ' '`"
>>>>>>>> if test $? != 0 ; then
>>>>>>>> RHSM_V="0 0 0"
>>>>>>>> fi
>>>>>>>> declare -a RHSM_VERSION=($RHSM_V)
>>>>>>>>
>>>>>>>> # exit on non-RHEL systems or when rhsm.conf is not found
>>>>>>>> *test -f $CFG || exit*
>>>>>>>> *
>>>>>>>> *
>>>>>>>> Anyone seen this before? The CentOS 6 test clients didn't have a
>>>>>>>> problem.
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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.
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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.
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/jZrMa8c-X1c/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, 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.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jamie.
>>>>>
>>>>> --
>>>>> 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.
>>>>>
>>>>
>>>> --
>>>> 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/jZrMa8c-X1c/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, 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.
>>>>
>>>
>>>
>>>
>>> --
>>> Jamie.
>>>
>>> --
>>> 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.
>>>
>>
>>
So I just tried this today and the 2.4 repo still has the same problem. Is
that ever going to get fixed?
···
On Thursday, November 19, 2015 at 3:55:46 AM UTC-8, JC wrote:
>
> Folks,
>
> subscription-manager in
> https://fedorapeople.org/groups/katello/releases/yum/2.4/client/RHEL/5/x86_64/
> has the same problem - V4 rather than V3.
>
> The newer version in
> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-5/x86_64/
> is fine, for those looking for a workaround.
>
> On Wednesday, 10 June 2015 18:44:46 UTC+1, Eric Helms wrote:
>>
>> We found that the EL5 client repositories for 2.2 were signed incorrectly
>> and have updated and tested them. I have set
>> http://projects.theforeman.org/issues/10608 to resolved. Please let us
>> know if you hit further issues.
>>
>>
>> Eric
>>
>> On Fri, May 22, 2015 at 5:38 AM, Jamie Caldwell >> wrote:
>>
>>> Yes, will do Eric, not a problem.
>>>
>>> Before I do, so as to check I'm not putting in (extra) duff info, I
>>> believe the issue may be with the subscription-manager package, rather than
>>> my server cert rpm. Despite yum telling me subscription-manager has been
>>> successfully installed (when I install the cert), it isn't. yum also tells
>>> me subscription-manager was installed successfully, when tried on its own,
>>> but again it isn't.
>>>
>>> Following something I read on an old blog, which may have since been
>>> addressed, I'm wondering whether:
>>>
>>> rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
>>> subscription-manager-1.11.3-11.el5.x86_64.rpm:
>>> Header *V4* RSA/SHA1 signature: BAD, key ID d5a88496
>>> Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
>>> V4 RSA/SHA1 signature: BAD, key ID d5a88496
>>> MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
>>>
>>> V4 should be V3? I'm using --nogpgcheck, but I wondered whether this
>>> was still a factor?
>>>
>>> *# yum install --nogpgcheck subscription-manager*
>>>
>>> Installing:
>>> subscription-manager x86_64
>>> 1.11.3-11.el5 katello-agent 1.1 M
>>>
>>>
>>> Transaction Test Succeeded
>>> Running Transaction
>>> *error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>> signature: BAD, key ID d5a88496*
>>>
>>> *Installed:*
>>> * subscription-manager.x86_64 0:1.11.3-11.el5*
>>>
>>> Complete!
>>> *# rpm -qa --last | head -1*
>>> python-uuid-1.30-3.el5 Fri 22 May 2015 09:56:48
>>> BST
>>>
>>> And, could the same magic be applied to
>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/*6*/x86_64/,
>>> as I'm similarly relying on
>>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/x86_64/
>>> for subscription-manager and python-rhsm. Much appreciated.
>>>
>>> On 21 May 2015 at 16:08, Eric D Helms wrote:
>>>
>>>> This sounds familiar to another issue we hit with EL5 for another
>>>> package. Everything completes successfully though? Mind filing an issue
>>>> with this information ?
>>>>
>>>> On Thu, May 21, 2015 at 10:57 AM, Jamie Caldwell >>> > wrote:
>>>>
>>>>> Yes, this was installing
>>>>> http://katello/pub/katello-ca-consumer-latest.noarch.rpm (having
>>>>> first collected it with wget).
>>>>>
>>>>> On 21 May 2015 at 15:49, Eric D Helms wrote:
>>>>>
>>>>>> I don't think its the same issue. JC -- you are seeing this issue on
>>>>>> EL5 clients after trying to install the bootstrap RPM?
>>>>>>
>>>>>> On Thu, May 21, 2015 at 10:35 AM, Bryan Kearney >>>>>> wrote:
>>>>>>
>>>>>>> This was fixed downstream, can someone pull the newwer package in
>>>>>>> upstream?
>>>>>>>
>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1203580
>>>>>>>
>>>>>>> -- bk
>>>>>>>
>>>>>>>
>>>>>>> On 05/21/2015 10:21 AM, JC wrote:
>>>>>>>
>>>>>>>> error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>>>>>>> signature:
>>>>>>>> BAD, key ID d5a88496
>>>>>>>> Installing : katello-ca-consumer-myhostname.mydomain
>>>>>>>> Non-fatal POSTIN scriptlet failure in rpm package
>>>>>>>> katello-ca-myhostname.mydomain-1.0-1.noarch
>>>>>>>> error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
>>>>>>>> scriptlet failed, exit status 1
>>>>>>>>
>>>>>>>> Being non-fatal, it does install, but it's not as satisfying as I'd
>>>>>>>> like. Using my best investigative skills (lots of google searches),
>>>>>>>> the
>>>>>>>> common theme is selinux, but I have this in permissive mode (well I
>>>>>>>> do now).
>>>>>>>>
>>>>>>>> Looking at the rpm, the postinstallsection should just exit when it
>>>>>>>> doesn't find rhsm.conf(this is a CentOS 5 host):
>>>>>>>>
>>>>>>>> postinstall scriptlet (using /bin/sh):
>>>>>>>> #!/bin/bash
>>>>>>>> < snip >
>>>>>>>> KATELLO_SERVER=myhostname.mydomain
>>>>>>>> PORT=443
>>>>>>>> BASEURL=https://$KATELLO_SERVER/pulp/repos
>>>>>>>>
>>>>>>>> PREFIX=/rhsm
>>>>>>>> *CFG=/etc/rhsm/rhsm.conf*
>>>>>>>> CFG_BACKUP=$CFG.kat-backup
>>>>>>>>
>>>>>>>> # Get version of RHSM
>>>>>>>> RHSM_V="`rpm -q --queryformat='%{VERSION}' subscription-manager 2>
>>>>>>>> /dev/null | tr . ' '`"
>>>>>>>> if test $? != 0 ; then
>>>>>>>> RHSM_V="0 0 0"
>>>>>>>> fi
>>>>>>>> declare -a RHSM_VERSION=($RHSM_V)
>>>>>>>>
>>>>>>>> # exit on non-RHEL systems or when rhsm.conf is not found
>>>>>>>> *test -f $CFG || exit*
>>>>>>>> *
>>>>>>>> *
>>>>>>>> Anyone seen this before? The CentOS 6 test clients didn't have a
>>>>>>>> problem.
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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.
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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.
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/jZrMa8c-X1c/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, 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.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jamie.
>>>>>
>>>>> --
>>>>> 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.
>>>>>
>>>>
>>>> --
>>>> 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/jZrMa8c-X1c/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, 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.
>>>>
>>>
>>>
>>>
>>> --
>>> Jamie.
>>>
>>> --
>>> 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.
>>>
>>
>>
I'm with Nathan on this one, I have recently been tasked with implementing
Katello in our environment, and we're quickly discovering that the Katello
Agent only gets partially installed on RHEL5 systems due to a myriad of
improperly signed and required packages in the Katello 2.4 Client Yum
repository. This issue prevents us from successfully installing and
running Katello Agent on about 80% of the systems in our infrastructure, so
this is quite the impediment. As such, I have submitted Bug # 14974
(Bug #14974: Multitude of bad signatures for EL5 Katello 2.4 Client packages - Katello - Foreman). However, if there is anyone
in this forum that works closely with the Katello project and may be able
to lend a helping hand on getting it resolved, it would be greatly
appreciated!
···
On Thursday, May 5, 2016 at 9:12:38 PM UTC-5, Nathan Peters wrote:
>
> So I just tried this today and the 2.4 repo still has the same problem.
> Is that ever going to get fixed?
>
> On Thursday, November 19, 2015 at 3:55:46 AM UTC-8, JC wrote:
>>
>> Folks,
>>
>> subscription-manager in
>> https://fedorapeople.org/groups/katello/releases/yum/2.4/client/RHEL/5/x86_64/
>> has the same problem - V4 rather than V3.
>>
>> The newer version in
>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-5/x86_64/
>> is fine, for those looking for a workaround.
>>
>> On Wednesday, 10 June 2015 18:44:46 UTC+1, Eric Helms wrote:
>>>
>>> We found that the EL5 client repositories for 2.2 were signed
>>> incorrectly and have updated and tested them. I have set
>>> http://projects.theforeman.org/issues/10608 to resolved. Please let us
>>> know if you hit further issues.
>>>
>>>
>>> Eric
>>>
>>> On Fri, May 22, 2015 at 5:38 AM, Jamie Caldwell >>> wrote:
>>>
>>>> Yes, will do Eric, not a problem.
>>>>
>>>> Before I do, so as to check I'm not putting in (extra) duff info, I
>>>> believe the issue may be with the subscription-manager package, rather than
>>>> my server cert rpm. Despite yum telling me subscription-manager has been
>>>> successfully installed (when I install the cert), it isn't. yum also tells
>>>> me subscription-manager was installed successfully, when tried on its own,
>>>> but again it isn't.
>>>>
>>>> Following something I read on an old blog, which may have since been
>>>> addressed, I'm wondering whether:
>>>>
>>>> rpm -v --checksig subscription-manager-1.11.3-11.el5.x86_64.rpm
>>>> subscription-manager-1.11.3-11.el5.x86_64.rpm:
>>>> Header *V4* RSA/SHA1 signature: BAD, key ID d5a88496
>>>> Header SHA1 digest: OK (347ce92f655257467140bc842d122224f425aaa8)
>>>> V4 RSA/SHA1 signature: BAD, key ID d5a88496
>>>> MD5 digest: OK (2ff9ba31ad09f0524a9d9848e5baaeae)
>>>>
>>>> V4 should be V3? I'm using --nogpgcheck, but I wondered whether this
>>>> was still a factor?
>>>>
>>>> *# yum install --nogpgcheck subscription-manager*
>>>>
>>>> Installing:
>>>> subscription-manager x86_64
>>>> 1.11.3-11.el5 katello-agent 1.1 M
>>>>
>>>>
>>>> Transaction Test Succeeded
>>>> Running Transaction
>>>> *error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>>> signature: BAD, key ID d5a88496*
>>>>
>>>> *Installed:*
>>>> * subscription-manager.x86_64 0:1.11.3-11.el5*
>>>>
>>>> Complete!
>>>> *# rpm -qa --last | head -1*
>>>> python-uuid-1.30-3.el5 Fri 22 May 2015 09:56:48
>>>> BST
>>>>
>>>> And, could the same magic be applied to
>>>> https://fedorapeople.org/groups/katello/releases/yum/2.2/client/RHEL/
>>>> *6*/x86_64/, as I'm similarly relying on
>>>> https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/x86_64/
>>>> for subscription-manager and python-rhsm. Much appreciated.
>>>>
>>>> On 21 May 2015 at 16:08, Eric D Helms wrote:
>>>>
>>>>> This sounds familiar to another issue we hit with EL5 for another
>>>>> package. Everything completes successfully though? Mind filing an issue
>>>>> with this information ?
>>>>>
>>>>> On Thu, May 21, 2015 at 10:57 AM, Jamie Caldwell < >>>>> mr.jamie...@gmail.com> wrote:
>>>>>
>>>>>> Yes, this was installing
>>>>>> http://katello/pub/katello-ca-consumer-latest.noarch.rpm (having
>>>>>> first collected it with wget).
>>>>>>
>>>>>> On 21 May 2015 at 15:49, Eric D Helms wrote:
>>>>>>
>>>>>>> I don't think its the same issue. JC -- you are seeing this issue on
>>>>>>> EL5 clients after trying to install the bootstrap RPM?
>>>>>>>
>>>>>>> On Thu, May 21, 2015 at 10:35 AM, Bryan Kearney >>>>>> > wrote:
>>>>>>>
>>>>>>>> This was fixed downstream, can someone pull the newwer package in
>>>>>>>> upstream?
>>>>>>>>
>>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1203580
>>>>>>>>
>>>>>>>> -- bk
>>>>>>>>
>>>>>>>>
>>>>>>>> On 05/21/2015 10:21 AM, JC wrote:
>>>>>>>>
>>>>>>>>> error: subscription-manager-1.11.3-11.el5: Header V4 RSA/SHA1
>>>>>>>>> signature:
>>>>>>>>> BAD, key ID d5a88496
>>>>>>>>> Installing : katello-ca-consumer-myhostname.mydomain
>>>>>>>>> Non-fatal POSTIN scriptlet failure in rpm package
>>>>>>>>> katello-ca-myhostname.mydomain-1.0-1.noarch
>>>>>>>>> error: %post(katello-ca-consumer-myhostname.mydomain-1.0-1.noarch)
>>>>>>>>> scriptlet failed, exit status 1
>>>>>>>>>
>>>>>>>>> Being non-fatal, it does install, but it's not as satisfying as I'd
>>>>>>>>> like. Using my best investigative skills (lots of google
>>>>>>>>> searches), the
>>>>>>>>> common theme is selinux, but I have this in permissive mode (well
>>>>>>>>> I do now).
>>>>>>>>>
>>>>>>>>> Looking at the rpm, the postinstallsection should just exit when it
>>>>>>>>> doesn't find rhsm.conf(this is a CentOS 5 host):
>>>>>>>>>
>>>>>>>>> postinstall scriptlet (using /bin/sh):
>>>>>>>>> #!/bin/bash
>>>>>>>>> < snip >
>>>>>>>>> KATELLO_SERVER=myhostname.mydomain
>>>>>>>>> PORT=443
>>>>>>>>> BASEURL=https://$KATELLO_SERVER/pulp/repos
>>>>>>>>>
>>>>>>>>> PREFIX=/rhsm
>>>>>>>>> *CFG=/etc/rhsm/rhsm.conf*
>>>>>>>>> CFG_BACKUP=$CFG.kat-backup
>>>>>>>>>
>>>>>>>>> # Get version of RHSM
>>>>>>>>> RHSM_V="`rpm -q --queryformat='%{VERSION}' subscription-manager 2>
>>>>>>>>> /dev/null | tr . ' '`"
>>>>>>>>> if test $? != 0 ; then
>>>>>>>>> RHSM_V="0 0 0"
>>>>>>>>> fi
>>>>>>>>> declare -a RHSM_VERSION=($RHSM_V)
>>>>>>>>>
>>>>>>>>> # exit on non-RHEL systems or when rhsm.conf is not found
>>>>>>>>> *test -f $CFG || exit*
>>>>>>>>> *
>>>>>>>>> *
>>>>>>>>> Anyone seen this before? The CentOS 6 test clients didn't have a
>>>>>>>>> problem.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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.
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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/jZrMa8c-X1c/unsubscribe
>>>>>>> .
>>>>>>> To unsubscribe from this group and all its topics, 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.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jamie.
>>>>>>
>>>>>> --
>>>>>> 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.
>>>>>>
>>>>>
>>>>> --
>>>>> 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/jZrMa8c-X1c/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, 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.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jamie.
>>>>
>>>> --
>>>> 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.
>>>>
>>>
>>>
