date:20180926

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-26 Thread Robert Paschedag

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-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk
>>
>>You need to create these files for each repo, of course.
>>
>>But even if this all works, you might still hit another bug with newer
>>Ubuntu / Debian distros using newer APT version, which got some
>>"improvements".
>>The error you might hit is the missing "Multi-Arch" header missing
>>within the repo meta data for each channel.
>>
>>So.what I currently do (on my SW 2.7)

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-26 Thread 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.

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-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk
>
>You need to create these files for each repo, of course.
>
>But even if this all works, you might still hit another bug with newer
>Ubuntu / Debian distros using newer APT version, which got some
>"improvements".
>The error you might hit is the missing "Multi-Arch" header missing
>within the repo meta data for each channel.
>
>So.what I currently do (on my SW 2.7) system is.
>
>- Use the "old" sync script from Steve Meier in a modified version.
>(see my repo
>https://github.com/rpasche/spacewalk-debian-sync/tree/add-multiarch-header)
>- wait some minutes after the sync finshed to let SW recreate the
>"packages.gz" for each channel (here, the "Multi-Arch" headers are
>missing)
>- now run my spacewalk-add-debian-multiarch-header script to add the
>missing

Re: [Spacewalk-list] Spacewalk-list Digest, Vol 124, Issue 31

2018-09-26 Thread Paul-Andre Panon

On Tue, 25 Sep 2018 16:21:22, "Randall R. Sargent"
 wrote:
>Branching this off to separate question.

>I'm trying to sign my Spacewalk repos for Deb/Ubuntu. Man apt-secure says
I need to set up a top-level release file first. >Is that your experience,
those who have signed repos? My SW server is on CentOS, so installing
apt-ftparchive doesn't >seem to be an option. I have used the secureApt.sh
script to create Release & Release.gpg files for my repos, however >my
clients are still reporting now release file for the repo. Not sure what
I'm missing.

There's a patch for rhnRepository.py that you need to apply so that the
server will offer Release, Release.gpg, (and InRelease if you use the
script variant to create that as well).
https://bugzilla.redhat.com/show_bug.cgi?id=1198723
Use the corrected rhnRepository.py changes in the comments, not the patch
attachment.

Cheers,

Paul-Andre Panon

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-26 Thread 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? 

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-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk

You need to create these files for each repo, of course.

But even if this all works, you might still hit another bug with newer Ubuntu / 
Debian distros using newer APT version, which got some "improvements".
The error you might hit is the missing "Multi-Arch" header missing within the 
repo meta data for each channel.

So.what I currently do (on my SW 2.7) system is.

- Use the "old" sync script from Steve Meier in a modified version. (see my 
repo https://github.com/rpasche/spacewalk-debian-sync/tree/add-multiarch-header)
- wait some minutes after the sync finshed to let SW recreate the "packages.gz" 
for each channel (here, the "Multi-Arch" headers are missing)
- now run my spacewalk-add-debian-multiarch-header script to add the missing 
headers to the packages.gz for each Debian channel I synced before.
- now sign the repos

Now, if all went well, clients have been patched (apt-spacewalk), server has 
been patched (rhnRepository.py - see PR 636), your clients should work.

Robert

> D: do_call packages.checkNeedUpdate('rhnsd=1',){}
> D: Called refresh_list
> Updating package profile
> D: rpcServer: Calling XMLRPC

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-26 Thread Robert Paschedag



> 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\nbind9-host\n9.10.3.dfsg.P4\n8ubuntu1.11\n1\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\nbind9-host\n9.10.3.dfsg.P4\n8ubuntu1.11\n1\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-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk

You need to create these files for each repo, of course.

But even if this all works, you might still hit another bug with newer Ubuntu / 
Debian distros using newer APT version, which got some "improvements".
The error you might hit is the missing "Multi-Arch" header missing within the 
repo meta data for each channel.

So.what I currently do (on my SW 2.7) system is.

- Use the "old" sync script from Steve Meier in a modified version. (see my 
repo https://github.com/rpasche/spacewalk-debian-sync/tree/add-multiarch-header)
- wait some minutes after the sync finshed to let SW recreate the "packages.gz" 
for each channel (here, the "Multi-Arch" headers are missing)
- now run my spacewalk-add-debian-multiarch-header script to add the missing 
headers to the packages.gz for each Debian channel I synced before.
- now sign the repos

Now, if all went well, clients have been patched (apt-spacewalk), server has 
been patched (rhnRepository.py - see PR 636), your clients should work.

Robert

> D: do_call packages.checkNeedUpdate('rhnsd=1',){}
> D: Called refresh_list
> Updating package profile
> D: rpcServer: Calling XMLRPC registration.welcome_message
> D: rpcServer: Calling XMLRPC registration.update_packages
> D: local action status: (0, 'package list refreshed', {})
> D: rpcServer: Calling XMLRPC registration.welcome_message
> 
> Does anyone have any ideas?
> 
> 
> 
> -Original Message-
> From: Robert Paschedag  
> Sent: Monday, September 24, 2018 2:28 PM
> To: spacewalk-list@redhat.com; Randall R. Sargent ; 
> spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] Ubuntu/Deb Support
> 
> Am 24. September 2018 21:07:58 MESZ schrieb "Randall R. Sargent" 
> :
> >Thanks much for this. I’m not seeing any difference in the behavior of 
> >my 16.04 clients. They are able to register, but doing a package update 
> >fails (any package):
> >
> >[cid:image001.png@01D4540F.FE7E7510]
> >
> 
> I'm pretty sure, you are not using signs repos.
> 
> Newer "apt", especially the python "apt" module fails while checking the 
> signatures of the repo, thus the "update" fails.
> 
> Note: it is the update ("apt-get update") within the call to install the

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-26 Thread Randall R. Sargent

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': "\n\npackages.update\n\n\n\n\nbind9-host\n9.10.3.dfsg.P4\n8ubuntu1.11\n1\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': "\n\npackages.update\n\n\n\n\nbind9-host\n9.10.3.dfsg.P4\n8ubuntu1.11\n1\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
D: Sending back response(1, 'update failed', {})
D: do_call packages.checkNeedUpdate('rhnsd=1',){}
D: Called refresh_list
Updating package profile
D: rpcServer: Calling XMLRPC registration.welcome_message
D: rpcServer: Calling XMLRPC registration.update_packages
D: local action status: (0, 'package list refreshed', {})
D: rpcServer: Calling XMLRPC registration.welcome_message

Does anyone have any ideas?



-Original Message-
From: Robert Paschedag  
Sent: Monday, September 24, 2018 2:28 PM
To: spacewalk-list@redhat.com; Randall R. Sargent ; 
spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Ubuntu/Deb Support

Am 24. September 2018 21:07:58 MESZ schrieb "Randall R. Sargent" 
:
>Thanks much for this. I’m not seeing any difference in the behavior of 
>my 16.04 clients. They are able to register, but doing a package update 
>fails (any package):
>
>[cid:image001.png@01D4540F.FE7E7510]
>

I'm pretty sure, you are not using signs repos.

Newer "apt", especially the python "apt" module fails while checking the 
signatures of the repo, thus the "update" fails.

Note: it is the update ("apt-get update") within the call to install the 
package that fails.

I also had this error with Debian 9, because I did not yet "sign" my repos and 
used "Allow unsigned = true" within apt.conf.

But these settings seem to be ignored, hence, the "apt" python module 
"requires" the repos to be signed. It took me a while to debug this.

In case you "are" using signs repos, you should provide some more info...e.g. 
"rhn_check -" while trying to install a package via SW.

Robert

>From: spacewalk-list-boun...@redhat.com 
> On Behalf Of Neal Gompa
>Sent: Monday, September 24, 2018 12:49 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] Ubuntu/Deb Support
>
>On Mon, Sep 24, 2018 at 10:59 AM Randall R. Sargent 
>mailto:rrsarg...@pilotcat.com>> wrote:
>Hi all,
>
>*Newbie* to Spacewalk here. At the risk of beating a dead horse, has 
>anyone been able to successfully manage Ubuntu clients on 2.8? We have
>14.04 & 16.04 clients and it would make my life so much easier if I 
>could get them to reliably work. I have been able to get 14.04 to 
>register, and even update (with minor issues), but not 16.x.
>Documentation is spotty out there in Google-land.
>
>Any help is appreciated!
>
>
>Hey, yeah, it's possible to successfully manage Ubuntu clients with 
>Spacewalk 2.8.
>
>A couple of months ago, my colleague and I fixed the clients to work in 
>Spacewalk git master (upcoming Spacewalk 2.9), and we backported this 
>to the 2.8 clients.
>
>The sources are here:
>https://gitlab.com/datto/engineering/spacewalk-debian-client-packages
>
>We also built the packages and published them on OBS. You can use them 
>by doing the following:
>
># If you have older clients from Debian/Ubuntu repos $ sudo apt purge 
>apt-transport-spacewalk rhnsd $ sudo apt autoremove # Installing the 
>new packages $ sudo bash -c 'echo "deb 
>http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:
>/2.8:/debclients/xUbuntu_16.04/ /" > 
>/etc/apt/sources.list.d/spacewalk2.8-debclients.list'
>$ sudo apt-key adv --fetch-keys
>http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:
>/2.8:/debclients/xUbuntu_16.04/Release.key
>$ sudo apt-get update
>$ sudo apt install rhn-client-tools

Re: [Spacewalk-list] spacewalk-setup --external-postgresql on external RDS instance FAILS

2018-09-26 Thread Robert Paschedag

Am 26. September 2018 03:50:30 MESZ schrieb Jason Hunt :
>When I run spacewalk-setup --external-postgresql I am receiving the
>below
>error and with the details being thin, not sure what the potential
>issue is;
>
># spacewalk-setup --external-postgresql
>* Setting up SELinux..
>** Database: Setting up database connection for PostgreSQL backend.
>Hostname (leave empty for local)? my.remote.database
>Port [5432]?
>Database [spacewalk]?
>Username [myuser]?
>Password [**]?
>** Database: Populating database.
>*** Progress: #
>Could not populate database.
>
>/var/log/rhn/populate_db.log  and rhn_installation.log contain the
>following;
>
># cat populate_db.log
>*psql:/etc/sysconfig/rhn/postgres/deploy.sql:4: ERROR:  extension
>"dblink"
>already exists*

Although this should not bail out (or checked by the script)... What, if you 
comment the line with the activation of dblink and try again?

Robert

>
># cat rhn_installation.log
>Installation log of Spacewalk
>Command: /bin/spacewalk-setup
>Running /usr/sbin/spacewalk-selinux-enable
>Running /usr/sbin/osa-dispatcher-selinux-enable
>
>I can utilize psql to connect and verify database;
>psql -h my.remote.database -U myuser -W -d spacewalk
>
>Password for user satellite_app:
>psql (9.2.24, server 9.6.8)
>WARNING: psql version 9.2, server version 9.6.
> Some psql features might not work.
>SSL connection (cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256)
>Type "help" for help.
>
>spacewalk=> \l
>  List of databases
>   Name|  Owner   | Encoding |   Collate   |Ctype|   Access
>privileges
>spacewalk | master   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>
>
>Anyone have any ideas?  Thanks in advance for the help.


-- 
sent from my mobile device

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Accessing spacewalk software/packages issue

2018-09-26 Thread Andreas Dijkman

Have you looked at the following page?

https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients

Those URL’s are recently retired so you need the fedora copr ones:
https://copr-be.cloud.fedoraproject.org/archive/spacewalk/2.7-client/ 

https://copr-be.cloud.fedoraproject.org/archive/spacewalk/2.7/ 

https://copr-be.cloud.fedoraproject.org/archive/spacewalk/2.6-client/ 

https://copr-be.cloud.fedoraproject.org/archive/spacewalk/2.6/ 


Andreas Dijkman


> On 25 Sep 2018, at 23:48, Yakin, Francis  wrote:
> 
>  
> I am having issue(403 – forbidden error) to install spacewalk client.tried to 
> install spacewalk  2.7 client on  centOS 2.6
>  
> rpm -Uvh 
> http://yum.spacewalkproject.org/2.7-client/RHEL/6/x86_64/spacewalk-client-repo-2.7-2.el6.noarch.rpm
>  
> 
> Retrieving 
> http://yum.spacewalkproject.org/2.7-client/RHEL/6/x86_64/spacewalk-client-repo-2.7-2.el6.noarch.rpm
>  
> 
> curl: (22) The requested URL returned error: 403 Forbidden
> error: skipping 
> http://yum.spacewalkproject.org/2.7-client/RHEL/6/x86_64/spacewalk-client-repo-2.7-2.el6.noarch.rpm
>  
> 
>  - transfer failed
>  
>  
>  
> Francis Yakin | IT System Admin |  direct: 510-749-2027
> 500 Wind River Way, Alameda, CA  94501
>     
>  
>  
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com 
> https://www.redhat.com/mailman/listinfo/spacewalk-list 
> 


smime.p7s
Description: S/MIME cryptographic signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Spacewalk-list Digest, Vol 124, Issue 31

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] spacewalk-setup --external-postgresql on external RDS instance FAILS

Re: [Spacewalk-list] Accessing spacewalk software/packages issue

8 matches

Site Navigation

Mail list logo

Footer information