[Spacewalk-list] RHEL 6,7,8 clients

[abhishekk.kumar]

Hello All,



It is may be an amateur question but it is very important for me. Could you 
please confirm if I can manage RHEL (6/7/8) clients using spacewalk?



If yes, are there any limitations for that, I am just trying to patch them 
using custom errata and custom repository.





Regards,

Abhishek


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[Spacewalk-list] Antwort: Process question - installing SW client RPMs when no Internet access is possible

[Matthias Gruber]

Hi Larry,

well I put the needed Files in a own "starting"-Repository. I Installed a 
machine, did a rpm -ql >PreSW, inststalled the SW-Client did a nother rpm 
-ql, then put all files in the diff into a repo for initial installation.
They reside on every Proxy or my SW-Server in the html-Directory... simple 
but works :-)

cheers
Matthias


METZLER 
Informationstechnologie

Matthias Gruber 
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com
www.metzler.com



Von:"Larry Clegg" 
An: spacewalk-list@redhat.com
Datum:  25.10.2019 00:09
Betreff:[Spacewalk-list] Process question - installing SW client 
RPMs when no Internet access is possible
Gesendet von:   spacewalk-list-boun...@redhat.com



Greetings Spacers,
 
I am wondering how others handle this situation:
 
When a new server is provisioned how do you get the Spacewalk client RPMs 
installed?  Our internal servers cannot reach the Internet so following 
the standard SW client installation procedures is not a viable option for 
us.  Currently including the RPMs in a pre-built image is also not a 
viable option for us at the moment.  I’ve thought about creating an 
internal repo that houses the RPMs but I haven’t figured out how to manage 
all the dependencies as well.
 
Thanks for your insight.   Regards,
 
Larry E. Clegg
Systems Engineer (SaaS Platform Operations) | Kyriba
[Cell Phone] +1 858-357-5579
[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California | 
92121
www.kyriba.com | Facebook | Twitter | LinkedIn | Blog
 ___
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, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. 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.


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

[Spacewalk-list] Process question - installing SW client RPMs when no Internet access is possible

[Larry Clegg]

Greetings Spacers,



I am wondering how others handle this situation:



When a new server is provisioned how do you get the Spacewalk client RPMs
installed?  Our internal servers cannot reach the Internet so following the
standard SW client installation procedures is not a viable option for us.
Currently including the RPMs in a pre-built image is also not a viable
option for us at the moment.  I’ve thought about creating an internal repo
that houses the RPMs but I haven’t figured out how to manage all the
dependencies as well.



Thanks for your insight.   Regards,



*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com | Facebook  | Twitter
 | LinkedIn
 | Blog

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

[Spacewalk-list] CentOS8 support in Spacewalk 2.9?

[Michael Trip]

Hi all,

i am trying to kickstart centOS8 in Spacewalk 2.9. I have some problems 
with packages nog being detected.


Ik have 1 Channel containing the  BaseOS repo. I have created a 
kickstartable distribution from this repo.
I have one child channel containing the Appstream repo. Both of them 
are enabled in the kickstart configuration. But the installer is not 
working. It is missing several packages including wget, perl, rhn-tools 
and so on.


Can someone help me with this? If i am forgetting anything imported 
please let me know.


Kind regards,

Michael Trip

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

[Spacewalk-list] Error in apt update

[Thiago Anderson Santos]

Hello,

I am implementing SpaceWalk 2.9 in my technology park, I am having problems
to do the apt update of the machines.

Some technical information:

- Server
 * CentOS 7.5
 * Spacewalk 2.9-4
 * Created repositories like Debian amd64

- Workstation:
  * Ubunutu 18.04.2 LTS
  * Installed packages and their commands:
apt-get -y install gir1.2-gudev-1.0 libgudev-1.0-0 python-dbus python-newt
python-dmidecode python-dbus-dev python-libxml2 python-gobject python-gi
python-gobject-2 python-ethtool python -jabber python-apt python-openssl
  apt-get -y -f install

  # Download and install our spacewalk packages, which are newer than in
the default 18.04 repo
  mkdir / tmp / bionic-debs
  pushd / tmp / bionic-debs
  wget --no-check-certificate https:
//$spacewalkserver/pub/spacewalk-client-bionic/apt-transport-spacewalk_1.0.6-4.1_all.deb
  wget --no-check-certificate https:
//$spacewalkserver/pub/spacewalk-client-bionic/python-rhn_2.5.72-1_all.deb
  wget --no-check-certificate https:
//$spacewalkserver/pub/spacewalk-client-bionic/rhn-client-tools_2.3.5-1_amd64.deb
  wget --no-check-certificate https:
//$spacewalkserver/pub/spacewalk-client-bionic/rhnsd_5.0.4-3_amd64.deb
  wget --no-check-certificate https:
//$spacewalkserver/pub/spacewalk-client-bionic/python-ethtool_0.12-1_amd64.deb
wget --no-check-certificate https:
//$spacewalkserver/pub/spacewalk-client-bionic/python-gudev_147.2-3_amd64.deb
  apt install -y ./python-ethtool_0.12-1_amd64.deb
./python-rhn_2.5.72-1_all.deb ./python-gudev_147.2-3_amd64.deb
  apt install ./rhn-client-tools_2.3.5-1_amd64.deb
 apt install ./apt-transport-spacewalk_1.0.6-4.1_all.deb
apt install ./rhnsd_5.0.4-3_amd64.deb

  apt-get -y -f install
  wget --no-check-certificate "https:
//$spacewalkserver/pub/spacewalk.gpg.pubkey";
  apt-key add spacewalk.gpg.pubkey

  # Now set up and register with our Spacewalk server
  mkdir / var / lock / subsys
  wget --no-check-certificate https: // $ spacewalkserver / pub /
RHN-ORG-TRUSTED-SSL-CER / O / usr / share / rhn / RHN-ORG-TRUSTED-SSL-CERT
  rhnreg_ks --force --serverUrl = https: // $ spacewalkserver / XMLRPC
--sslCACert = / usr / share / rhn / RHN-ORG-TRUSTED-SSL-CERT
--activationkey = 1-ubuntu-18-lts-workstation
  # Take updates and security patches for main and universe from spacewalk
  echo "deb spacewalk: // $ spacewalkserver / XMLRPC channels: main
bionic-updates bionic-backports bionic-security">
/etc/apt/sources.list.d/spacewalk.list
  cp /etc/apt/sources.list /etc/apt/sources.list.bak
  # and not from the standard repositories
  perl -pi -e 's / ^ deb ([- src] *) (. *) bionic main / # deb $ 1 $ 2
bionic main /' /etc/apt/sources.list
  perl -pi -e 's / ^ deb ([- src] *) (. *) bionic-updates ([m | u] [^ u]) /
# deb $ 1 $ 2 bionic-updates $ 3 /' / etc / apt /sources.list
  perl -pi -e 's / ^ deb ([- src] *) (. *) bionic-security ([m | u] [^ u])
/ # deb $ 1 $ 2 bionic-security $ 3 /' / etc / apt /sources.list
  perl -pi -e 's / ^ deb ([- src] *) (. *) bionic-backports / # deb $ 1 $ 2
bionic-backports /' /etc/apt/sources.list

  # Work around https://bugzilla.redhat.com/show_bug.cgi?id=1187189
  wget --no-check-certificate https: // $ spacewalkserver / pub /
spacewalk-client-bionic / 49spacewalk-workaround -O
/etc/apt/apt.conf.d/49spacewalk-workaround

cat /etc/apt/apt.conf.d/49spacewalk-workaround
Acquire :: Pdiffs "false";


After apt:

gn: 1 spacewalk: // spacewalk / XMLRPC channels: InRelease
Err: 2 spacewalk: // spacewalk / XMLRPC channels: Release
  404 Not Found

E: The repository 'spacewalk: // spacewalk / XMLRPC channels: Release' does
not have a Release file.
Updating from such a repository cannot be done securely, and is therefore
disabled by default.
See apt-secure (8) manpage for repository creation and user configuration
details.




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

Re: [Spacewalk-list] Spacewalk Channels not

[Glennie, Jonathan - 0443 - MITLL]

Jonathan-

 

Did you ever find a solution for this?  We are running into a similar
problem after updating our distro tree to the Cent 7.7 from 7.6.  

 

From: spacewalk-list-boun...@redhat.com 
On Behalf Of Jonathan Horne
Sent: Wednesday, February 13, 2019 10:54 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk Channels not

 

its been a few months since i last built a new CentOS7 system via my
spacewalk server, but this past week i tried to build a new one over PXE and
now i am getting strange errors.

if i use my existing profiles (which include other child channels like
updates, EPEL7, etc) it hangs with this error in the packaging log:

 

14:17:53,301 WARN packaging: 1:NetworkManager-1.12.0-8.el7_6.x86_64 requires
glib2 >= 2.56.1
14:17:53,301 WARN packaging: systemd-219-62.el7_6.3.x86_64 requires
libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit)
14:17:53,301 WARN packaging: policycoreutils-2.5-29.el7_6.1.x86_64 requires
libselinux-utils >= 2.5-14
14:17:53,301 WARN packaging: systemd-219-62.el7_6.3.x86_64 requires
libcryptsetup.so.12()(64bit)
14:17:53,301 WARN packaging: policycoreutils-2.5-29.el7_6.1.x86_64 requires
libsemanage >= 2.5-14
14:17:53,301 WARN packaging: policycoreutils-2.5-29.el7_6.1.x86_64 requires
libsepol >= 2.5-10
14:17:53,301 WARN packaging: selinux-policy-3.13.1-229.el7_6.9.noarch
requires libsemanage >= 2.5-13
14:17:53,302 WARN packaging: kernel-3.10.0-957.5.1.el7.x86_64 requires
linux-firmware >= 20180911-68
14:17:53,302 WARN packaging: nss-util-3.36.0-1.1.el7_6.x86_64 requires nspr
>= 4.19.0-1
14:17:53,302 WARN packaging: nss-3.36.0-7.1.el7_6.x86_64 requires
nss-softokn(x86-64) >= 3.36.0-1
14:17:53,302 WARN packaging: nss-3.36.0-7.1.el7_6.x86_64 requires nspr >=
4.19.0

 

upon verifying packages in both the package search in the spacewalk gui as
well as double checking files in the file system on the spacewalk server,
the package at a higher revision is there.  i made a new test profile which
only included base and updates, and got the same error.  if i remove the
updates channel, it tries to proceed, then hangs with 

 

Error populating transaction and fails 10 times, in this case trying to find
3.10.0-862.el7 when in fact the kernel in the repo for the base install is
3.10.0-957.el7.  

in troubleshooting i have deleted all my existing centos repo files (but not
the actual channels) and re-run spacewalk-repo-sync, but it seems like
anaconda is pulling some really old package list that is no longer current
to the physical rpm files that are there.

i have googled and googled, but have not found the solution i need.  i am
sure this will turn out to be something simple, but i just cant place my
finger on it.

thanks for any help,

Jonathan



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