Hi,
I'm trying to update our katello/foreman install but get the following
errors:
Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is not signed
Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not signed
Is there something going wrong with the signing of the foreman plugins
packages?
Kind regards,
Jorick Astrego
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
Plugin packages never have been signed, so this is normal (although it
sounds like you might have gpgcheck=1 set when it should be 0).
···
On 13/01/15 15:54, Jorick Astrego wrote:
> Hi,
>
> I'm trying to update our katello/foreman install but get the following
> errors:
>
> Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is not
> signed
>
> Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not
> signed
>
> Is there something going wrong with the signing of the foreman plugins
> packages?
–
Dominic Cleal
Red Hat Engineering
Ok, is there a way to do this when using katello? We use the locally
synced repo's an katello to manage them.
I set the GPG key in the local foreman plugins repo now but it still
fails on the unsigned packages.
Regards,
Jorick
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
···
On 01/14/2015 09:53 AM, Dominic Cleal wrote:
> On 13/01/15 15:54, Jorick Astrego wrote:
>> Hi,
>>
>> I'm trying to update our katello/foreman install but get the following
>> errors:
>>
>> Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is not
>> signed
>>
>> Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not
>> signed
>>
>> Is there something going wrong with the signing of the foreman plugins
>> packages?
> Plugin packages never have been signed, so this is normal (although it
> sounds like you might have gpgcheck=1 set when it should be 0).
>
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
Sorry that should be "I removed the GPG key in the local foreman
plugins repo in katello", need some coffee 
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
···
On 01/14/2015 12:25 PM, Jorick Astrego wrote:
>
> On 01/14/2015 09:53 AM, Dominic Cleal wrote:
> > On 13/01/15 15:54, Jorick Astrego wrote:
> >> Hi,
> >>
> >> I'm trying to update our katello/foreman install but get the following
> >> errors:
> >>
> >> Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is
> not
> >> signed
> >>
> >> Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not
> >> signed
> >>
> >> Is there something going wrong with the signing of the foreman plugins
> >> packages?
> > Plugin packages never have been signed, so this is normal (although it
> > sounds like you might have gpgcheck=1 set when it should be 0).
> >
>
> Ok, is there a way to do this when using katello? We use the locally
> synced repo's an katello to manage them.
>
> I set the GPG key in the local foreman plugins repo now but it still
> fails on the unsigned packages.
>
> Regards,
>
> Jorick
>
----------------
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
Maybe subscription-manager refresh
on the client? It should set
gpgcheck=0 for any repo that doesn't have a gpg key.
···
On Wed, Jan 14, 2015 at 12:31:18PM +0100, Jorick Astrego wrote:
>
> On 01/14/2015 12:25 PM, Jorick Astrego wrote:
> >
> > On 01/14/2015 09:53 AM, Dominic Cleal wrote:
> > > On 13/01/15 15:54, Jorick Astrego wrote:
> > >> Hi,
> > >>
> > >> I'm trying to update our katello/foreman install but get the following
> > >> errors:
> > >>
> > >> Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is
> > not
> > >> signed
> > >>
> > >> Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not
> > >> signed
> > >>
> > >> Is there something going wrong with the signing of the foreman plugins
> > >> packages?
> > > Plugin packages never have been signed, so this is normal (although it
> > > sounds like you might have gpgcheck=1 set when it should be 0).
> > >
> >
> > Ok, is there a way to do this when using katello? We use the locally
> > synced repo's an katello to manage them.
> >
> > I set the GPG key in the local foreman plugins repo now but it still
> > fails on the unsigned packages.
> >
> > Regards,
> >
> > Jorick
> >
> Sorry that should be "I _removed_ the GPG key in the local foreman
> plugins repo _in katello_", need some coffee ;-)
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
···
On 01/14/2015 01:48 PM, Stephen Benjamin wrote:
> On Wed, Jan 14, 2015 at 12:31:18PM +0100, Jorick Astrego wrote:
>>
>> On 01/14/2015 12:25 PM, Jorick Astrego wrote:
>>>
>>> On 01/14/2015 09:53 AM, Dominic Cleal wrote:
>>>> On 13/01/15 15:54, Jorick Astrego wrote:
>>>>> Hi,
>>>>>
>>>>> I'm trying to update our katello/foreman install but get the following
>>>>> errors:
>>>>>
>>>>> Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is
>>> not
>>>>> signed
>>>>>
>>>>> Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not
>>>>> signed
>>>>>
>>>>> Is there something going wrong with the signing of the foreman plugins
>>>>> packages?
>>>> Plugin packages never have been signed, so this is normal (although it
>>>> sounds like you might have gpgcheck=1 set when it should be 0).
>>>>
>>>
>>> Ok, is there a way to do this when using katello? We use the locally
>>> synced repo's an katello to manage them.
>>>
>>> I set the GPG key in the local foreman plugins repo now but it still
>>> fails on the unsigned packages.
>>>
>>> Regards,
>>>
>>> Jorick
>>>
>> Sorry that should be "I _removed_ the GPG key in the local foreman
>> plugins repo _in katello_", need some coffee ;-)
>
>
> Maybe `subscription-manager refresh` on the client? It should set
> gpgcheck=0 for any repo that doesn't have a gpg key.
Nope, did a refresh and also more than 4 hours have passed. Still the
same error…
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
Nope, did a refresh and also more than 4 hours have passed. Still the
same error…
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
···
On 01/14/2015 01:48 PM, Stephen Benjamin wrote:
> On Wed, Jan 14, 2015 at 12:31:18PM +0100, Jorick Astrego wrote:
>> On 01/14/2015 12:25 PM, Jorick Astrego wrote:
>>> On 01/14/2015 09:53 AM, Dominic Cleal wrote:
>>>> On 13/01/15 15:54, Jorick Astrego wrote:
>>>>> Hi,
>>>>>
>>>>> I'm trying to update our katello/foreman install but get the following
>>>>> errors:
>>>>>
>>>>> Package ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch.rpm is
>>> not
>>>>> signed
>>>>>
>>>>> Package ruby193-rubygem-foreman_dhcp_browser-0.0.6-1.el6.noarch is not
>>>>> signed
>>>>>
>>>>> Is there something going wrong with the signing of the foreman plugins
>>>>> packages?
>>>> Plugin packages never have been signed, so this is normal (although it
>>>> sounds like you might have gpgcheck=1 set when it should be 0).
>>>>
>>> Ok, is there a way to do this when using katello? We use the locally
>>> synced repo's an katello to manage them.
>>>
>>> I set the GPG key in the local foreman plugins repo now but it still
>>> fails on the unsigned packages.
>>>
>>> Regards,
>>>
>>> Jorick
>>>
>> Sorry that should be "I _removed_ the GPG key in the local foreman
>> plugins repo _in katello_", need some coffee ;-)
>
> Maybe `subscription-manager refresh` on the client? It should set
> gpgcheck=0 for any repo that doesn't have a gpg key.
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