[Spacewalk-list] Server ping through proxy not working

2018-04-20 Thread Guy Matz 
anyone have any good method for debugging this?  My jabber clients/servers
can all talk to each other, and osa-dispatcher is running on the spacewalk
server . . .

Any thoughts would be really appreciated.

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

Re: [Spacewalk-list] Spacewalk 2.8 Released!

2018-04-20 Thread Michael Watters 
It may help to mention in the upgrade guide that you need to run yum
upgrade 'spacewalk*'.  Just running yum upgrade would not install any
updates on my server.


On 04/19/2018 12:59 PM, Jiří Dostál wrote:
> Hello everyone,
>
> We are proudly announcing release of Spacewalk 2.8, a systems
> management solution.
>
> Spacewalk 2.8 could be installed on
>
>     * RHEL 6
>     * RHEL 7
>     * Fedora 26
>     * Fedora 27
>     * Fedora 28 (tested on Beta)
>
> The download location is
>
> https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/spacewalk-2.8/
>
> with client repositories under
>
> https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/spacewalk-2.8-client/
>
>
> SUSE Linux client packages can be found here
>
> http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8/
>
>
> For fresh installations, please use steps from
>
> https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall
>
> If you plan to upgrade from older release, search no more -- the
> following page will guide you:
>
> https://github.com/spacewalkproject/spacewalk/wiki/HowToUpgrade
>
> Features & Enhancements in Spacewalk 2.8
>
>     * Spacewalk now installable on Fedora 27 and has been tested on
> Fedora 28 Beta as well
>     * Spacewalk supports Fedora 27 and Fedora 28 clients
>     * All packages and repositories are exclusively in
> https://copr.fedorainfracloud.org/
>     * spacewalkproject.github.io has been completely redesigned
>     * Python 2 packages are no longer needed on systems with Python 3
> as default
>     * Spacewalk server is now capable of syncing and distributing of
> Fedora modularity (modules.yaml) files.
>     * PostgreSQL 10 is now supported
>     * Package dwr updated to version 3.0.2 fixing security
> vulnerabilities
>     * It's now possible to manage errata severities via Spacewalk server
>     * Several bugfixes
>
>     Updated API calls:
>  * errata.create/setDetails - add possibility to manage
> severities
>  * system.schedulePackageRemoveByNevra - support removal of
> packages which are not in database
>
> Known issues
> * Unfortunately, for certain domain names jabberd does not start on
> Fedora 27/28 due to issue with
>    'libidn-1.34-1' from Fedora repositories. If you run at this issue,
> please downgrade the package to libidn-1.33-1
>     until it's fixed in Fedora repositories.
>
> The up-to-date API documentation can be found at
> http://spacewalkproject.github.io/documentation/api/2.8/
>
> Contributors
>
> Our thanks go to the community members who contributed to this release:
>
>     Amit Upadhye
>     Andrew Dahms
>     Ben Roberts
>     Candace
>     Candace Sheremeta
>     Christian Lanig
>     Dario Leidi
>     Dario Maiocchi
>     Frantisek Kobzik
>     Jakub Jankowski
>     Johannes Renner
>     Kevin Walter
>     Laurence Rochfort
>     Marcelo Moreira de Mello
>     Mattias Giese
>     Michael Calmer
>     Michele Bologna
>     Miroslav Suchý
>     Pavel Studenik
>     Robert Paschedag
>     Silvio Moioli
>     Thomas Blanchard
>     Thomas Mueller
>     angystardust
>     bhavesh_bharadiya
>     ranmses
>     suzuki
>
> see https://github.com/spacewalkproject/spacewalk/wiki/ContributorList
> for all contributors list
>
> Some statistics
>
> In Spacewalk 2.8, we've seen
>
> * 85 major bugs fixed
> * 641 changesets committed
> * 1146 commits done
>
> User community, reporting issues
>
> To reach the user community with questions and ideas, please use
> mailing list spacewalk-list@redhat.com.
> On this list, you can of course also discuss issues you might find
> when installing or using Spacewalk,
> but please do not be surprised if we ask you to file a bug at
> https://bugzilla.redhat.com/enter_bug.cgi?product=Spacewalk with more
> details or full logs.
>
> Thank you for using Spacewalk.
>
> ___
> 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

Re: [Spacewalk-list] Roll back doesn't happend

2018-04-20 Thread Yakin, Francis 
Michael

There is no actual error, it reported from event-history it was successful, but 
it doesn't roll back to the previous one.
I created a snapshot and tag it before I patch the system, so the snapshot 
should contains the packages needed before I upgrade it.

Francis

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Michael Mraka
Sent: Thursday, April 19, 2018 11:30 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Roll back doesn't happend

Yakin, Francis:
> Hi All,
> 
> I need some help.
> 
> I created a Snap shot - and Tag it before I did the patching on one of our 
> CentOS 7.4 client. It has 170 packages needed to be upgraded.
> 
> Patched it ( clear it become 0 packages needed to be upgrade) and we tried to 
> roll back from the snapshot, but it didn't happened.
> It should back to 170 packages, but it just doesn't work.

Hello Francis,

What was the actual error message?
Do you have all packages necessary for rollback available in your
spacewalk server?

> I tried to run rhn-profile-sync, and still not working.
> 
> Thanks
> 
> Francis Yakin | IT System Admin |  direct: 510-749-2027
> 500 Wind River Way, Alameda, CA  94501
> [cid:image001.png@01D12D0C.E17713F0]
> AN INTEL COMPANY

--
Michael Mráka
System Management Engineering, Red Hat

___
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

Re: [Spacewalk-list] Spacewalk 2.7 && Ubuntu 15.04 && Debian 9 [ working solution ]

2018-04-20 Thread Florin 

Hi Robert,

Just updated to spacewalk 2.8 and  some minor updates to secureApt.sh

cd $_PKG_MAIN
 /var/www/html/pub/spw_scripts/secureApt.sh  xenial xenial-main
cd $_PKG_SEC
 /var/www/html/pub/spw_scripts/secureApt.sh  xenial xenial-security

===

DATE=`date "+%a, %d %b %Y %H:%M:%S *UTC*"`
GPG_PASS='bugsbunny'

HEADER="Origin: Ubuntu
Label: Ubuntu
Date: ${DATE}
Archive: $1
Version: 16.04
Architectures: amd64
Component: $2
MD5Sum:"


.

echo $GPG_PASS | gpg --armor *--digest-algo SHA256* --detach-sign -o 
Release.gpg *--default-key 88B9763A* --batch --no-tty --passphrase-fd 0 
--sign Release


=

Somehow if I have multiple keys defined to get the last one, have no 
idea how to automate this.



On 20.4.2018 06:39, Robert Paschedag wrote:

Am 19. April 2018 15:08:05 MESZ schrieb Florin :

So, finally after so much trial and error here is what I've done to
allow smooth integration of Debian 9 and Ubuntu 16.0 with spacewalk

Just to keep it simple

1. create channels: xenial-main + xenial-updates, xenial-security,
xenial-universe

2. tricky part  syncing channels [ adding multi-arch header]:

#!/bin/bash

_BIN_PATH=/var/www/html/pub/spw_scripts
_URL_MAIN='http://de.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64'
_URL_SEC='http://us.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64'
_URL_UPD='http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64'
_URL_UNIV='http://de.archive.ubuntu.com/ubuntu/dists/xenial/universe/binary-amd64'
_PKG_MAIN=/var/cache/rhn/repodata/xenial-main
_PKG_SEC=/var/cache/rhn/repodata/xenial-security
_PKG_UPD=/var/cache/rhn/repodata/xenial-updates
_PKG_UNIV=/var/cache/rhn/repodata/xenial-universe
_USER=bugs
_PASS=bunny

$_BIN_PATH/spacewalk-debian-sync.pl  --url $_URL_MAIN --channel
xenial-main    --username=$_USER  --password $_PASS
$_BIN_PATH/spacewalk-debian-sync.pl  --url $_URL_SEC  --channel
xenial-security --username=$_USER  --password $_PASS
$_BIN_PATH/spacewalk-debian-sync.pl  --url $_URL_UPD  --channel
xenial-updates    --username=$_USER  --password $_PASS
$_BIN_PATH/spacewalk-debian-sync.pl  --url $_URL_UNIV  --channel
xenial-universe  --username=$_USER  --password $_PASS

s=180
trap 'echo "Ctrl-C detected."' 2
for (( i=$s ; i>0; i--));
     do
     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
$_PKG_MAIN/Packages
/tmp/xenial-main
$_BIN_PATH/spacewalk-add-debian-multiarch-header.py
$_PKG_SEC/Packages    /tmp/xenial-security
$_BIN_PATH/spacewalk-add-debian-multiarch-header.py
$_PKG_UPD/Packages
/tmp/xenial-updates
$_BIN_PATH/spacewalk-add-debian-multiarch-header.py
$_PKG_UNIV/Packages
/tmp/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_SEC/Packages > $_PKG_SEC/Packages.gz
     gzip < $_PKG_UPD/Packages > $_PKG_UPD/Packages.gz
     gzip < $_PKG_UNIV/Packages > $_PKG_UNIV/Packages.gz

3. client side  [ ubuntu/debian clients]

spw_srv=192.168.100.101

cat >/etc/apt/apt.conf.d/50spacewalk<
You don't need this Post-Invoke hack as the python script adds the missing 
header.


   }
};
DPkg::Post-Invoke {
     "[ ! -e /usr/lib/apt-spacewalk/post_invoke.py ] ||
/usr/lib/apt-spacewalk/post_invoke.py";
};
FIX
sed  -i "s|'main'|'xenial-main'|g" /usr/lib/apt-spacewalk/pre_invoke.py
perl -pi -e "s/type='deb'/type='deb [trusted=yes] '/g"
/usr/lib/apt-spacewalk/pre_invoke.py

4. Now can perform apt-get update/upgrade w/o any issues after
disabling
/etc/apt/source.list

One thing "missing". Secure the channels with @philicious "secureApt.sh" script. Find it 
at my fork  https://github.com/rpasche/spacewalk-scripts or "origin" 
https://github.com/philicious/spacewalk-scripts.
Also have a look at PR #636 and #637 of the SW GitHub repo.

You can then also try to import errata information for Ubuntu and Debian.

Robert



___
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

Re: [Spacewalk-list] Roll back doesn't happend

2018-04-20 Thread Michael Mraka 
Yakin, Francis:
> Hi All,
> 
> I need some help.
> 
> I created a Snap shot - and Tag it before I did the patching on one of our 
> CentOS 7.4 client. It has 170 packages needed to be upgraded.
> 
> Patched it ( clear it become 0 packages needed to be upgrade) and we tried to 
> roll back from the snapshot, but it didn't happened.
> It should back to 170 packages, but it just doesn't work.

Hello Francis,

What was the actual error message?
Do you have all packages necessary for rollback available in your
spacewalk server?

> I tried to run rhn-profile-sync, and still not working.
> 
> Thanks
> 
> Francis Yakin | IT System Admin |  direct: 510-749-2027
> 500 Wind River Way, Alameda, CA  94501
> [cid:image001.png@01D12D0C.E17713F0]
> AN INTEL COMPANY

--
Michael Mráka
System Management Engineering, Red Hat

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