My Spacewalk version is 2.4. Installed on Centos 7.2
________________________________________
From: [email protected] <[email protected]> on
behalf of [email protected] <[email protected]>
Sent: Tuesday, May 10, 2016 3:36 PM
To: [email protected]
Subject: Spacewalk-list Digest, Vol 96, Issue 16
Send Spacewalk-list mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/spacewalk-list
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Spacewalk-list digest..."
Today's Topics:
1. Re: help (Max Mitschke) (Max Mitschke)
2. Re: import errata to spacewalk (Rose Dowson)
3. Re: import errata to spacewalk (Lo?c Chanel)
4. Provisioning from WebConsole (Philipp Wehling)
----------------------------------------------------------------------
Message: 1
Date: Mon, 9 May 2016 19:03:58 +0000
From: Max Mitschke <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: Re: [Spacewalk-list] help (Max Mitschke)
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hello,
First off, my apologies about the title. If I have a question next time I will
make it more descriptive.
I was able to resolve my issue by increasing the memory usage for Spacewalk.
In /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf:
I increased wrapper.java.initmemory from 256 to 512.
I increased wrapper.java.maxmemory from 1024 to 2048
I checked both the checksum and size of the java package in the repository and
spacewalk; everything looked good. I believe that this would be a proper method
of checking the package. If not, then please advise another way of doing so.
Lastly, I checked the taskomatic log and could not find anything related to
memory issues or the repodata job failing.
My issue has been resolved. Thank you for your help!
Max Mitschke
Message: 5
Date: Mon, 09 May 2016 11:22:29 -0400
From: mailto:[email protected]
To: Max Mitschke <mailto:[email protected]>,
"'[email protected]'" <mailto:[email protected]>
Subject: Re: [Spacewalk-list] help
Message-ID: <mailto:[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
This sounds like one of 3 things
An incomplete repo sync,
A failed repodata job in taskomatic (usually happens when the memory tuning
settings are too low, check the taskomaic logs.)
Or a corrupt package in your repo.
? Original Message ?
From: Max Mitschke
Sent: Monday, May 9, 2016 03:22
To: '[email protected]'
Reply To: mailto:[email protected]
Subject: [Spacewalk-list] help
Hello,
When I try to update the java-1.8.0-openjdk package on a CentOS 6 server using
Spacewalk, I am receiving the following error message:
"Error while executing packages action: Error Downloading Packages:
1:java-1.8.0-openjdk-headless-1.8.0.91-0.b14.el6_7.x86_64: failed to retrieve
getPackage/java-1.8.0-openjdk-headless-1.8.0.91-0.b14.el6_7.x86_64.rpm from
centos-6-base error was [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=centos-6-base clean metadata [[6]]"
I have tried the suggested resolution but the issue still occurs. In addition,
I have cleared the cache on the Spacewalk server, restarted taskomatic, and
attempted to install updates but to no avail. Lastly, I have tried resyncing
the channel that contains the package and attempted to install the updates.
The only way I was able to resolve this issue was by running the following
command on the server:
yum update java-1.8.0-openjdk* --disablerepo=* --enablerepo=base
--enablerepo=updates --enablerepo=extras
I was wondering if this was a common issue with Spacewalk and java packages? If
not, would someone be able to help resolve the issue?
Thanks,
Max Mitschke
________________________________
This electronic transmission and any information that it contains is the
property of MSU Federal Credit Union and is intended for the use of the
intended recipient. If you are not the intended recipient, any disclosure,
copying or other use of this information is strictly prohibited. If you
acquired this transmission in error or feel that any of the information
contained within it is offensive or inappropriate, please contact
[email protected]<mailto:[email protected]>.
------------------------------
Message: 2
Date: Tue, 10 May 2016 08:40:21 +0100
From: Rose Dowson <[email protected]>
To: [email protected]
Subject: Re: [Spacewalk-list] import errata to spacewalk
Message-ID:
<caa3lwtzmew7uoxpux9wjrumopidtswvkmbtrmxsplzy+rfr...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
I have a problem about deploying errata to my ubuntu clients (12.04 LTS
and 14.04 LTS). Every time the schedule action failed.
Do you have any ideas ?
Thank you for the help.
Best Regards,
2016-05-06 16:00 GMT+01:00 Steve Meier <[email protected]>:
> Hi Kris,
>
> the answer is simple: You don't need to distinguish between 32 and 64 bit.
>
> The way that the import scripts work is straightforward. For each erratum
> all
> files for all versions and architectures are listed in the XML file. The
> script will then check which of these RPMs is present in your Spacewalk and
> link those to the erratum. It will not download or sync any RPMs into your
> Spacewalk that aren't already there.
>
> Hope this helps.
>
> Kind regards,
> Steve
>
>
>
>
> Am 2016-05-06 15:43, schrieb Kristijan Besu:
>
>> Dear Steve Meier,
>>
>> I have a simply question regarding errata-import.pl script. I followed
>> the instruction on following portal:
>>
>> https://cefs.steve-meier.de/
>>
>> Script works great, just dont know how to distinguished 64 from 32
>> errata packages during errata import into the spacewalk since there is
>> no such option included into the script.
>>
>> I am running following command:
>>
>> for example:
>>
>> SPACEWALK_PASS=xyz SPACEWALK_USER=su-errata
>> /opt/tools/errata-import.pl --server localhost \
>> --errata errata.latest.xml
>> --include-channels=centos6-updates-x86_64,epel-el6-x86_64 \
>> --rhsa-oval=/tmp/com.redhat.rhsa-all.xml --publish
>>
>> but on the end both architectures 64bit and 32bit have been imported
>> to my spacewalk channels. Is there a possibility to add --os-version
>> option or --architecture option.
>>
>> Please let me know if there is a workaround to this issue?
>>
>> Thank you in advance,
>>
>> Kris
>> _______________________________________________
>> Spacewalk-list mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://www.redhat.com/archives/spacewalk-list/attachments/20160510/6d6814d7/attachment.html>
------------------------------
Message: 3
Date: Tue, 10 May 2016 09:49:08 +0200
From: Lo?c Chanel <[email protected]>
To: [email protected]
Subject: Re: [Spacewalk-list] import errata to spacewalk
Message-ID:
<CAEg_P-LGs-y=crm-on5oe_-nkkbwvymlwojfvs8vnvaiw_a...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
What is your Spacewalk version ?
Lo?c CHANEL
System & virtualization engineer
TO - XaaS Ind - Worldline (Villeurbanne, France)
2016-05-10 9:40 GMT+02:00 Rose Dowson <[email protected]>:
> Hi,
>
> I have a problem about deploying errata to my ubuntu clients (12.04 LTS
> and 14.04 LTS). Every time the schedule action failed.
> Do you have any ideas ?
> Thank you for the help.
>
> Best Regards,
>
> 2016-05-06 16:00 GMT+01:00 Steve Meier <[email protected]>:
>
>> Hi Kris,
>>
>> the answer is simple: You don't need to distinguish between 32 and 64 bit.
>>
>> The way that the import scripts work is straightforward. For each erratum
>> all
>> files for all versions and architectures are listed in the XML file. The
>> script will then check which of these RPMs is present in your Spacewalk
>> and
>> link those to the erratum. It will not download or sync any RPMs into your
>> Spacewalk that aren't already there.
>>
>> Hope this helps.
>>
>> Kind regards,
>> Steve
>>
>>
>>
>>
>> Am 2016-05-06 15:43, schrieb Kristijan Besu:
>>
>>> Dear Steve Meier,
>>>
>>> I have a simply question regarding errata-import.pl script. I followed
>>> the instruction on following portal:
>>>
>>> https://cefs.steve-meier.de/
>>>
>>> Script works great, just dont know how to distinguished 64 from 32
>>> errata packages during errata import into the spacewalk since there is
>>> no such option included into the script.
>>>
>>> I am running following command:
>>>
>>> for example:
>>>
>>> SPACEWALK_PASS=xyz SPACEWALK_USER=su-errata
>>> /opt/tools/errata-import.pl --server localhost \
>>> --errata errata.latest.xml
>>> --include-channels=centos6-updates-x86_64,epel-el6-x86_64 \
>>> --rhsa-oval=/tmp/com.redhat.rhsa-all.xml --publish
>>>
>>> but on the end both architectures 64bit and 32bit have been imported
>>> to my spacewalk channels. Is there a possibility to add --os-version
>>> option or --architecture option.
>>>
>>> Please let me know if there is a workaround to this issue?
>>>
>>> Thank you in advance,
>>>
>>> Kris
>>> _______________________________________________
>>> Spacewalk-list mailing list
>>> [email protected]
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://www.redhat.com/archives/spacewalk-list/attachments/20160510/55265696/attachment.html>
------------------------------
Message: 4
Date: Tue, 10 May 2016 15:36:26 +0200 (CEST)
From: Philipp Wehling <[email protected]>
To: [email protected]
Subject: [Spacewalk-list] Provisioning from WebConsole
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
Hello,
when Provisioning from WebConsole, I get some weird error:
At first, here is the output from rhn_check after scheduling the kickstart:
[root@hostname ~]# rhn_check
Preserve files! : []
- looking for Cobbler at http://spacewalkserver:443/cobbler_api
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/koan/utils.py", line 570, in
__try_connect
xmlrpc_server.ping()
File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.7/xmlrpclib.py", line 1587, in __request
verbose=self.__verbose
File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib64/python2.7/xmlrpclib.py", line 1321, in single_request
response.msg,
ProtocolError: <ProtocolError for spacewalkserver:443/cobbler_api: 400 Bad
Request>
- looking for Cobbler at https://spacewalkserver:443/cobbler_api
- reading URL: http://spacewalkserver/cblr/svc/op/ks/system/hostname:1
install_tree: http://spacewalkserver/ty/RGlonnd5
downloading initrd initrd.img to /boot/initrd.img_koan
url=http://spacewalkserver/cobbler/images/CentOS7-x86_64-dist:1:SpacewalkDefaultOrganization/initrd.img
- reading URL:
http://spacewalkserver/cobbler/images/CentOS7-x86_64-dist:1:SpacewalkDefaultOrganization/initrd.img
downloading kernel vmlinuz to /boot/vmlinuz_koan
url=http://spacewalkserver/cobbler/images/CentOS7-x86_64-dist:1:SpacewalkDefaultOrganization/vmlinuz
- reading URL:
http://spacewalkserver/cobbler/images/CentOS7-x86_64-dist:1:SpacewalkDefaultOrganization/vmlinuz
- ['/sbin/grubby', '--add-kernel', '/boot/vmlinuz_koan', '--initrd',
'/boot/initrd.img_koan', '--args', '"ksdevice=ens160 lang= text
hostname=hostname ks=file:ks.cfg netmask=255.255.255.0 dns=<ip> ip=<ip>
kssendmac gateway=<ip> "', '--make-default', '--title=kick1462878829']
- ['/sbin/grubby', '--update-kernel', '/boot/vmlinuz_koan',
'--remove-args=root']
- reboot to apply changes
Shutdown scheduled for Tue 2016-05-10 13:16:49 CEST, use 'shutdown -c' to
cancel.
Broadcast message from root@hostname (Tue 2016-05-10 13:13:49 CEST):
Reboot of system "hostname" initiated by Spacewalk reboot action.
The system is going down for reboot at Tue 2016-05-10 13:16:49 CEST!
The problem I have is marked: ks=file:ks.cfg
Isnt this wrong?
When I do a Kickstart with an ISO-Image, ks= contains an url to my spacewalk
server.
Then, when rebooting, there is the error message:
Cant find file:ks.cfg
kind regards,
Philipp
Sie kC6nnen uns "live" erleben.
ILA Berlin Air Show
01. - 04. Juni 2016 - Berlin ExpoCenter Airport
Halle 4, Stand 4201 / http://www.ila-berlin.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://www.redhat.com/archives/spacewalk-list/attachments/20160510/54b04128/attachment.html>
------------------------------
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
End of Spacewalk-list Digest, Vol 96, Issue 16
**********************************************
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
