[Spacewalk-list] spacewalk 2.10 && debian support
Hello, I just had upgraded one of spacewalk servers from 2.8 to 2.10. I have removed debian channels bustr-main && buster-security. I have resync the channels and after sync was completed I created the Release and Release.gpg files. However, now EVERY time the debian client tries to perform an "apt update" getting this on the server: INFO | jvm 1 | 2020/04/07 13:37:00 | 2020-04-07 13:37:00,204 [Thread-48661] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - File Modified Date:2020-04-07 13:24:31 CEST INFO | jvm 1 | 2020/04/07 13:37:00 | 2020-04-07 13:37:00,204 [Thread-48661] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Channel Modified Date:2020-04-07 01:24:49 CEST INFO | jvm 1 | 2020/04/07 13:37:00 | 2020-04-07 13:37:00,205 [Thread-48662] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - File Modified Date:2020-04-07 13:27:15 CEST INFO | jvm 1 | 2020/04/07 13:37:00 | 2020-04-07 13:37:00,205 [Thread-48662] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Channel Modified Date:2020-04-07 00:38:23 CEST INFO | jvm 1 | 2020/04/07 13:37:00 | 2020-04-07 13:37:00,256 [Thread-48661] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new DEB repository for channel buster-security INFO | jvm 1 | 2020/04/07 13:37:00 | 2020-04-07 13:37:00,262 [Thread-48662] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new DEB repository for channel buster-main ..and the client fails to sync (server keeps regenerating Package file) This didn't happen on SPW 2.8. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] Subject: spacewalk - monitoring processes
Hello, This is more like a question directly for RH support :) We're about to monitor our spacewalk server by HP OMI and we'd need following info: 1. what processes are critical for spacewalk functionality. ( postgresql is running on a different server ) ? 2. minimum number for each process: eh ( httpd => min 2 processes, jabber => min 3 processes, and so on) signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.9 && never ending issue with ubuntu/debian clients
On 2019-02-22 22:30, Robert Paschedag wrote: > On 2/22/19 7:53 PM, Robert Paschedag wrote: Am 22. Februar 2019 13:11:00 MEZ > schrieb Florin Portase : On 2019-02-13 10:56, > Florin Portase wrote: > > Hello, > > I just have upgraded the spacewalk server from 2.7 => 2.9. > > I have applied also the sql patch from > https://bugzilla.redhat.com/show_bug.cgi?id=1661347 > + upgraded the clients from : > > http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.9:/debclients/ > > Just to mention spacewalk 2.7 + patches was working just fine for both > debian & ubuntu. > Now, for ubuntu 16.05 I have over 100 packages marked as up-gradable( over > and over) > ___ > > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list > So, after digging through SPW archive Dec '18 til Feb '19 finally I > come to something more acceptable: > > 1. sync script for Ubuntu channels > > 2. "spacewalk-add-debian-multiarch-header.py.NEW " took it from > "https://www.redhat.com/archives/spacewalk-list/2018-December/msg00017.html; > > wget -q > http://de.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages.gz > \ > -O /tmp/Packages-xenial-main.gz && gunzip -f > /tmp/Packages-xenial-main.gz > wget -q > http://cz.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages.gz > \ > -O /tmp/Packages-xenial-updates.gz && gunzip -f > /tmp/Packages-xenial-updates.gz > wget -q > http://cz.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages.gz > \ > -O /tmp/Packages-xenial-security.gz && gunzip -f > /tmp/Packages-xenial-security.gz > > s=180 > trap 'echo "Ctrl-C detected."' 2 > for (( i=$s ; i>0; i--)); > do > #printf '\rFinishing sync in: %2d seconds' $i; sleep 1 > echo -ne "\rFinishing sync in: $i seconds\033[0K"; > sleep 1 > done > echo -e "\nSync completed!" > trap 2 > $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW > $_PKG_MAIN/Packages/tmp/Packages-xenial-main > $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW > $_PKG_UPD/Packages /tmp/Packages-xenial-updates > $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW > $_PKG_SEC/Packages /tmp/Packages-xenial-security > $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW > $_PKG_UNIV/Packages/tmp/Packages-xenial-universe Below is your error Packages.new is the "modified" Packages which you rename and *afterwards* use its "modified" timestamp. This is wrong. You have to use the "modified" timestamp of the "original" (the one generated by Spacewalk) packages file So when you have the original "Packages" file (by spacewalk), do - run the script (which generates "Packages.new") - gzip -c Packages.new > Packages.gz - touch -r Packages Packages.new Packages.gz && mv Packages.new Packages So you have transferred the original timestamp to the new files and all set to "secure" your repo then. Robert >> /bin/mv $_PKG_MAIN/Packages.new $_PKG_MAIN/Packages >> /bin/mv $_PKG_SEC/Packages.new $_PKG_SEC/Packages >> /bin/mv $_PKG_UPD/Packages.new $_PKG_UPD/Packages >> /bin/mv $_PKG_UNIV/Packages.new $_PKG_UNIV/Packages >> >> gzip < $_PKG_MAIN/Packages > $_PKG_MAIN/Packages.gz >> gzip < $_PKG_UPD/Packages > $_PKG_UPD/Packages.gz >> gzip < $_PKG_SEC/Packages > $_PKG_SEC/Packages.gz >> gzip < $_PKG_UNIV/Packages > $_PKG_UNIV/Packages.gz >> >> cd $_PKG_MAIN >> $_BIN_PATH/secureApt.sh xenial xenial-main >> touch -r Packages.gz Packages >> cd $_PKG_UPD >> $_BIN_PATH/secureApt.sh xenial xenial-updates >> touch -r Packages.gz Packages >> cd $_PKG_SEC >> $_BIN_PATH/secureApt.sh xenial xenial-security >> touch -r Packages.gz Packages >> >> So just to resume, SYNC =>OK, applying ALL missing headers =>OK, now >> the >> packages that are showed as up-gradable dropped from ~120 to only 6 ( >> base-files libbind9-140 libisc160 libisccc140 libisccfg140 liblwres141 >> ) >> >> ~~BUT~~ >> >> Here I run into another problem, it seems taskomatic is generating >> Package files over and over ( touch -r Packages.gz Packages seems to >> have no effect) > > This seems to be new. You might have to check within code, at which > conditions a rebuild of the Packages file gets triggered > > I'm still on SW2.7 so I cannot test on my environment. > > Robert Hi Rober, So far so good, here is the
Re: [Spacewalk-list] spacewalk 2.9 && never ending issue with ubuntu/debian clients
On 2019-02-13 10:56, Florin Portase wrote: > Hello, > > I just have upgraded the spacewalk server from 2.7 => 2.9. > > I have applied also the sql patch from > https://bugzilla.redhat.com/show_bug.cgi?id=1661347 > > + upgraded the clients from : > > http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.9:/debclients/ > > > Just to mention spacewalk 2.7 + patches was working just fine for both > debian & ubuntu. > > Now, for ubuntu 16.05 I have over 100 packages marked as up-gradable( over > and over) > > ___ > > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list So, after digging through SPW archive Dec '18 til Feb '19 finally I come to something more acceptable: 1. sync script for Ubuntu channels 2. "spacewalk-add-debian-multiarch-header.py.NEW " took it from "https://www.redhat.com/archives/spacewalk-list/2018-December/msg00017.html; wget -q http://de.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages.gz \ -O /tmp/Packages-xenial-main.gz && gunzip -f /tmp/Packages-xenial-main.gz wget -q http://cz.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages.gz \ -O /tmp/Packages-xenial-updates.gz && gunzip -f /tmp/Packages-xenial-updates.gz wget -q http://cz.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages.gz \ -O /tmp/Packages-xenial-security.gz && gunzip -f /tmp/Packages-xenial-security.gz s=180 trap 'echo "Ctrl-C detected."' 2 for (( i=$s ; i>0; i--)); do #printf '\rFinishing sync in: %2d seconds' $i; sleep 1 echo -ne "\rFinishing sync in: $i seconds\033[0K"; sleep 1 done echo -e "\nSync completed!" trap 2 $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_MAIN/Packages/tmp/Packages-xenial-main $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_UPD/Packages /tmp/Packages-xenial-updates $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_SEC/Packages /tmp/Packages-xenial-security $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_UNIV/Packages/tmp/Packages-xenial-universe /bin/mv $_PKG_MAIN/Packages.new $_PKG_MAIN/Packages /bin/mv $_PKG_SEC/Packages.new $_PKG_SEC/Packages /bin/mv $_PKG_UPD/Packages.new $_PKG_UPD/Packages /bin/mv $_PKG_UNIV/Packages.new $_PKG_UNIV/Packages gzip < $_PKG_MAIN/Packages > $_PKG_MAIN/Packages.gz gzip < $_PKG_UPD/Packages > $_PKG_UPD/Packages.gz gzip < $_PKG_SEC/Packages > $_PKG_SEC/Packages.gz gzip < $_PKG_UNIV/Packages > $_PKG_UNIV/Packages.gz cd $_PKG_MAIN $_BIN_PATH/secureApt.sh xenial xenial-main touch -r Packages.gz Packages cd $_PKG_UPD $_BIN_PATH/secureApt.sh xenial xenial-updates touch -r Packages.gz Packages cd $_PKG_SEC $_BIN_PATH/secureApt.sh xenial xenial-security touch -r Packages.gz Packages So just to resume, SYNC =>OK, applying ALL missing headers =>OK, now the packages that are showed as up-gradable dropped from ~120 to only 6 ( base-files libbind9-140 libisc160 libisccc140 libisccfg140 liblwres141 ) ~~BUT~~ Here I run into another problem, it seems taskomatic is generating Package files over and over ( touch -r Packages.gz Packages seems to have no effect) signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.9 && never ending issue with ubuntu/debian clients
On 2019-02-13 10:56, Florin Portase wrote: > Hello, > > I just have upgraded the spacewalk server from 2.7 => 2.9. > > I have applied also the sql patch from > https://bugzilla.redhat.com/show_bug.cgi?id=1661347 > > + upgraded the clients from : > > http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.9:/debclients/ > > > Just to mention spacewalk 2.7 + patches was working just fine for both > debian & ubuntu. > > Now, for ubuntu 16.05 I have over 100 packages marked as up-gradable( over > and over) > > So, here are more info about: > > Spacewalk server 2.9 (upgraded from 2.7) > > +spacewalk-add-debian-multiarch-header.py > > Ubuntu client: 16.04 ( basic install => only ssh server) > > -here are the list of packages that are installed over and over... > > The following packages will be upgraded: > accountsservice amd64-microcode apparmor apport apt base-files bash > bash-completion bsdutils ca-certificates cloud-guest-utils console-setup > console-setup-linux coreutils cryptsetup cryptsetup-bin dh-python > distro-info-data dnsmasq-base dpkg friendly-recovery gcc-5-base git git-man > grep > grub-common grub-pc grub2-common ifupdown init init-system-helpers > initramfs-tools initramfs-tools-core keyboard-configuration klibc-utils kmod > language-selector-common libaccountsservice0 libapt-pkg5.0 libasprintf0v5 > libaudit-common libc6 libdbus-1-3 libglib2.0-0 libgssapi-krb5-2 libk5crypto3 > libkrb5-3 libkrb5support0 liblxc1 libpam-modules libparted2 libperl5.22 > libplymouth4 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpython2.7-minimal > libpython2.7-stdlib libpython3.5-stdlib libsasl2-2 libsasl2-modules > libsasl2-modules-db libstdc++6 libsystemd0 libx11-data linux-firmware > linux-headers-4.4.0-116 linux-headers-4.4.0-142 locales login logrotate > lsb-base lxc-common lxd lxd-client mdadm mount ntfs-3g open-iscsi > open-vm-tools > openssh-sftp-server perl perl-base perl-modules-5.22 plymouth policykit-1 > procps python python-apt python-apt-common python-minimal python2.7 > python2.7-minimal python3-apt python3-distupgrade python3-update-manager > python3.5-minimal resolvconf rsync snapd software-properties-common systemd > systemd-sysv tar ubuntu-release-upgrader-core udev update-manager-core > update-notifier-common util-linux uuid-runtime vim-common vim-runtime xfsprogs > zlib1g > 113 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/145 MB of archives. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] n > Abort. > > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] spacewalk 2.9 && never ending issue with ubuntu/debian clients
Hello, I just have upgraded the spacewalk server from 2.7 => 2.9. I have applied also the sql patch from https://bugzilla.redhat.com/show_bug.cgi?id=1661347 + upgraded the clients from : http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.9:/debclients/ Just to mention spacewalk 2.7 + patches was working just fine for both debian & ubuntu. Now, for ubuntu 16.05 I have over 100 packages marked as up-gradable( over and over) signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.8 && debian9 && ubuntu 16
Ok, so here are 2 examples: dpkg -l libperl5.24 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=- ii libperl5.24:amd64 5.24.1-3+deb9u4 amd64 shared Perl library dpkg -l perl-modules-5.24 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=- ii perl-modules-5.24 5.24.1-3+deb9u4 all Core Perl modules == apt-cache show perl-modules-5.24 Package: perl-modules-5.24 Version: 5.24.1-3+deb9u4 Architecture: all .. Filename: XMLRPC/GET-REQ/stretch-security/getPackage/perl-modules-5.24_5.24.1-3+deb9u4.all-deb.deb apt-cache show libperl5.24 Package: libperl5.24 Version: 5.24.1-3+deb9u4 Architecture: amd64 ... Filename: XMLRPC/GET-REQ/stretch-security/getPackage/libperl5.24_5.24.1-3+deb9u4.amd64-deb.deb grep -A4 ": libperl5.24" /var/cache/rhn/repodata/stretch-security/Packages Package: libperl5.24 Version: 5.24.1-3+deb9u3 Architecture: amd64 Maintainer: Niko Tyni Installed-Size: 20931 -- Package: libperl5.24 Version: 5.24.1-3+deb9u2 Architecture: amd64 Maintainer: Niko Tyni Installed-Size: 20930 -- Package: libperl5.24 Version: 5.24.1-3+deb9u4 Architecture: amd64 ..and here is the complete list of one of my systems: apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: dirmngr gnupg gnupg-l10n gpgv libcups2 libpam-systemd libperl5.24 libsystemd0 libudev1 linux-image-4.9.0-6-amd64 perl perl-base perl-modules-5.24 procps systemd systemd-sysv udev Hope it helps :) On 2018-08-07 11:36, Robert Paschedag wrote: > Hmmm...I think, the "server" side of this patch (rhnRepository.py) should > already be included within spacewalk. So this part of the patches should > be needed anymore (see > https://github.com/spacewalkproject/spacewalk/pull/636/files) and part of > "client side" patches in > https://github.com/spacewalkproject/spacewalk/pull/637/files > > I'm still running SW 2.7, so I cannot confirm this behaviour. > > But as I look through the pull requests, there was some work for Debian / > Ubuntu. Maybe something was done here. > > However, I think the problem might be my script to add the Multi-Arch > headers. So please show some output of packages you can "always" install over > and over again and also show "apt-cache search " to check the > headers. > > Robert > > GESENDET: Dienstag, 07. August 2018 um 10:50 Uhr > VON: "Florin Portase" > AN: spacewalk-list@redhat.com > BETREFF: [Spacewalk-list] spacewalk 2.8 && debian9 && ubuntu 16 > > Hello, > > It looks like spacewalk 2.8 broke again all workarounds to proper sync > debian9 and ubuntu 16 clients. > > So just to resume: > > server side > > I had to repatch : rhnRepository.py > > https://bugzilla.redhat.com/attachment.cgi?id=999613=diff=patch==1=raw > > > client side: > > https://bugzilla.redhat.com/attachment.cgi?id=999611=diff=patch==1=raw > > > https://bugzilla.redhat.com/attachment.cgi?id=999612=diff=patch==1=raw > > > ..and multi-arch + downloading debian packages from here: > > https://github.com/rpasche/spacewalk-debian-sync/tree/add-multiarch-header > > Just to mention, previous steps were working w/o any issues in case of > Spacewalk 2.7 > > Now, after repatching everything I get again,small list this time of packages > that are downloaded over and over for both Debian 9 + Ubuntu 16. > > So, any solution for it ? ___ > Spacewalk-list mailing list 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 signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] spacewalk 2.8 && debian9 && ubuntu 16
Hello, It looks like spacewalk 2.8 broke again all workarounds to proper sync debian9 and ubuntu 16 clients. So just to resume: server side I had to repatch : rhnRepository.py https://bugzilla.redhat.com/attachment.cgi?id=999613=diff=patch==1=raw client side: https://bugzilla.redhat.com/attachment.cgi?id=999611=diff=patch==1=raw https://bugzilla.redhat.com/attachment.cgi?id=999612=diff=patch==1=raw ..and multi-arch + downloading debian packages from here: https://github.com/rpasche/spacewalk-debian-sync/tree/add-multiarch-header Just to mention, previous steps were working w/o any issues in case of Spacewalk 2.7 Now, after repatching everything I get again,small list this time of packages that are downloaded over and over for both Debian 9 + Ubuntu 16. So, any solution for it ? signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] proper way of migrating satellite server RHEL6 => RHEL7
Hello, In our environment, we try to migrate a spacewalk server from rhel 6 to 7. So: - orig => 1xVM RHEL6 [ 1xdisk for OS + 1xdisk 300G ] for /var/satellite/redhat; OS with spacewalk installed , using an external postgres DB ( clustered ) - dst => 1xVM RHEL7 with same postgresDB from previous step - exported vg rhn_data_vg So, I just attached the old disk from previous machine to the new one , import rhn_data_vg. Now , in order to connect to same database, what would be the next step ? ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] proper way for creating channels for rhel7
Hello, I just have downloaded a huge list of rpms from: https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os Also I do have independent dvd for each release : DVD for rhel 7.2, 7.3, 7.4 Now what I can't figure out how to do properly: 1. - create a base channel for rhel7.2 [ from dvd ] + a child channel rhel 72-updates from all rpms *7_2*.rpm - create a base channel for rhel7.3 [ from dvd ] + a child channel rhel 73-updates from all rpms *7_3*.rpm i do have an activation key 1-rhel72 for rhel 72 release and 1-rhel73 for rhel 73 release now, if I want to upgrade from 72 to 73 w/o changing activation keys, or base channel in GUI howto do it properly ? 2. 2nd approach create a base channel with ALL rpms downloaded from "https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os; and and activation key for it , but if I'm running currently on rhel 72 and do yum update don't want to jump directly to rhel74, but only to install rhel72 updates it's something related to clone-by-date but as I said don;t know how to do it properly. signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] basic concept of multiple activation keys
Hello, I'm trying to figure out how to achieve this: 1. organization = ORG1 2. base channel rhel6-x64 2. 1 child channels - updates - rhn-tools - optional - vm-tools Activation keys 1-rh6-key [ base channel: rhel6-x64 + child channels: updates. optional, rhn-toools ] So far so good, But I'm trying to implement a custom bootstrap script: IF machine=Hp or DELL then *rhnreg_ks --activationkey=1-rh6-key* IF machime is VM then*rhnreg_ks --activationkey=1-rh6-key,1-vmtools* So, have no idea how to define activation key: 1-vmtools, that should contains only packages from vm-tools channel ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.6 debian jessie [package not found]
Hi, Environment: Centox6 x86_64 + spacewalk 2.6 Debian 8 custom channel Can confirm, that per suggested patch fixed the issue of downloading debian packages. ALSO IMPORTANT, DEBIAN CHANNELS [ IN MY CASE JESSIE-MAIN + JESSIE-UPDATES ] MUST TO BE DELETED AND RECREATE THEM + SYNC AGAIN. On 2017-01-08 21:22, Mark Hlawatschek wrote: > Hi, > > please take a look at my pull request. This might solve your issue. > https://github.com/spacewalkproject/spacewalk/pull/444 > > Mark > > -- > Mark Hlawatschek > > ATIX AG > http://www.atix.de > > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.6 debian jessie [package not found]
Hi Mark, Can't locate this file on my spacewalk server:: DebPackageWriter.java Now about rebuilding the rhn.jar file; I see only DebPackageWriter.class I'm quite noob when is about java ... :) On 2017-01-09 10:29, Mark Hlawatschek wrote: > Hi Florin, > > you also need to patch the file > java/code/src/com/redhat/rhn/taskomatic/task/repomd/DebPackageWriter.java and > rebuild rhn.jar. > After that you need to completely delete and rebuild your debian channel. > > Without the patches, spacewalk cannot distinguish between debian package name > and package version (for packages with multiple „-" in the file name). > > Mark signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.6 debian jessie [package not found]
On 2017-01-08 21:22, Mark Hlawatschek wrote: > Hi, > > please take a look at my pull request. This might solve your issue. > https://github.com/spacewalkproject/spacewalk/pull/444 > > Mark > > Am 08.01.2017 um 21:10 schrieb Florin Portase > <portase.flo...@medianetork.ro>: > > On 2017-01-08 21:04, Robert Paschedag wrote: > Am 8. Januar 2017 19:58:11 MEZ schrieb Florin Portase > <portase.flo...@medianetork.ro>: Hello, > > I just created a channel for debian 8 [ jessie-main+jessie-updates ] > > So far so good, however, to certain packages apt-get complains can't > find them. > > Ex: > > apt-get install openjdk-7-jre > > Err spacewalk://192.168.50.105/ channels:/jessie-updates > openjdk-7-jre-headless amd64 7u111-2.6.7-2~deb8u1 > 404 Not Found > Err spacewalk://192.168.50.105/ channels:/jessie-updates openjdk-7-jre > amd64 7u111-2.6.7-2~deb8u1 > 404 Not Found > E: Failed to fetch > spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb > 404 Not Found > > E: Failed to fetch > spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb > 404 Not Found > > And here httpd access log > > 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "POST /XMLRPC HTTP/1.1" > 200 2005 "-" "rhn.rpclib.py/$Revision$" > 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "GET > //XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb > HTTP/1.1" 404 - "-" "-" > 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "GET > //XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb > HTTP/1.1" 404 - "-" > > = > > File located on spacewalk server > > redhat/1/d54/openjdk-7-jre-headless/7u111-2.6.7-2~deb8u1/amd64-deb/d540e4f7c8da546091c349cefb38d970747050f2f00e3a360ddb11466e7df9c6/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb > > redhat/1/3db/openjdk-7-jre/7u111-2.6.7-2~deb8u1/amd64-deb/3db61f01db5861b184385f9bb9e01b251abe912167f51eab4a73aac7e25f24bf/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb > > Also, if I go to jessie-updates channel, can find + download them . > > I deleted the channel+delete the packages but still same issue, EVERY > time apt-get complains about the same packages ? > > Is some other ways to trace this issue or anyone faced the same ? > Please also show us the sync logs, where these files have been downloaded > from Debian server. > > Robert So, here are [root@web-satt1 repodata]# grep openjdk-7-jre /var/log/rhn/reposync/jessie-updates.log 2016/12/19 13:19:01 +02:00 1689/2118 : openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb 2016/12/19 13:19:01 +02:00 1690/2118 : openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb 2016/12/19 13:19:23 +02:00 1691/2118 : openjdk-7-jre-lib-7u111-2.6.7-2~deb8u1.all-deb 2016/12/19 13:19:23 +02:00 1692/2118 : openjdk-7-jre-zero-7u111-2.6.7-2~deb8u1.amd64-deb .. 2017/01/08 06:01:50 +02:00 18/18 : pcscd-1.8.13-1+deb8u1.amd64-deb 2017/01/08 06:01:51 +02:00 Linking packages to channel. 2017/01/08 06:01:52 +02:00 Repo http://security.debian.org/dists/jessie/updates/main/binary-amd64/ has 0 errata. 2017/01/08 06:01:52 +02:00 Sync of channel completed in 0:01:51. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list -- Mark Hlawatschek ATIX AG http://www.atix.de ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list Hi Mark, In fact after patching /usr/lib/python2.6/site-packages/spacewalk/common/rhn/Lib.py /usr/lib/python2.6/site-packages/spacewalk/rhn_deb.py /usr/lib/python2.6/site-packages/spacewalk/server/rhnLib.py still no success [ I just deleted all packages in channel and resync ] ++ Why E: Failed to fetch spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-main/getPackage/aspell-en-7.1-0-1.1.all-deb.deb 404 Not Found but apt-get install aspell-de is OK both packages being present on the server ?!?!!? signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk 2.6 debian jessie [package not found]
On 2017-01-08 21:04, Robert Paschedag wrote: > Am 8. Januar 2017 19:58:11 MEZ schrieb Florin Portase > <portase.flo...@medianetork.ro>: > >> Hello, >> >> I just created a channel for debian 8 [ jessie-main+jessie-updates ] >> >> So far so good, however, to certain packages apt-get complains can't >> find them. >> >> Ex: >> >> apt-get install openjdk-7-jre >> >> Err spacewalk://192.168.50.105/ channels:/jessie-updates >> openjdk-7-jre-headless amd64 7u111-2.6.7-2~deb8u1 >> 404 Not Found >> Err spacewalk://192.168.50.105/ channels:/jessie-updates openjdk-7-jre >> amd64 7u111-2.6.7-2~deb8u1 >> 404 Not Found >> E: Failed to fetch >> spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb >> 404 Not Found >> >> E: Failed to fetch >> spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb >> 404 Not Found >> >> And here httpd access log >> >> 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "POST /XMLRPC HTTP/1.1" >> 200 2005 "-" "rhn.rpclib.py/$Revision$" >> 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "GET >> //XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb >> HTTP/1.1" 404 - "-" "-" >> 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "GET >> //XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb >> HTTP/1.1" 404 - "-" >> >> = >> >> File located on spacewalk server >> >> redhat/1/d54/openjdk-7-jre-headless/7u111-2.6.7-2~deb8u1/amd64-deb/d540e4f7c8da546091c349cefb38d970747050f2f00e3a360ddb11466e7df9c6/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb >> >> redhat/1/3db/openjdk-7-jre/7u111-2.6.7-2~deb8u1/amd64-deb/3db61f01db5861b184385f9bb9e01b251abe912167f51eab4a73aac7e25f24bf/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb >> >> Also, if I go to jessie-updates channel, can find + download them . >> >> I deleted the channel+delete the packages but still same issue, EVERY >> time apt-get complains about the same packages ? >> >> Is some other ways to trace this issue or anyone faced the same ? > > Please also show us the sync logs, where these files have been downloaded > from Debian server. > > Robert So, here are [root@web-satt1 repodata]# grep openjdk-7-jre /var/log/rhn/reposync/jessie-updates.log 2016/12/19 13:19:01 +02:00 1689/2118 : openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb 2016/12/19 13:19:01 +02:00 1690/2118 : openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb 2016/12/19 13:19:23 +02:00 1691/2118 : openjdk-7-jre-lib-7u111-2.6.7-2~deb8u1.all-deb 2016/12/19 13:19:23 +02:00 1692/2118 : openjdk-7-jre-zero-7u111-2.6.7-2~deb8u1.amd64-deb .. 2017/01/08 06:01:50 +02:00 18/18 : pcscd-1.8.13-1+deb8u1.amd64-deb 2017/01/08 06:01:51 +02:00 Linking packages to channel. 2017/01/08 06:01:52 +02:00 Repo http://security.debian.org/dists/jessie/updates/main/binary-amd64/ has 0 errata. 2017/01/08 06:01:52 +02:00 Sync of channel completed in 0:01:51. signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] spacewalk 2.6 debian jessie [package not found]
Hello, I just created a channel for debian 8 [ jessie-main+jessie-updates ] So far so good, however, to certain packages apt-get complains can't find them. Ex: apt-get install openjdk-7-jre Err spacewalk://192.168.50.105/ channels:/jessie-updates openjdk-7-jre-headless amd64 7u111-2.6.7-2~deb8u1 404 Not Found Err spacewalk://192.168.50.105/ channels:/jessie-updates openjdk-7-jre amd64 7u111-2.6.7-2~deb8u1 404 Not Found E: Failed to fetch spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb 404 Not Found E: Failed to fetch spacewalk://192.168.50.105/XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb 404 Not Found And here httpd access log 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "POST /XMLRPC HTTP/1.1" 200 2005 "-" "rhn.rpclib.py/$Revision$" 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "GET //XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb HTTP/1.1" 404 - "-" "-" 192.168.50.16 - - [08/Jan/2017:19:48:22 +0100] "GET //XMLRPC/GET-REQ/jessie-updates/getPackage/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb HTTP/1.1" 404 - "-" = File located on spacewalk server redhat/1/d54/openjdk-7-jre-headless/7u111-2.6.7-2~deb8u1/amd64-deb/d540e4f7c8da546091c349cefb38d970747050f2f00e3a360ddb11466e7df9c6/openjdk-7-jre-headless-7u111-2.6.7-2~deb8u1.amd64-deb.deb redhat/1/3db/openjdk-7-jre/7u111-2.6.7-2~deb8u1/amd64-deb/3db61f01db5861b184385f9bb9e01b251abe912167f51eab4a73aac7e25f24bf/openjdk-7-jre-7u111-2.6.7-2~deb8u1.amd64-deb.deb Also, if I go to jessie-updates channel, can find + download them . I deleted the channel+delete the packages but still same issue, EVERY time apt-get complains about the same packages ? Is some other ways to trace this issue or anyone faced the same ? signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Antwort: spacewalk 2.6 multiple activation keys / register system to epel channel
Hi, So, looks like I will try to be a bit more clear centos7.3-base | \_ centos7.3-updates rhel-7 | \_ epel_rhel7_x86_64 As shown here I have 2 base channels [ centos7.3-base/centos7.3-updates, rhel-7/epel_rhel7_x86_64 ] And I have also a distribution channel mapping OS=centos-release Release=7 ARCH=x86_64 Channel Label=centos-7.3-base ] Now, the issue: My activation key has as BASE Channel " SPACEWALK DEFAULT" that points to distribution channel mapping and for the child channels "centos7.3-updates, epel_rhel7_x86_64" Problem is the child channel "epel_rhel7_x86_64" got ignored during system registration... And have no idea why ? Have attached a screenshot to illustrate better. On 2017-01-06 12:05, Matthias Gruber wrote: Hi! As far as I know, and if I understand your problem correct, you can not assign a System with two basechannels, only with one basechannel and as many childchannels below that base channel as you like, but perhaps thats new in 2.6 we use a 2.5 cheers Matthias Von:Florin Portase <portase.flo...@medianetork.ro> An:spacewalk-list@redhat.com Datum:06.01.2017 11:23 Betreff:[Spacewalk-list] spacewalk 2.6 multiple activation keys / register system to epel channel Gesendet von:spacewalk-list-boun...@redhat.com - * PGP Signed by an unknown key Hello, So here is my setup:: Spacewalk 2.6 Software Channels centos7.2-base | \_ centos7.2-updates centos7.3-base | \_ centos7.3-updates rhel-7 | \_ epel_rhel7_x86_64 So far so good, but here is what I can't figure out what do I have to do:: I want to register a system, let's say for base channel centos7.3-base + epel7 To reproduce what I have tried: 1. create distrib channel mapping => OS=centos-release Release=7 ARCH=x86_64 Channel Label=centos-7.3-base 2. create an activation key [ 1-MYORG-key01 ]=> Base Channel = "Spacewalk Default" Child Channels="centos-7.3-updates, epel_rhel7_x86_64" But on my client system [ installed centos 7.3 ] if I do rhnreg_ks --activationkey=1-MYORG-key01 system is registering only on centos7.3-base + centos-7.3-updates; epel is completely ignored * Unknown Key * 0x4994F78A(L) ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von Metzler, Emmerich Müller, Dr. Johannes J. Reich, Gerhard Wiesheu Vorsitzender des Aufsichtsrates: Dr. Christoph Schücking Sitz der Gesellschaft: Frankfurt am Main, Handelsregisternummer: HRB 27 515 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen und die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder Vollständigkeit der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern können, sind die vorstehenden Ausführungen rechtlich nicht bindend. Eine Haftung hierfür wird ausgeschlossen. This message is confidential. If you are not the intended recipient, we kindly ask you to inform the sender and delete the information. Any unauthorised dissemination or copying hereof is prohibited. As we cannot guarantee or assure the genuineness or completeness of the information contained in this message, the statements set forth above are not legally binding. Accordingly we cannot accept any liability for their contents. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list signature.asc Description: OpenPGP digital signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] spacewalk 2.6 multiple activation keys / register system to epel channel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, So here is my setup:: Spacewalk 2.6 Software Channels centos7.2-base | \_ centos7.2-updates centos7.3-base | \_ centos7.3-updates rhel-7 | \_ epel_rhel7_x86_64 So far so good, but here is what I can't figure out what do I have to do:: I want to register a system, let's say for base channel centos7.3-base + epel7 To reproduce what I have tried: 1. create distrib channel mapping => OS=centos-release Release=7 ARCH=x86_64 Channel Label=centos-7.3-base 2. create an activation key [ 1-MYORG-key01 ]=> Base Channel = "Spacewalk Default" Child Channels="centos-7.3-updates, epel_rhel7_x86_64" But on my client system [ installed centos 7.3 ] if I do rhnreg_ks - --activationkey=1-MYORG-key01 system is registering only on centos7.3-base + centos-7.3-updates; epel is completely ignored -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEbBAEBAgAGBQJYb2xeAAoJEEleVOdJlPeKsmoH+Mc8QVp9ORWEDWEg5rDpX/lk tKbSWatlB6XtbFPYDbTj6GEgYdjpHYQANhOys18N7Y73DDSuJMyQdc8mr7cJMX3g dC10PlOlhjO70C9dir7zwK8umvFyIgUrzChSV3MCGsJjNGMzPRJclnNze0YZwIHa vxFzzv4aDFyR+D33NF1Or1vLdrCiavCKvLNHScSc/edwA5JUyZn93hA4ca51l4iH ZsoIuRYhmDalSvw03ZxfoGy8Qevx9NHlSFylVP/z3A49Q6yyt4ijsXCAVPjv5ybr gITaEXwSNzqB4ZdjKCxd5v1ZIA4/Lh4qOAF1l2aGZIDypgYopW4EqOwZbkMWeg== =ujZQ -END PGP SIGNATURE- ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
