from:"Randall R. Sargent"

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-28 Thread Randall R. Sargent

Ok, I commented out the default sources.list and inserted the SW repos from my 
spacewalk.list - this time I was able to install a package manually from SW 
*and also able to rhn_check and upgrade packages.* So I'm confused.

What's interesting is SW was reporting 17 packages that could be upgraded, 
however apt list --upgradable showed over 400 packages. I applied the 17 
package updates via SW and now it shows 0 updates for that client, but on the 
client apt list --upgradable shows 400. I manually ran apt upgrade and it ran 
successfully, but still shows those updates are needed. SW says no updates are 
available.

Help?

-Original Message-
From: Randall R. Sargent 
Sent: Friday, September 28, 2018 11:35 AM
To: 'Robert Paschedag' ; spacewalk-list@redhat.com
Subject: RE: [Spacewalk-list] Ubuntu/Deb Support

I'm an idiot. Yes, that worked, but it looks like it's getting it from the 
ubuntu repos instead of Spacewalk:

# apt install bind9-host
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  dnsutils libbind9-140 libdns162 libisc160 libisccfg140 liblwres141 Suggested 
packages:
  rblcheck
The following packages will be upgraded:
  bind9-host dnsutils libbind9-140 libdns162 libisc160 libisccfg140 liblwres141
7 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
Need to get 1,321 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 bind9-host 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [38.4 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 dnsutils 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [89.2 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libisc160 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [215 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdns162 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [881 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccfg140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [40.4 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 liblwres141 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [33.7 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libbind9-140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [23.6 kB] Fetched 1,321 kB in 
0s (1,712 kB/s) (Reading database ... 71960 files and directories currently 
installed.) Preparing to unpack 
.../bind9-host_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../dnsutils_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libisc160_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libdns162_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libisccfg140_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb 
...
Unpacking libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../liblwres141_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libbind9-140_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb 
...
Unpacking libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Apt-Spacewalk: Updating package profile



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

Am 28. September 2018 18:06:58 MESZ schrieb "Randall R. Sargent" 
:
>Trying to install 'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb' - 
>which also shows as an available upgrade package in SW:
>
># apt install bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>E: Unable to locate

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-28 Thread Randall R. Sargent

I'm an idiot. Yes, that worked, but it looks like it's getting it from the 
ubuntu repos instead of Spacewalk:

# apt install bind9-host
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  dnsutils libbind9-140 libdns162 libisc160 libisccfg140 liblwres141
Suggested packages:
  rblcheck
The following packages will be upgraded:
  bind9-host dnsutils libbind9-140 libdns162 libisc160 libisccfg140 liblwres141
7 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
Need to get 1,321 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 bind9-host 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [38.4 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 dnsutils 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [89.2 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libisc160 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [215 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdns162 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [881 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccfg140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [40.4 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 liblwres141 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [33.7 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libbind9-140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.11 [23.6 kB]
Fetched 1,321 kB in 0s (1,712 kB/s)
(Reading database ... 71960 files and directories currently installed.)
Preparing to unpack .../bind9-host_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../dnsutils_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libisc160_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libdns162_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libisccfg140_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb 
...
Unpacking libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../liblwres141_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb ...
Unpacking liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Preparing to unpack .../libbind9-140_1%3a9.10.3.dfsg.P4-8ubuntu1.11_amd64.deb 
...
Unpacking libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) over 
(1:9.10.3.dfsg.P4-8ubuntu1.10) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Setting up dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.11) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Apt-Spacewalk: Updating package profile



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

Am 28. September 2018 18:06:58 MESZ schrieb "Randall R. Sargent" 
:
>Trying to install 'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb' - 
>which also shows as an available upgrade package in SW:
>
># apt install bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>E: Unable to locate package
>bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb
>E: Couldn't find any package by glob
>'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb'
>E: Couldn't find any package by regex
>'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb'

apt-get install bind9-host


>
>-Original Message-
>From: Robert Paschedag 
>Sent: Friday, September 28, 2018 10:25 AM
>To: Randall R. Sargent ; 
>spacewalk-list@redhat.com
>Subject: RE: [Spacewalk-list] Ubuntu/Deb Support
>
>Am 28. September 2018 16:23:42 MESZ schrieb "Randall R. Sargent"
>:
>>I'm finding two cache.py files. Which am I debugging?
>>
>>/usr/lib/python2.7/dist-packages/apt/cache.py
>>
>>/usr/lib/python3/dist-packages/apt/cache.py
>
>That depends on your default version of

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-28 Thread Randall R. Sargent

Also, performing an apt update looks normal to me:

# apt update
Apt-Spacewalk: Updating sources.list
Ign:1 cdrom://Ubuntu-Server 16.04.5 LTS _Xenial Xerus_ - Release amd64 
(20180731) xenial InRelease
Err:2 cdrom://Ubuntu-Server 16.04.5 LTS _Xenial Xerus_ - Release amd64 
(20180731) xenial Release
  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update 
cannot be used to add new CD-ROMs
Ign:3 spacewalk://spacewalk.pilotcat.com xenial-main InRelease
Ign:4 spacewalk://spacewalk.pilotcat.com xenial-security InRelease
Ign:5 spacewalk://spacewalk.pilotcat.com xenial-updates InRelease
Get:6 spacewalk://spacewalk.pilotcat.com xenial-main Release [929 B]
Get:7 spacewalk://spacewalk.pilotcat.com xenial-security Release [929 B]
Get:8 spacewalk://spacewalk.pilotcat.com xenial-updates Release [932 B]
Hit:9 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:12 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:14 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
Ign:15 
http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8:/debclients/xUbuntu_16.04
  InRelease
Hit:16 
http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8:/debclients/xUbuntu_16.04
  Release
Get:17 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Reading package lists... Done
E: The repository 'cdrom://Ubuntu-Server 16.04.5 LTS _Xenial Xerus_ - Release 
amd64 (20180731) xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.

-Original Message-
From: Robert Paschedag  
Sent: Friday, September 28, 2018 10:25 AM
To: Randall R. Sargent ; spacewalk-list@redhat.com
Subject: RE: [Spacewalk-list] Ubuntu/Deb Support

Am 28. September 2018 16:23:42 MESZ schrieb "Randall R. Sargent" 
:
>I'm finding two cache.py files. Which am I debugging?
>
>/usr/lib/python2.7/dist-packages/apt/cache.py
>
>/usr/lib/python3/dist-packages/apt/cache.py

That depends on your default version of Python and the shebang line within 
"rhn_check"

But if apt-get update does not complain anymore, the update should work... Or 
say, the cache update should not be the problem anymore.

What if you try to install the package manually via apt-get install??

Robert
>
>Yes, no SHA1 errors. I re-did the key with SHA256.
>
>-Original Message-
>From: Robert Paschedag 
>Sent: Friday, September 28, 2018 12:11 AM
>To: Randall R. Sargent ; 
>spacewalk-list@redhat.com
>Subject: 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-amd
>>6 4/ --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.

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-28 Thread Randall R. Sargent

Trying to install 'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb' - which 
also shows as an available upgrade package in SW:

# apt install bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb
E: Couldn't find any package by glob 
'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb'
E: Couldn't find any package by regex 
'bind9-host-9.10.3.dfsg.P4-8ubuntu1.11:1.amd64-deb'

-Original Message-
From: Robert Paschedag  
Sent: Friday, September 28, 2018 10:25 AM
To: Randall R. Sargent ; spacewalk-list@redhat.com
Subject: RE: [Spacewalk-list] Ubuntu/Deb Support

Am 28. September 2018 16:23:42 MESZ schrieb "Randall R. Sargent" 
:
>I'm finding two cache.py files. Which am I debugging?
>
>/usr/lib/python2.7/dist-packages/apt/cache.py
>
>/usr/lib/python3/dist-packages/apt/cache.py

That depends on your default version of Python and the shebang line within 
"rhn_check"

But if apt-get update does not complain anymore, the update should work... Or 
say, the cache update should not be the problem anymore.

What if you try to install the package manually via apt-get install??

Robert
>
>Yes, no SHA1 errors. I re-did the key with SHA256.
>
>-Original Message-
>From: Robert Paschedag 
>Sent: Friday, September 28, 2018 12:11 AM
>To: Randall R. Sargent ; 
>spacewalk-list@redhat.com
>Subject: 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-amd
>>6 4/ --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 (space

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-28 Thread Randall R. Sargent

I'm finding two cache.py files. Which am I debugging?

/usr/lib/python2.7/dist-packages/apt/cache.py

/usr/lib/python3/dist-packages/apt/cache.py

Yes, no SHA1 errors. I re-did the key with SHA256.

-Original Message-
From: Robert Paschedag  
Sent: Friday, September 28, 2018 12:11 AM
To: Randall R. Sargent ; spacewalk-list@redhat.com
Subject: 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-amd6
>4/ --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

Re: [Spacewalk-list] Ubuntu/Deb Support

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

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 se

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-27 Thread Randall R. Sargent

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

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-27 Thread Randall R. Sargent

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']]
>>

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.
-

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_

[Spacewalk-list] Debian Signed Repos

2018-09-25 Thread Randall R. Sargent

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.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-24 Thread Randall R. Sargent

Robert – Your comment on the repo not being signed sounds like the issue. Do I 
assign a gpg key to the Channel, or do I assign a cert to the repo?

*I’m seeing messages in the archive long before I get the email.

From: Randall R. Sargent
Sent: Monday, September 24, 2018 2:08 PM
To: spacewalk-list@redhat.com
Subject: RE: [Spacewalk-list] Ubuntu/Deb Support

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@01D45418.9F063740]

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Neal Gompa
Sent: Monday, September 24, 2018 12:49 PM
To: spacewalk-list@redhat.com<mailto: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 rhn-check rhn-setup rhnsd 
apt-transport-spacewalk rhncfg rhncfg-actions

There are builds for xUbuntu 16.04 and 18.04, as well as Debian 8.0 and 9.0. 
Just swap "xUbuntu_16.04" in the instructions above for "xUbuntu_18.04" or 
"Debian_8.0" or "Debian_9.0".

Future development of the clients are going into Spacewalk's next release.

--
真実はいつも一つ！/ Always, there's only one truth!
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-24 Thread 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]

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 rhn-check rhn-setup rhnsd 
apt-transport-spacewalk rhncfg rhncfg-actions

There are builds for xUbuntu 16.04 and 18.04, as well as Debian 8.0 and 9.0. 
Just swap "xUbuntu_16.04" in the instructions above for "xUbuntu_18.04" or 
"Debian_8.0" or "Debian_9.0".

Future development of the clients are going into Spacewalk's next release.

--
真実はいつも一つ！/ Always, there's only one truth!
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Ubuntu/Deb Support

2018-09-24 Thread Randall R. Sargent

16.04 registers, but any package installation or upgrade fails. Console on the 
client after doing a rhn_check doesn’t show an error, but the event history on 
SW just says the client reported it failed.

On Sep 24, 2018, at 12:26 PM, Andrei Popenta 
mailto:andrei.pope...@visma.com>> wrote:

Hi,

I've got Ubuntu 16.04 and 18.04 working in SW 2.7.
what's your issue with ubuntu 16.04 ?

Andrei

On Mon, 24 Sep 2018 at 17:59, 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!


Randy Sargent
Sr. Systems Administrator | Technology Services
[cid:image001.png@01D3D32B.1D990B60]<https://www.pilotcat.com/>
Office (251) 634-3312 | Fax (888) 217-4567

This e-mail and its attachments are subject to the Electronic Communications 
Privacy Act, 18 USC 2510-2521 and intended solely for the intended addressee. 
If you are not the intended recipient, stop reading this message and delete it 
from your system. Unauthorized retaining, reading, distribution, copying, or 
other use is strictly prohibited.

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

[Spacewalk-list] Ubuntu/Deb Support

2018-09-24 Thread Randall R. Sargent

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!


Randy Sargent
Sr. Systems Administrator | Technology Services
[cid:image001.png@01D3D32B.1D990B60]
Office (251) 634-3312 | Fax (888) 217-4567

This e-mail and its attachments are subject to the Electronic Communications 
Privacy Act, 18 USC 2510-2521 and intended solely for the intended addressee. 
If you are not the intended recipient, stop reading this message and delete it 
from your system. Unauthorized retaining, reading, distribution, copying, or 
other use is strictly prohibited.

___
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] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

[Spacewalk-list] Debian Signed Repos

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

Re: [Spacewalk-list] Ubuntu/Deb Support

[Spacewalk-list] Ubuntu/Deb Support

15 matches

Site Navigation

Mail list logo

Footer information