[Spacewalk-list] Can't install post kickstart install

Lachlan Musicman datakid at gmail.com
Mon Apr 4 22:41:48 UTC 2016


Sorry, I should be clear.

We have an SSL cert on that page - is that not enough? Do I need a separate
gpg key? I would presume the cert was sufficient - at no point in the
documentation did I see an explicit instruction to make one of each?

cheers
L.

------
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 5 April 2016 at 08:13, Lachlan Musicman <datakid at gmail.com> wrote:

> Andreas,
>
> Thanks for your response - but I've already done that. AND it's
> transferred during the installation. This is what I don't understand and am
> trying to get to the bottom of - I have a GPG key, and it's on the machine
> in question. But yum installs and webui installs still fail?
>
> Cheers
> L.
>
> ------
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 4 April 2016 at 16:43, Andreas Dijkman <Andreas.Dijkman at cygnis.nl>
> wrote:
>
>> In the kickstart-menu is also a submenu GPG and SSL Keys. Create your
>> keys there and import them into your kickstart profile.
>>
>> That part is in a submenu of your kickstart profile System Details -> GPG
>> & SSL.
>>
>> Kind regards,
>>
>> Andreas Dijkman
>>
>>
>> On 04 Apr 2016, at 08:23, Lachlan Musicman <datakid at gmail.com> wrote:
>>
>> Is it because my kickstart software channel is based on the tree
>> /var/distro-trees/Centos-7 (which is essentially the maximum install dvd
>> with all the rpms removed), and that has a key RPM-GPG-KEY-CentOS-7 which
>> I'm not importing?
>>
>> How would I import that?
>>
>> cheers
>> L.
>>
>> ------
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 4 April 2016 at 16:09, Lachlan Musicman <datakid at gmail.com> wrote:
>>
>>> Hola,
>>>
>>> After installation via kickstart, I get the following errors (first the
>>> webui, then the cli):
>>>
>>> Client execution returned "Error while executing packages action: Public
>>> key for htop-2.0.1-1.el7.x86_64.rpm is not installed [[6]]" (code -1)
>>>
>>> [root at vmpr-res-head-node rhn]# yum install htop
>>> Loaded plugins: fastestmirror, langpacks, rhnplugin
>>> Adding en_US.UTF-8 to language list
>>> Config time: 0.031
>>> This system is receiving updates from RHN Classic or Red Hat Satellite.
>>> Looking for repo options for [main]
>>> Looking for repo options for [centos_7_x86_64]
>>> Repo 'centos_7_x86_64' setting option 'enabled' = '1'
>>> Repo 'centos_7_x86_64' setting option 'gpgcheck' = '1'
>>> Repo 'centos_7_x86_64' setting option 'timeout' = '120'
>>> Looking for repo options for [slurm_15.08]
>>> Repo 'slurm_15.08' setting option 'enabled' = '1'
>>> Repo 'slurm_15.08' setting option 'gpgcheck' = '1'
>>> Repo 'slurm_15.08' setting option 'timeout' = '120'
>>> Looking for repo options for [jpackage_5.0_noarch]
>>> Repo 'jpackage_5.0_noarch' setting option 'enabled' = '1'
>>> Repo 'jpackage_5.0_noarch' setting option 'gpgcheck' = '1'
>>> Repo 'jpackage_5.0_noarch' setting option 'timeout' = '120'
>>> Looking for repo options for [centos_7_x86_64_base]
>>> Repo 'centos_7_x86_64_base' setting option 'enabled' = '1'
>>> Repo 'centos_7_x86_64_base' setting option 'gpgcheck' = '1'
>>> Repo 'centos_7_x86_64_base' setting option 'timeout' = '120'
>>> Looking for repo options for [centos_7_x86_64_extras]
>>> Repo 'centos_7_x86_64_extras' setting option 'enabled' = '1'
>>> Repo 'centos_7_x86_64_extras' setting option 'gpgcheck' = '1'
>>> Repo 'centos_7_x86_64_extras' setting option 'timeout' = '120'
>>> Looking for repo options for [zabbix_x86_64]
>>> Repo 'zabbix_x86_64' setting option 'enabled' = '1'
>>> Repo 'zabbix_x86_64' setting option 'gpgcheck' = '1'
>>> Repo 'zabbix_x86_64' setting option 'timeout' = '120'
>>> Looking for repo options for [spacewalk_x86_64_client]
>>> Repo 'spacewalk_x86_64_client' setting option 'enabled' = '1'
>>> Repo 'spacewalk_x86_64_client' setting option 'gpgcheck' = '1'
>>> Repo 'spacewalk_x86_64_client' setting option 'timeout' = '120'
>>> Looking for repo options for [spacewalk_x86_64_server]
>>> Repo 'spacewalk_x86_64_server' setting option 'enabled' = '1'
>>> Repo 'spacewalk_x86_64_server' setting option 'gpgcheck' = '1'
>>> Repo 'spacewalk_x86_64_server' setting option 'timeout' = '120'
>>> Looking for repo options for [epel_7_x86_64]
>>> Repo 'epel_7_x86_64' setting option 'enabled' = '1'
>>> Repo 'epel_7_x86_64' setting option 'gpgcheck' = '1'
>>> Repo 'epel_7_x86_64' setting option 'timeout' = '120'
>>> Looking for repo options for [cisco_snic_x86_64]
>>> Repo 'cisco_snic_x86_64' setting option 'enabled' = '1'
>>> Repo 'cisco_snic_x86_64' setting option 'gpgcheck' = '1'
>>> Repo 'cisco_snic_x86_64' setting option 'timeout' = '120'
>>> Looking for repo options for [centos_7_x86_64_updates]
>>> Repo 'centos_7_x86_64_updates' setting option 'enabled' = '1'
>>> Repo 'centos_7_x86_64_updates' setting option 'gpgcheck' = '1'
>>> Repo 'centos_7_x86_64_updates' setting option 'timeout' = '120'
>>> Yum version: 3.4.3
>>>
>>> You have enabled checking of packages via GPG keys. This is a good
>>> thing.
>>> However, you do not have any GPG public keys installed. You need to
>>> download
>>> the keys for packages you wish to install and install them.
>>> You can do that by running the command:
>>>     rpm --import public.gpg.key
>>>
>>>
>>> Alternatively you can specify the url to the key you would like to use
>>> for a repository in the 'gpgkey' option in a repository section and yum
>>> will install it for you.
>>>
>>> For more information contact your distribution or package provider.
>>>
>>> Problem repository: centos_7_x86_64
>>>
>>>
>>>
>>> There are a number main issues here.
>>>
>>> 1. AFAICT, the Activation key associated with this base/parent channel
>>> (RHN-ORG-TRUSTED-SSL-CERT) has successfully been bought across. Why
>>> wouldn't this work, and why would it fail on centos_7_x86_64, which is the
>>> base channel with no rpms? (we have a centos_7_x86_64_base child channel
>>> with all the rpms, because having the rpms in the base/parent channel
>>> doesn't work for kickstart installs...)
>>>
>>> 2. I want all my servers to only talk to the Spacewalk server for
>>> purposes of yum. So the key problem should only exist for the Spacewalk
>>> server if any server is affected by it.
>>>
>>> 3. I'm not sure where the local spacewalk repos are set enabled=1,
>>> /etc/yum.repos.d/ is empty.
>>>
>>> cheers
>>> L.
>>>
>>>
>>>
>>>
>>> ------
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160405/c148d7f1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-04-05 08-16-13.png
Type: image/png
Size: 34914 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160405/c148d7f1/attachment.png>


More information about the Spacewalk-list mailing list