Re: [Spacewalk-list] Ubuntu/Deb Support
Am 27. September 2018 22:55:40 MESZ schrieb "Randall R. Sargent"
:
>I'm still unable to update packages on Xenial. I've updated
>'/usr/lib/python2.7/site-packages/spacewalk/server/rhnRepository.py' to
>include Release files, I'm using spacewalk-debian-sync.pl &
>spacewalk-add-debian-multiarch-header.py to sync repos and
>'secureApt.sh' to sign the files. Running 'apt update' on the client
>gives zero errors on the Spacewalk repos. Still not working.
Also no warning anymore about low security SHA1?
Well...I would tail the http logs while trying to update a package on the
client. As it is trying to update the cache, you should find requests to your
release and package files.
Finally.. Debug python. Schedule a package install via SW and run "python -i -m
pdb $(which rhn_check)" on the client
You need to know the line within the python-apt module you want to start debug.
(I think it's the "update" function within the "cache.py" file). Set a
breakpoint within debugger with "break :"
Robert
>
>Does anyone have ideas? How can I debug to get the reason why the
>rhnpush-initiated update is failing?
>
>/etc/rhn/spacewalk-debian-sync.pl
>--url=http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/
>--channel=xenial-main --username= --password=
>
>/etc/rhn/spacewalk-add-debian-multiarch-header.py
>/var/cache/rhn/repodata/xenial-main/Packages
>/var/satellite/sat-tmp/xenial-main
>
>gzip -c /var/cache/rhn/repodata/xenial-main/Packages.new >
>/var/cache/rhn/repodata/xenial-main/Packages.gz && touch -r
>/var/cache/rhn/repodata/xenial-main/Packages
>
>/var/cache/rhn/repodata/xenial-main/Packages.gz
>
>/etc/rhn/secureApt.sh xenial-main Xenial
>
>-Original Message-
>From: Randall R. Sargent
>Sent: Thursday, September 27, 2018 8:40 AM
>To: 'Robert Paschedag' ;
>spacewalk-list@redhat.com
>Cc: spacewalk-list@redhat.com
>Subject: RE: [Spacewalk-list] Ubuntu/Deb Support
>
>The other issue I'm having is the sync script keeps keeps giving me
>"rhnpush failed". The first time it was permissions issues for the
>apache process on /tmp. I fixed that and got about 75% of the way
>finished syncing, then it did it again. Next I tried running it as
>'apache' and now I'm getting permission issues writing to
>'/usr/share/httpd/.rhnpushcache'.
>
>-Original Message-
>From: Robert Paschedag
>Sent: Thursday, September 27, 2018 12:07 AM
>To: spacewalk-list@redhat.com; Randall R. Sargent
>
>Cc: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] Ubuntu/Deb Support
>
>Am 27. September 2018 07:03:19 MESZ schrieb Robert Paschedag
>:
>>Am 26. September 2018 18:01:16 MESZ schrieb "Randall R. Sargent"
>>:
>>>Thanks Robert.
>>>
>>>I applied the patch for rhnRepository.py and verified the client
>>>version is up to date using the criteria gave (spacewalk.list). I did
>
>>>follow Phil's blog and have been able to create Release & Release.gpg
>
>>>files. I did not do any of the patching he mentioned though because
>>I'm
>>>assuming my versions are updated since he wrote the post.
>>>
>>>Attempting to patch after that gives me the same error.
>>>
>>>Next I am trying to run your add-multiarch-header script but am
>>getting
>>>the following error:
>>>
>>>/etc/rhn/spacewalk-add-debian-multiarch-header.py
>>>/var/cache/rhn/repodata/xenial-main/Packages /tmp/xenial-main
>>>Error: Inputfile '/tmp/xenial-main' not available.
>>>
>>>Am I just running your modified script, or do I need to run
>>>spacewalk-debian-sync.pl before?
>>
>>Of course you must sync the repos with the modified sync script (as
>>stated). This extracts the Multi-Arch headers from the original Ubuntu
>
>>/ Debian repos and writes them to temporary files within /tmp.
>
>But you should check your repos are signed correctly by running apt-get
>update.
>
>If this does not work correctly or complains about missing release
>files, you made a mistake somewhere.
>
>Robert
>>
>>Robert
>>>
>>>Thanks again.
>>>
>>>-Original Message-
>>>From: Robert Paschedag
>>>Sent: Wednesday, September 26, 2018 10:10 AM
>>>To: Randall R. Sargent
>>>Cc: spacewalk-list@redhat.com
>>>Subject: Aw: RE: [Spacewalk-list] Ubuntu/Deb Support
>>>
>>>
>>>
Gesendet: Mittwoch, 26. September 2018 um 15:16 Uhr
Von: "Randall R. Sargent"
An: "Robert Paschedag" ,
"spacewalk-list@redhat.com" ,
"spacewalk-list@redhat.com"
Betreff: RE: [Spacewalk-list] Ubuntu/Deb Support
I'm having no luck getting my xenial clients to recognize the
>>Release
>>>& Release.gpg files in my repos. I resorted to modifying the
>>>pre-invoke.py script to write [trusted=yes] for each line in
>>>spacewalk.list, now I'm no longer getting complaints about missing
>>>Release files when I do an apt update. I am still unable to upgrade
>>any
>>>packages though:
# rhn_check -
D: check_action{'action': ">>>
>>>version='1.0'?>\n\npackages.update>>>
\n\n\n\n\n>>>
>>>ue>bind9-host\n9.10.3.dfsg.P4<
>>>/string>\n8ubuntu1.11\n
>>>1\
Re: [Spacewalk-list] Ubuntu/Deb Support
I'm still unable to update packages on Xenial. I've updated
'/usr/lib/python2.7/site-packages/spacewalk/server/rhnRepository.py' to include
Release files, I'm using spacewalk-debian-sync.pl &
spacewalk-add-debian-multiarch-header.py to sync repos and 'secureApt.sh' to
sign the files. Running 'apt update' on the client gives zero errors on the
Spacewalk repos. Still not working.
Does anyone have ideas? How can I debug to get the reason why the
rhnpush-initiated update is failing?
/etc/rhn/spacewalk-debian-sync.pl
--url=http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/
--channel=xenial-main --username= --password=
/etc/rhn/spacewalk-add-debian-multiarch-header.py
/var/cache/rhn/repodata/xenial-main/Packages /var/satellite/sat-tmp/xenial-main
gzip -c /var/cache/rhn/repodata/xenial-main/Packages.new >
/var/cache/rhn/repodata/xenial-main/Packages.gz && touch -r
/var/cache/rhn/repodata/xenial-main/Packages
/var/cache/rhn/repodata/xenial-main/Packages.gz
/etc/rhn/secureApt.sh xenial-main Xenial
-Original Message-
From: Randall R. Sargent
Sent: Thursday, September 27, 2018 8:40 AM
To: 'Robert Paschedag' ; spacewalk-list@redhat.com
Cc: spacewalk-list@redhat.com
Subject: RE: [Spacewalk-list] Ubuntu/Deb Support
The other issue I'm having is the sync script keeps keeps giving me "rhnpush
failed". The first time it was permissions issues for the apache process on
/tmp. I fixed that and got about 75% of the way finished syncing, then it did
it again. Next I tried running it as 'apache' and now I'm getting permission
issues writing to '/usr/share/httpd/.rhnpushcache'.
-Original Message-
From: Robert Paschedag
Sent: Thursday, September 27, 2018 12:07 AM
To: spacewalk-list@redhat.com; Randall R. Sargent
Cc: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Ubuntu/Deb Support
Am 27. September 2018 07:03:19 MESZ schrieb Robert Paschedag
:
>Am 26. September 2018 18:01:16 MESZ schrieb "Randall R. Sargent"
>:
>>Thanks Robert.
>>
>>I applied the patch for rhnRepository.py and verified the client
>>version is up to date using the criteria gave (spacewalk.list). I did
>>follow Phil's blog and have been able to create Release & Release.gpg
>>files. I did not do any of the patching he mentioned though because
>I'm
>>assuming my versions are updated since he wrote the post.
>>
>>Attempting to patch after that gives me the same error.
>>
>>Next I am trying to run your add-multiarch-header script but am
>getting
>>the following error:
>>
>>/etc/rhn/spacewalk-add-debian-multiarch-header.py
>>/var/cache/rhn/repodata/xenial-main/Packages /tmp/xenial-main
>>Error: Inputfile '/tmp/xenial-main' not available.
>>
>>Am I just running your modified script, or do I need to run
>>spacewalk-debian-sync.pl before?
>
>Of course you must sync the repos with the modified sync script (as
>stated). This extracts the Multi-Arch headers from the original Ubuntu
>/ Debian repos and writes them to temporary files within /tmp.
But you should check your repos are signed correctly by running apt-get update.
If this does not work correctly or complains about missing release files, you
made a mistake somewhere.
Robert
>
>Robert
>>
>>Thanks again.
>>
>>-Original Message-
>>From: Robert Paschedag
>>Sent: Wednesday, September 26, 2018 10:10 AM
>>To: Randall R. Sargent
>>Cc: spacewalk-list@redhat.com
>>Subject: Aw: RE: [Spacewalk-list] Ubuntu/Deb Support
>>
>>
>>
>>> Gesendet: Mittwoch, 26. September 2018 um 15:16 Uhr
>>> Von: "Randall R. Sargent"
>>> An: "Robert Paschedag" ,
>>> "spacewalk-list@redhat.com" ,
>>> "spacewalk-list@redhat.com"
>>> Betreff: RE: [Spacewalk-list] Ubuntu/Deb Support
>>>
>>> I'm having no luck getting my xenial clients to recognize the
>Release
>>& Release.gpg files in my repos. I resorted to modifying the
>>pre-invoke.py script to write [trusted=yes] for each line in
>>spacewalk.list, now I'm no longer getting complaints about missing
>>Release files when I do an apt update. I am still unable to upgrade
>any
>>packages though:
>>>
>>> # rhn_check -
>>> D: check_action{'action': ">>
>>version='1.0'?>\n\npackages.update>>
>>>\n\n\n\n\n>>
>>ue>bind9-host\n9.10.3.dfsg.P4<
>>>
>>/string>\n8ubuntu1.11\n
>>>
>>1\namd64-deb\
>>>
>>n\n\n\n
>>> \n\n", 'version': 2, 'id': 26}
>>> updateLoginInfo() login info
>>> D: login(forceUpdate=True) invoked
>>> logging into up2date server
>>> D: rpcServer: Calling XMLRPC up2date.login
>>> D: writeCachedLogin() invoked
>>> D: Wrote pickled loginInfo at 1537966985.67 with expiration of
>>1537970585.67 seconds.
>>> successfully retrieved authentication token from up2date server
>>> D: logininfo:{'X-RHN-Server-Id': 11,
>>'X-RHN-Auth-Server-Time':
>>> '1537966985.69', 'X-RHN-Auth':
>>> '8okffYSJDt+fznMR/PhU4rZCo31NCg9sFe84Gx6oRVo=',
>>'X-RHN-Auth-Channels':
>>> [['xenial-main', '20180925171652', '1', '1'], ['xenial-security',
>>> '20180925175349', '0', '1'], ['xenial-updates', '20180925172643',
[Spacewalk-list] spacewalk::sync rpm and errata
Hi All- I'm new to spacewalk first of all. i have installed spacewalk on one of RH registered system, and my environment consist of underlying centos6/7 and redhat6/7 boxes, can anyone procedure to sync the rpms,update and respective errata associated with it, so that I can apply to underlying machines. I really appreciate, if some one can help me. Thanks Anand vamsi DISCLAIMER: This e-mail message and any attachments are intended solely for the use of the individual or entity to which it is addressed and may contain information that is confidential or legally privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and permanently delete this message and any attachments. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] How to create local repo on Spacewalk
Thanks for your reply. I don’t have a local repo or how can I find it? Regards, Jérôme From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Harshal Lakare Sent: Donnerstag, 27. September 2018 16:17 To: spacewalk-list@redhat.com Subject: [Spacewalk-list] How to create local repo on Spacewalk You can simple run script to add your local repo in kickstart file. Regards, Harshal Lakare smime.p7s Description: S/MIME cryptographic signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] How to create local repo on Spacewalk
You can simple run script to add your local repo in kickstart file. Regards, Harshal Lakare ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] import older errata
Hello, I recently encountered with spacewalk's errata , i noticed or i did not able to find a way to import older errata than 2018. Our internal security scanner has reported CVE than 2018 (once CVE i found from 1990 ) . How do i import those into spacewalk ? Regards, Harshal Lakare ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Ubuntu/Deb Support
The other issue I'm having is the sync script keeps keeps giving me "rhnpush
failed". The first time it was permissions issues for the apache process on
/tmp. I fixed that and got about 75% of the way finished syncing, then it did
it again. Next I tried running it as 'apache' and now I'm getting permission
issues writing to '/usr/share/httpd/.rhnpushcache'.
-Original Message-
From: Robert Paschedag
Sent: Thursday, September 27, 2018 12:07 AM
To: spacewalk-list@redhat.com; Randall R. Sargent
Cc: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Ubuntu/Deb Support
Am 27. September 2018 07:03:19 MESZ schrieb Robert Paschedag
:
>Am 26. September 2018 18:01:16 MESZ schrieb "Randall R. Sargent"
>:
>>Thanks Robert.
>>
>>I applied the patch for rhnRepository.py and verified the client
>>version is up to date using the criteria gave (spacewalk.list). I did
>>follow Phil's blog and have been able to create Release & Release.gpg
>>files. I did not do any of the patching he mentioned though because
>I'm
>>assuming my versions are updated since he wrote the post.
>>
>>Attempting to patch after that gives me the same error.
>>
>>Next I am trying to run your add-multiarch-header script but am
>getting
>>the following error:
>>
>>/etc/rhn/spacewalk-add-debian-multiarch-header.py
>>/var/cache/rhn/repodata/xenial-main/Packages /tmp/xenial-main
>>Error: Inputfile '/tmp/xenial-main' not available.
>>
>>Am I just running your modified script, or do I need to run
>>spacewalk-debian-sync.pl before?
>
>Of course you must sync the repos with the modified sync script (as
>stated). This extracts the Multi-Arch headers from the original Ubuntu
>/ Debian repos and writes them to temporary files within /tmp.
But you should check your repos are signed correctly by running apt-get update.
If this does not work correctly or complains about missing release files, you
made a mistake somewhere.
Robert
>
>Robert
>>
>>Thanks again.
>>
>>-Original Message-
>>From: Robert Paschedag
>>Sent: Wednesday, September 26, 2018 10:10 AM
>>To: Randall R. Sargent
>>Cc: spacewalk-list@redhat.com
>>Subject: Aw: RE: [Spacewalk-list] Ubuntu/Deb Support
>>
>>
>>
>>> Gesendet: Mittwoch, 26. September 2018 um 15:16 Uhr
>>> Von: "Randall R. Sargent"
>>> An: "Robert Paschedag" ,
>>> "spacewalk-list@redhat.com" ,
>>> "spacewalk-list@redhat.com"
>>> Betreff: RE: [Spacewalk-list] Ubuntu/Deb Support
>>>
>>> I'm having no luck getting my xenial clients to recognize the
>Release
>>& Release.gpg files in my repos. I resorted to modifying the
>>pre-invoke.py script to write [trusted=yes] for each line in
>>spacewalk.list, now I'm no longer getting complaints about missing
>>Release files when I do an apt update. I am still unable to upgrade
>any
>>packages though:
>>>
>>> # rhn_check -
>>> D: check_action{'action': ">>
>>version='1.0'?>\n\npackages.update>>
>>>\n\n\n\n\n>>
>>ue>bind9-host\n9.10.3.dfsg.P4<
>>>
>>/string>\n8ubuntu1.11\n
>>>
>>1\namd64-deb\
>>>
>>n\n\n\n
>>> \n\n", 'version': 2, 'id': 26}
>>> updateLoginInfo() login info
>>> D: login(forceUpdate=True) invoked
>>> logging into up2date server
>>> D: rpcServer: Calling XMLRPC up2date.login
>>> D: writeCachedLogin() invoked
>>> D: Wrote pickled loginInfo at 1537966985.67 with expiration of
>>1537970585.67 seconds.
>>> successfully retrieved authentication token from up2date server
>>> D: logininfo:{'X-RHN-Server-Id': 11,
>>'X-RHN-Auth-Server-Time':
>>> '1537966985.69', 'X-RHN-Auth':
>>> '8okffYSJDt+fznMR/PhU4rZCo31NCg9sFe84Gx6oRVo=',
>>'X-RHN-Auth-Channels':
>>> [['xenial-main', '20180925171652', '1', '1'], ['xenial-security',
>>> '20180925175349', '0', '1'], ['xenial-updates', '20180925172643',
>>'0',
>>> '1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset':
>>'3600.0'}
>>> D: handle_action{'action': ">>
>>version='1.0'?>\n\npackages.update>>
>>>\n\n\n\n\n>>
>>ue>bind9-host\n9.10.3.dfsg.P4<
>>>
>>/string>\n8ubuntu1.11\n
>>>
>>1\namd64-deb\
>>>
>>n\n\n\n
>>> \n\n", 'version': 2, 'id': 26}
>>> D: handle_action actionid = 26, version = 2
>>> D: do_call packages.update([['bind9-host', '9.10.3.dfsg.P4',
>>> '8ubuntu1.11', '1', 'amd64-deb']],){'cache_only': None}
>>> D: Called update[['bind9-host', '9.10.3.dfsg.P4', '8ubuntu1.11',
>'1',
>>
>>> 'amd64-deb']]
>>> Apt-Spacewalk: Updating sources.list
>>
>>Error starts here
>>
>>> D: Sending back response(1, 'update failed', {})
>>
>>The python-apt module failes to verify the repos.
>>
>>You said, your are using SW 2.8. Release? If yes, you are missing a
>>patch to support "signed" debian repos. See PR
>>https://github.com/spacewalkproject/spacewalk/pull/636. This is the
>>part you need to patch on the server.
>>
>>You also need to patch the clients. If you installed the newest
>>packages (as stated within this thread), your clients should be ok.
>You
>>can check this within your /etc/apt/sources.list.d/spacewalk file. If
>>this file contains one line for each channel your client subscribes,
Re: [Spacewalk-list] Ubuntu/Deb Support
Thanks Robert. My clients are complaining about the repos being signed with a
weak digest (SHA1), but it doesn't look fatal. I thought I created the gpg keys
with SHA256, but I may need to try again.
-Original Message-
From: Robert Paschedag
Sent: Thursday, September 27, 2018 12:07 AM
To: spacewalk-list@redhat.com; Randall R. Sargent
Cc: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Ubuntu/Deb Support
Am 27. September 2018 07:03:19 MESZ schrieb Robert Paschedag
:
>Am 26. September 2018 18:01:16 MESZ schrieb "Randall R. Sargent"
>:
>>Thanks Robert.
>>
>>I applied the patch for rhnRepository.py and verified the client
>>version is up to date using the criteria gave (spacewalk.list). I did
>>follow Phil's blog and have been able to create Release & Release.gpg
>>files. I did not do any of the patching he mentioned though because
>I'm
>>assuming my versions are updated since he wrote the post.
>>
>>Attempting to patch after that gives me the same error.
>>
>>Next I am trying to run your add-multiarch-header script but am
>getting
>>the following error:
>>
>>/etc/rhn/spacewalk-add-debian-multiarch-header.py
>>/var/cache/rhn/repodata/xenial-main/Packages /tmp/xenial-main
>>Error: Inputfile '/tmp/xenial-main' not available.
>>
>>Am I just running your modified script, or do I need to run
>>spacewalk-debian-sync.pl before?
>
>Of course you must sync the repos with the modified sync script (as
>stated). This extracts the Multi-Arch headers from the original Ubuntu
>/ Debian repos and writes them to temporary files within /tmp.
But you should check your repos are signed correctly by running apt-get update.
If this does not work correctly or complains about missing release files, you
made a mistake somewhere.
Robert
>
>Robert
>>
>>Thanks again.
>>
>>-Original Message-
>>From: Robert Paschedag
>>Sent: Wednesday, September 26, 2018 10:10 AM
>>To: Randall R. Sargent
>>Cc: spacewalk-list@redhat.com
>>Subject: Aw: RE: [Spacewalk-list] Ubuntu/Deb Support
>>
>>
>>
>>> Gesendet: Mittwoch, 26. September 2018 um 15:16 Uhr
>>> Von: "Randall R. Sargent"
>>> An: "Robert Paschedag" ,
>>> "spacewalk-list@redhat.com" ,
>>> "spacewalk-list@redhat.com"
>>> Betreff: RE: [Spacewalk-list] Ubuntu/Deb Support
>>>
>>> I'm having no luck getting my xenial clients to recognize the
>Release
>>& Release.gpg files in my repos. I resorted to modifying the
>>pre-invoke.py script to write [trusted=yes] for each line in
>>spacewalk.list, now I'm no longer getting complaints about missing
>>Release files when I do an apt update. I am still unable to upgrade
>any
>>packages though:
>>>
>>> # rhn_check -
>>> D: check_action{'action': ">>
>>version='1.0'?>\n\npackages.update>>
>>>\n\n\n\n\n>>
>>ue>bind9-host\n9.10.3.dfsg.P4<
>>>
>>/string>\n8ubuntu1.11\n
>>>
>>1\namd64-deb\
>>>
>>n\n\n\n
>>> \n\n", 'version': 2, 'id': 26}
>>> updateLoginInfo() login info
>>> D: login(forceUpdate=True) invoked
>>> logging into up2date server
>>> D: rpcServer: Calling XMLRPC up2date.login
>>> D: writeCachedLogin() invoked
>>> D: Wrote pickled loginInfo at 1537966985.67 with expiration of
>>1537970585.67 seconds.
>>> successfully retrieved authentication token from up2date server
>>> D: logininfo:{'X-RHN-Server-Id': 11,
>>'X-RHN-Auth-Server-Time':
>>> '1537966985.69', 'X-RHN-Auth':
>>> '8okffYSJDt+fznMR/PhU4rZCo31NCg9sFe84Gx6oRVo=',
>>'X-RHN-Auth-Channels':
>>> [['xenial-main', '20180925171652', '1', '1'], ['xenial-security',
>>> '20180925175349', '0', '1'], ['xenial-updates', '20180925172643',
>>'0',
>>> '1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset':
>>'3600.0'}
>>> D: handle_action{'action': ">>
>>version='1.0'?>\n\npackages.update>>
>>>\n\n\n\n\n>>
>>ue>bind9-host\n9.10.3.dfsg.P4<
>>>
>>/string>\n8ubuntu1.11\n
>>>
>>1\namd64-deb\
>>>
>>n\n\n\n
>>> \n\n", 'version': 2, 'id': 26}
>>> D: handle_action actionid = 26, version = 2
>>> D: do_call packages.update([['bind9-host', '9.10.3.dfsg.P4',
>>> '8ubuntu1.11', '1', 'amd64-deb']],){'cache_only': None}
>>> D: Called update[['bind9-host', '9.10.3.dfsg.P4', '8ubuntu1.11',
>'1',
>>
>>> 'amd64-deb']]
>>> Apt-Spacewalk: Updating sources.list
>>
>>Error starts here
>>
>>> D: Sending back response(1, 'update failed', {})
>>
>>The python-apt module failes to verify the repos.
>>
>>You said, your are using SW 2.8. Release? If yes, you are missing a
>>patch to support "signed" debian repos. See PR
>>https://github.com/spacewalkproject/spacewalk/pull/636. This is the
>>part you need to patch on the server.
>>
>>You also need to patch the clients. If you installed the newest
>>packages (as stated within this thread), your clients should be ok.
>You
>>can check this within your /etc/apt/sources.list.d/spacewalk file. If
>>this file contains one line for each channel your client subscribes,
>>you are fine.
>>
>>Now you still need to create the "InRelease" or "Release.gpg" files.
>>@Phil has written in his blog years ago. See
>>http://www.devops-bl
[Spacewalk-list] How to create local repo on Spacewalk
Hi Team, Here's a newbie question: How can I define a local repository on Spacewalk server for our client's kickstart file? Actually it is redirected to external link. Our spacewalk have a base-centos7 channel who is linked to the software channel base-centos7. This software channel is connected to some repositories, all from extern links. (External - centos7, etc...). I need to have a local repository which will be updated and also used for kickstart. Should I use the same principle as CentOS, namely createrepo, etc... ? I did some research and unfortunately I didn't find something useful... Could anyone give me some advice or useful links? Thanks for your help, Regards, Jérôme smime.p7s Description: S/MIME cryptographic signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] ERROR: can't read "the_log_id": no such variable
Hello all, When I link spacewalk to a external standalone postgresql db everything is running fine. When we change to production I get this error. In production we have a postgresql cluster running with streaming replication and pgpool2. Does anybody have experience with this behaviour? 2018-09-27 12:43:51.550 CEST [6184] spaceuser@spacedb ERROR: can't read "the_log_id": no such variable 2018-09-27 12:43:51.550 CEST [6184] spaceuser@spacedb CONTEXT: can't read "the_log_id": no such variable while executing "return $the_log_id" (procedure "__PLTcl_proc_22794" line 4) invoked from within "__PLTcl_proc_22794" in PL/Tcl function "_get_log_id" PL/pgSQL function get_log_id() line 7 at assignment PL/pgSQL function rhnserver_log_trig_fun() line 5 at assignment 2018-09-27 12:43:51.550 CEST [6184] spaceuser@spacedb STATEMENT: update rhnServer set last_boot = 1538032759.55119 where id = 110036 Kind regards, Tom Degroote ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] Yum shows updates available but Spacewalk does not
Hello all,
On the GUI, all the systems of one of our organization report that there is
no update available and that they are up to date, but "yum update" on the
same servers report updates are available.
We tried running rhn-profile-sync on some of the servers (output below),
but the result is the same : the GUI still shows no update whereas 'yum
update' does.
The packages proposed by yum all come from Spacewalk channels, and not from
the classic yum repositories.
[root@server ~]# rhn-profile-sync -
updateLoginInfo() login info
D: login(forceUpdate=True) invoked
D: opening db environment /var/lib/rpm cdb:mpool:joinenv
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: locked db index /var/lib/rpm/Packages
D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
D: loading keyring from rpmdb
D: opening db index /var/lib/rpm/Name rdonly mode=0x0
D: added key gpg-pubkey-ab913528-4ec7933a to keyring
D: added key gpg-pubkey-c105b9de-4e0fd3a3 to keyring
D: added key gpg-pubkey-ee907298-4f212424 to keyring
D: added key gpg-pubkey-66fd4949-4803fe57 to keyring
D: added key gpg-pubkey-0608b895-4bd22942 to keyring
D: added key gpg-pubkey-772cfdff-4ec79366 to keyring
D: added key gpg-pubkey-3903421e-4f217f8b to keyring
D: added key gpg-pubkey-bcce5563-4fad226c to keyring
D: added key gpg-pubkey-863a853d-4f55f54d to keyring
D: added key gpg-pubkey-b3892132-4c63febc to keyring
D: added key gpg-pubkey-430a1c35-48515c2a to keyring
D: added key gpg-pubkey-741ef998-4f7eefdc to keyring
D: added key gpg-pubkey-d180f94d-4f327fe4 to keyring
D: added key gpg-pubkey-066e5810-53cfcd27 to keyring
D: added key gpg-pubkey-b8002de1-553126bd to keyring
D: added key gpg-pubkey-a7a1d4b6-43281558 to keyring
D: added key gpg-pubkey-4cf7c514-4b2b473d to keyring
D: added key gpg-pubkey-e00b8985-512dde96 to keyring
D: added key gpg-pubkey-2833155f-4f83fca5 to keyring
D: added key gpg-pubkey-7bd9bf62-4e4e3262 to keyring
D: added key gpg-pubkey-bdc414dd-4eeb495f to keyring
D: added key gpg-pubkey-84017165-528b36ab to keyring
D: added key gpg-pubkey-f21541eb-4a5233e7 to keyring
D: added key gpg-pubkey-db42a60e-37ea5438 to keyring
D: added key gpg-pubkey-37017186-45761324 to keyring
D: added key gpg-pubkey-42193e6b-4624eff2 to keyring
D: added key gpg-pubkey-fd431d51-4ae0493b to keyring
D: added key gpg-pubkey-5bb941bb-552fe38f to keyring
D: added key gpg-pubkey-223d08ff-4f33840c to keyring
D: added key gpg-pubkey-4a97d041-52527935 to keyring
D: added key gpg-pubkey-9cd4953f-4a9da118 to keyring
D: added key gpg-pubkey-00f97f56-467e318a to keyring
D: added key gpg-pubkey-c4deffeb-4c872f3a to keyring
D: added key gpg-pubkey-f2ee9d55-560cfc0a to keyring
D: added key gpg-pubkey-96dd1df9-57832bc5 to keyring
D: added key gpg-pubkey-b1275ea3-546d1808 to keyring
D: added key gpg-pubkey-26c2b797-5669d0b9 to keyring
D: added key gpg-pubkey-d88e42b4-52371eca to keyring
D: added key gpg-pubkey-07513cad-4fe4cf94 to keyring
D: Using legacy gpg-pubkey(s) from rpmdb
D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
logging into up2date server
D: rpcServer: Calling XMLRPC up2date.login
D: writeCachedLogin() invoked
D: Wrote pickled loginInfo at 1537976706.73 with expiration of
1537980306.73 seconds.
successfully retrieved authentication token from up2date server
D: logininfo:{'X-RHN-Server-Id': 113028, 'X-RHN-Auth-Server-Time':
'1537976706.73', 'X-RHN-Auth':
'lQaS+miHHi4EFmosXUf1lDZ39KempjGSLMX1ZbvgXDA=', 'X-RHN-Auth-Channels':
[['cha-centos-6-x86_64', '20170919084117', '1', '1'],
['cha-centos-6server-x86_64-20180901', '20180901070305', '0', '1'],
['cha-centos-6-x86_64-epel-20180901', '20180901070304', '0', '1'],
['cha-centos-6-x86_64-inner-20180901', '20180901070304', '0', '1'],
['cha-centos-6-x86_64-checktools-20180901', '20180901070304', '0', '1'],
['cha-centos-6-x86_64-acacia-20180901', '20180901070303', '0', '1'],
['cha-centos-6-x86_64-vmware_5_5-20180901', '20180901070305', '0', '1'],
['cha-centos-6-x86_64-spacewalk_client-20180901', '20180901070305', '0',
'1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'}
Updating package profile...
Updating package profile
D: rpcServer: Calling XMLRPC registration.welcome_message
D: rpcServer: Calling XMLRPC registration.update_packages
Updating hardware profile...
D: rpcServer: Calling XMLRPC registration.welcome_message
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Name
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm
Can anyone help me with this issue ?
Thanks in advance for your replies.
Regards, Florence
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
