Re: [Spacewalk-list] Alternatives

[William Hongach]

Good Afternoon,

From the background you have listed, Spacewalk on Oracle Linux or Uyuni on 
openSUSE / SLES could be viable alternatives for you to consider.  Hope this 
helps.


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Emmett Hogan
Sent: Wednesday, December 16, 2020 2:18 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Alternatives


[EXTERNAL EMAIL]
Hi Everyone,

First off, I want to thank everyone in this community for all the help over the 
years, Spacewalk has been a life saver and I've taken it through two companies 
now.  I know that there are folks continuing to maintain Spacewalk, but with 
the official end of the project and the decision from IBM/Red Hat to  EOL 
CentOS 8 in a year; we are faced with the decision of what distro to move to 
(if we change at all).

Basically, I'm asking for your thoughts on distros and provisioning systems 
(like spacewalk) for an enterprise.  We have always been a CentOS house, but we 
are not CentOS/Red Hat "snobs"... we would definitely consider other 
distros well, maybe not Mint. :-)  It's all for server based applications, 
no desktop.

I guess it's pretty obvious, since we've been running the business on CentOS 
and Spacewalk, that cost is a definite consideration.

Thanks again for everyone's hard work!

Any recommendations would be GREATLY appreciated!

-Emmett

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

Re: [Spacewalk-list] SLES 12 SP5 package import

[William Hongach]

Thanks, Michael!  This was spot on and the patch fixed it.  SLES 12 SP5 
packages are now importing properly with rhnpush.

I appreciate the help.  I missed this post in my previous search of the 
archive.  Have a good weekend.


-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Michael Calmer
Sent: Friday, June 12, 2020 11:42 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] SLES 12 SP5 package import

[EXTERNAL EMAIL]

Hi

Maybe this?

  https://www.redhat.com/archives/spacewalk-list/2020-May/msg00036.html

Am Freitag, 12. Juni 2020, 15:23:48 CEST schrieb William Hongach:
> Hi Robert,
>
> There is no error on the command line when using rhnpush and the 
> packages do not make it into the channel.  There is, however, the 
> issue of certain packages (some not all) which will not upload and 
> timeout after three tries.  These timeouts are reported in the log as follows:
>
> 2020-06-12 09:15:13.400 EDT ERROR:  duplicate key value violates 
> unique constraint "rhn_pkg_clr_pid_cld_uq" 2020-06-12 09:15:13.400 EDT DETAIL:
> Key (package_id, changelog_data_id)=(173553, 492862) already exists.
> 2020-06-12 09:15:13.400 EDT STATEMENT:  insert into 
> rhnPackageChangeLogRec (package_id, changelog_data_id, id) values 
> (173553, 492862, 19335529)
>
> Thank you for your assistance in pointing me to the correct log file 
> to review.  Does anyone have an idea how to resolve this "duplicate 
> key value violates unique constraint" issue?  I have not seen this problem 
> before.
> Again, it is only happening with SLES 12 SP5 packages.  No other SLES 
> or RHEL repositories are having this issue on our Spacewalk system.
>
> I read a post in the archive that says "clearing the satellite sync cache"
> can resolve this but I do not know how to do that correctly.  Any 
> advice would be greatly appreciated.
>
> -Original Message-
> From: spacewalk-list-boun...@redhat.com 
> 
> On Behalf Of Robert Paschedag Sent: Thursday, June 11, 2020 2:53 AM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] SLES 12 SP5 package import
>
> [EXTERNAL EMAIL]
>
> Do you see any error when running the rhnpush or do the packages just 
> don't make it into the channel?
>
> You should take a look into the PostgreSQL logs in 
> /var/lib/pgsql/data/log and look for errors.
>
> Robert
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: William Hongach 
> Gesendet: Wed Jun 10 16:36:18 GMT+02:00 2020
> An: "spacewalk-list@redhat.com" 
> Betreff: [Spacewalk-list] SLES 12 SP5 package import
>
> Good Morning,
>
> Is anyone experiencing issues with pushing SLES 12 SP5 packages to 
> Spacewalk via rhnpush?  We stage our updates in a Spacewalk 2.8 server 
> and this is our first attempt to push SP5 updates but it does not 
> appear to work.  We are successfully pushing SLES 12 SP3, SP4, SLES 15 
> SP1 updates without issue.  The scripted process is the same for SP5 
> yet they cause a timeout during the POST process which then fails after three 
> attempts.
>
> Unfortunately, there are no error messages logged to 
> /var/log/httpd/ssl_error_log or error_log.  Has anyone seen this problem?
> Is there an alternate logging location that I should check to try to 
> view more detailed information about what is occurring?  Any insight 
> would be greatly appreciated.
>
>
>
> --
> --
>
> ___
> 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
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list


--
Regards

Michael Calmer

--
Michael Calmer
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg
T: +49 (0) 911 74053 0
F: +49 (0) 911 74053575  - e-mail: michael.cal...@suse.com
--
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG
Nürnberg)




___
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] SLES 12 SP5 package import

[William Hongach]

Hi Robert,

There is no error on the command line when using rhnpush and the packages do 
not make it into the channel.  There is, however, the issue of certain packages 
(some not all) which will not upload and timeout after three tries.  These 
timeouts are reported in the log as follows:

2020-06-12 09:15:13.400 EDT ERROR:  duplicate key value violates unique 
constraint "rhn_pkg_clr_pid_cld_uq"
2020-06-12 09:15:13.400 EDT DETAIL:  Key (package_id, 
changelog_data_id)=(173553, 492862) already exists.
2020-06-12 09:15:13.400 EDT STATEMENT:  insert into rhnPackageChangeLogRec 
(package_id, changelog_data_id, id) values (173553, 492862, 19335529)

Thank you for your assistance in pointing me to the correct log file to review. 
 Does anyone have an idea how to resolve this "duplicate key value violates 
unique constraint" issue?  I have not seen this problem before.  Again, it is 
only happening with SLES 12 SP5 packages.  No other SLES or RHEL repositories 
are having this issue on our Spacewalk system.

I read a post in the archive that says "clearing the satellite sync cache" can 
resolve this but I do not know how to do that correctly.  Any advice would be 
greatly appreciated.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Robert Paschedag
Sent: Thursday, June 11, 2020 2:53 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] SLES 12 SP5 package import

[EXTERNAL EMAIL]

Do you see any error when running the rhnpush or do the packages just don't 
make it into the channel?

You should take a look into the PostgreSQL logs in /var/lib/pgsql/data/log and 
look for errors.

Robert

⁣sent from my mobile device​


 Originale Nachricht 
Von: William Hongach 
Gesendet: Wed Jun 10 16:36:18 GMT+02:00 2020
An: "spacewalk-list@redhat.com" 
Betreff: [Spacewalk-list] SLES 12 SP5 package import

Good Morning,

Is anyone experiencing issues with pushing SLES 12 SP5 packages to Spacewalk 
via rhnpush?  We stage our updates in a Spacewalk 2.8 server and this is our 
first attempt to push SP5 updates but it does not appear to work.  We are 
successfully pushing SLES 12 SP3, SP4, SLES 15 SP1 updates without issue.  The 
scripted process is the same for SP5 yet they cause a timeout during the POST 
process which then fails after three attempts.

Unfortunately, there are no error messages logged to 
/var/log/httpd/ssl_error_log or error_log.  Has anyone seen this problem?  Is 
there an alternate logging location that I should check to try to view more 
detailed information about what is occurring?  Any insight would be greatly 
appreciated.





___
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

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

[Spacewalk-list] SLES 12 SP5 package import

[William Hongach]

Good Morning,

Is anyone experiencing issues with pushing SLES 12 SP5 packages to Spacewalk 
via rhnpush?  We stage our updates in a Spacewalk 2.8 server and this is our 
first attempt to push SP5 updates but it does not appear to work.  We are 
successfully pushing SLES 12 SP3, SP4, SLES 15 SP1 updates without issue.  The 
scripted process is the same for SP5 yet they cause a timeout during the POST 
process which then fails after three attempts.

Unfortunately, there are no error messages logged to 
/var/log/httpd/ssl_error_log or error_log.  Has anyone seen this problem?  Is 
there an alternate logging location that I should check to try to view more 
detailed information about what is occurring?  Any insight would be greatly 
appreciated.

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

Re: [Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk

[William Hongach]

Hello,

Not directly.  The method I use for SLES 12 and 15 is to sync the target repos 
to a local SMT server using smt-mirror, then use a scripted cron job to push 
these package updates to custom Spacewalk channels via rhnpush.  It's not 
elegant but it works as a staging process with granular control over what 
updates go to specific channels for testing in dev before being pushed to prod.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Alan Pittman
Sent: Thursday, January 16, 2020 8:51 AM
To: spacewalk-list@redhat.com
Cc: Spencer Chan 
Subject: [Spacewalk-list] syncing SLES15 and SLES15SP1 repos to Spacewalk


[EXTERNAL EMAIL]
Hi,
  Is anyone successfully syncing SLES 15 and SLES 15 SP1 repos from 
updates.suse.com to Spacewalk 2.8 (or 2.9)? If you are, can I compare notes 
with you please? I have been successfully syncing SLES11 and SLES12 repos for 
some time now, but haven't been able to  get a SLES 15 repo to sync. Suse 
support isn't any help. They will only verify the URL and userid/password.

Any help would sure be appreciated.

Alan

Alan Pittman
Publix Super Markets, Inc.
alan.pitt...@publix.com
1-863-686-8754 x46320

Unix is user friendly. It's just very selective about who its friends are.



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

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[William Hongach]

Hello,

The same holds true for SLES with respect to the 2.9 client as well.  The 2.8 
client made use of the rhnsd binary, whereas the 2.9 client uses systemd 
timers.  This is something that seems to have changed relatively quietly.

Have a good day.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Gerald Vogt
Sent: Wednesday, January 8, 2020 10:59 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[EXTERNAL EMAIL]

As Nicole Beck wrote before: on CentOS 7 there is no daemon anymore.
It's a systemd service with a systemd timer which calls rhn_check directly.

See

# systemctl list-timers
# systemctl status rhnsd.timer

-Gerald

On 08.01.20 16:53, Len Ewen wrote:
> Ok, so if I start the daemon, it checks in, then instantly dies. I 
> look at the osad file and nothing has updated and I cannot seem to 
> find a log file for rhnsd to see if something is going on there so 
> what am I missing?  I've removed and reinstalled the rhnsd package and 
> still have no luck.
>
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
>
>
> UIndyIT.jpg
>
> Confidentiality Notice: This communication and/or its content are for 
> the sole use of the intended recipient, and may be privileged, 
> confidential, or otherwise protected from disclosure by law. If you 
> are not the intended recipient, please notify the sender and then 
> delete all copies of it. Unless you are the intended recipient, your 
> use or dissemination of the information contained in this 
> communication may be illegal.
>
>
>
> On Wed, Jan 8, 2020 at 9:28 AM Len Ewen  > wrote:
>
> Ok, so why wouldn't the daemon be running?  I forced a check in by
> installing and removing a package, which seemed to work fine, but if
> it requires the daemon to be running constantly, I am assuming it
> won't check in again unless I force it?  I didn't do anything
> special to this box, I literally did a fresh minimal install and
> installed the spacewalk server on one box and the client on another
> to see if I could get it to work.
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
>
>
> UIndyIT.jpg
>
> Confidentiality Notice: This communication and/or its content are
> for the sole use of the intended recipient, and may be privileged,
> confidential, or otherwise protected from disclosure by law. If you
> are not the intended recipient, please notify the sender and then
> delete all copies of it. Unless you are the intended recipient, your
> use or dissemination of the information contained in this
> communication may be illegal.
>
>
>
> On Wed, Jan 8, 2020 at 9:21 AM Robert Paschedag
> mailto:robert.pasche...@web.de>> wrote:
>
> The daemon should be running. It should then check every
> interval minutes if something has to be done. See also within
> /etc/sysconfig/rhn/ for the interval. (Just right now know the
> name of the config file). The minimum interval is 60 minutes.
>
> Robert
>
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Len Ewen mailto:ew...@uindy.edu>>
> Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
> An: spacewalk-list@redhat.com 
> Betreff: Re: [Spacewalk-list] Spacewalk client not checking in
> on CentOS 7
>
> The rhnsd daemon isn't running, should it be constantly running
> or does it
> pause and then run again?  It is enabled, just not running.
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
> [image: UIndyIT.jpg]
>
> Confidentiality Notice: This communication and/or its content
> are for the
> sole use of the intended recipient, and may be privileged,
> confidential, or
> otherwise protected from disclosure by law. If you are not the
> intended
> recipient, please notify the sender and then delete all copies
> of it.
> Unless you are the intended recipient, your use or dissemination
> of the
> information contained in this communication may be illegal.
>
>
> On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka
> mailto:michael.mr...@redhat.com>>
> wrote:
>
>  > Len Ewen:
>  > > I know this a stupid noob question but I have a problem.
> I've got a
>  > clean
>  > > built, fresh out of the box spacewalk 2.9 server and a 2.9
> client.  The
>  > > client checked in once, but hasn't 

Re: [Spacewalk-list] Migrating from 2.7 to 2.9

[William Hongach]

Hello,

I can confirm that my 2.9 clients are checking in with the 2.8 server 
successfully.  I did notice a change in the frequency of rhn_check, however.  
It now uses rhnsd.timer which may account for the change in behavior that 
you're seeing.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Michael Mraka
Sent: Tuesday, July 2, 2019 8:29 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Migrating from 2.7 to 2.9

Paul Greene:
> I probably jumped the gun on the slow response rate of the remote 
> tasks I'd scheduled - they eventually did kick in
> 
> But, if anyone has some input on whether or not there's likely to be 
> an issue because I didn't update the clients, I'd eagerly appreciate 
> some feedback.
...
> > Maybe I'm overthinking it, but I'm wondering if not updating any of 
> > the client packages to 2.9 is going to cause any issues that aren't 
> > initially apparent. I tried to push out some remote commands to a 
> > group of 7 systems, and I usually start seeing some successful 
> > and/or failed actions within maybe 15 minutes or so, but it's been 
> > about an hour and a half now and there hasn't been any movement yet on the 
> > remote tasks.
> >
> > Can anyone think of any potential issues I might be running in to 
> > taking this route?

Generally Spacewalk server and clients of different version are compatible.
If not clients would complain in the log (during each rhn_check).
AFAIK there were no API change since 2.7.

Regards,

--
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.9 System Groups always show green check mark

[William Hongach]

Hello,

I experience the same issue with the 2.8 web interface.  It would appear to be 
a bug as the column is labeled "Updates" but only tracks Errata.  I would 
welcome a fix in 2.8 and 2.9 repositories.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Jay McCanta
Sent: Tuesday, June 25, 2019 2:06 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.9 System Groups always show green 
check mark

To clarify - There are groups with updates, but not errata that do not show 
different color icon in the Update column of the System Groups page.

From: Jay McCanta
Sent: Monday, June 24, 2019 12:37 PM
To: spacewalk-list@redhat.com
Subject: Spacewalk 2.9 System Groups always show green check mark

I our prior installation of spacewalk 2.6, the system groups pages rolled up 
the highest error into the system group icon.  Since we updated to spacewalk 
2.9, we are only seeing green checkmarks.  There are a number of groups with 
errata that are showing green.  In addition, the groups that only have patches 
used to show yellow, but now only show green.  Drilling into the group reveals 
the correct status.  The summary page is the only inconsistent page.  Looking 
for ideas on what to check to find this problem.


[https://cdn.f5.com/webcommon/email-signature/images/f5-logo-rgb-30x30.jpg]
 Jay McCanta  |  Principal Systems Administrator
 D +1 (206) 272-7998  M +1-206-434-1080


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

Re: [Spacewalk-list] Spacewalk in container

[William Hongach]

Hello,

I am curious to learn what specific benefits you are seeking to run in a 
container versus a traditional virtual machine given the usual Spacewalk model. 
 It seems like an interesting endeavor and perhaps a worthwhile discussion.


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Ananta Chakravartula
Sent: Tuesday, June 25, 2019 7:59 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk in container

Thanks Michael.

My main worry is to figure out what all files I have to mount in the container 
to keep the changes persistent on restart. Most of the articles I searched 
doesn't talk about it. They run sync commands directly inside the container 
without mounting any local volumes. I would imagine all the data is gone on 
container restart. I will check the links you sent.

Anyways, I got the answer. I think I will skip the container install for now.

Cheers,
ac

sent from my phone. Sory fer eny typeos

On Tue, Jun 25, 2019, 5:40 AM Michael Mraka 
mailto:michael.mr...@redhat.com>> wrote:
Ananta Chakravartula:
> Is it recommended/supported to run Spacewalk in a container?  What all
> locations I have to make persistent? I see data written to /var/satellite
> and /var/lib/pgsql. Are there any other places to keep in mind if I use
> every service of spacewalk?

Hello Ananta,

Spacewalk in container has not been tested / supported.
Some users tried and reported their progress:
https://jacobsalmela.com/2019/02/18/spacewalk-containerized-and-running-in-kubernetes/
http://egonzalez.org/spacewalk-red-hat-satellite-v5-in-a-docker-container-poc/

> Also, Is there any chance of updating the documentation with support of
> running Spacewalk in a Container?
> https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall
>
> Cheers,
> ac

Regards,

--
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] Best Practice for adding a child Channel?

[William Hongach]

Hello,

SSM can be managed from spacecmd.  You can add your systems using “spacecmd 
ssm_add” and then continue from there.  They can be added individually, by 
group, by channel or by search string.

You should have a look at “spacecmd help” or “man spacecmd” for details.  Its 
capabilities are quite extensive.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Guy Matz
Sent: Saturday, June 15, 2019 12:48 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Best Practice for adding a child Channel?

Thanks.  Would be nice if SSM could be managed from spacecmd . . .

On Tue, Jun 11, 2019 at 5:00 PM William Hongach 
mailto:william.hong...@marist.edu>> wrote:
Hello,

Add all of the target systems to the SSM as Robert suggested, then run the 
following from the server:

spacecmd system_addchildchannels ssm 

This should subscribe all of the systems currently in the SSM to the child 
channel that you specify by its label.  If you do not have the “spacecmd” CLI 
already installed on your system, you should be able to grab it from the 
Spacewalk repo for your distribution.  Hope this helps.

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Guy Matz
Sent: Tuesday, June 11, 2019 4:43 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Best Practice for adding a child Channel?

Hey!  Thanks for the reply!  I'm asking about the scenario in which a system is 
already registered and a new child channel is added . . .

On Tue, Jun 11, 2019 at 4:36 PM William Hongach 
mailto:william.hong...@marist.edu>> wrote:
Hello,

If the child channel is already associated with the activation key at the time 
of client registration, the client should subscribe to the base and child 
channels simultaneously if things are working correctly.  If you want to 
retroactively associate previously registered clients with a newly added child 
channel, I think you may have to script something to process this.  For 
example, you can make use of “spacecmd system_addchildchannels” to associate 
the system or system groups with the child channel.

I’m not sure if “Reactivation” within the GUI using the generated key would 
also work, but that is also a possibility to investigate.

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Guy Matz
Sent: Tuesday, June 11, 2019 4:21 PM
To: Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Best Practice for adding a child Channel?

Hi!  Is there a best way to add child channels?  I've added a channel, and made 
it a child channel in the "Activation Keys" section of the UI, but the channel 
does not show up on the client unless I add the child channel to the system.  
Is there a better way?  Am I missing something?

Thanks a lot,
Guy
___
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

Re: [Spacewalk-list] Is the rhnsd service required to be able to communicate with a spacewalk server?

[William Hongach]

Hello,

It is the service (or related timer) that runs rhn_check based on the interval 
specified in /etc/sysconfig/rhn/rhnsd.  This is how Spacewalk clients check in 
with the server for queued tasks.  There should be a man page available for 
rhnsd.

If you shut it down, the client will not check in with the server, unless 
rhn_check is run manually or via a scheduled task like cron.  However, if you 
run osad (I do not) then I do not believe you need it since that is a different 
model.  But your security team may also flag osad like they flagged rhnsd.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Paul Greene
Sent: Thursday, June 13, 2019 1:56 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Is the rhnsd service required to be able to 
communicate with a spacewalk server?

What is the actual function of rhnsd? What is actually being lost if its not 
running?

On Thu, Jun 13, 2019 at 1:02 PM William Hongach 
mailto:william.hong...@marist.edu>> wrote:
Hello,

I suppose you could run rhn_check out of cron if you did not want rhnsd to 
schedule it.

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Paul Greene
Sent: Thursday, June 13, 2019 12:31 PM
To: Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Is the rhnsd service required to be able to 
communicate with a spacewalk server?

Our security group is telling me, based on a Nessus scan, that I need to 
disable the rhnsd service.

Is the rhnsd service required to be able to communicate with a spacewalk server?
___
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

Re: [Spacewalk-list] Is the rhnsd service required to be able to communicate with a spacewalk server?

[William Hongach]

Hello,

I suppose you could run rhn_check out of cron if you did not want rhnsd to 
schedule it.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Paul Greene
Sent: Thursday, June 13, 2019 12:31 PM
To: Spacewalk-list@redhat.com
Subject: [Spacewalk-list] Is the rhnsd service required to be able to 
communicate with a spacewalk server?

Our security group is telling me, based on a Nessus scan, that I need to 
disable the rhnsd service.

Is the rhnsd service required to be able to communicate with a spacewalk server?
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Best Practice for adding a child Channel?

[William Hongach]

Hello,

Add all of the target systems to the SSM as Robert suggested, then run the 
following from the server:

spacecmd system_addchildchannels ssm 

This should subscribe all of the systems currently in the SSM to the child 
channel that you specify by its label.  If you do not have the “spacecmd” CLI 
already installed on your system, you should be able to grab it from the 
Spacewalk repo for your distribution.  Hope this helps.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Guy Matz
Sent: Tuesday, June 11, 2019 4:43 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Best Practice for adding a child Channel?

Hey!  Thanks for the reply!  I'm asking about the scenario in which a system is 
already registered and a new child channel is added . . .

On Tue, Jun 11, 2019 at 4:36 PM William Hongach 
mailto:william.hong...@marist.edu>> wrote:
Hello,

If the child channel is already associated with the activation key at the time 
of client registration, the client should subscribe to the base and child 
channels simultaneously if things are working correctly.  If you want to 
retroactively associate previously registered clients with a newly added child 
channel, I think you may have to script something to process this.  For 
example, you can make use of “spacecmd system_addchildchannels” to associate 
the system or system groups with the child channel.

I’m not sure if “Reactivation” within the GUI using the generated key would 
also work, but that is also a possibility to investigate.

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Guy Matz
Sent: Tuesday, June 11, 2019 4:21 PM
To: Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Best Practice for adding a child Channel?

Hi!  Is there a best way to add child channels?  I've added a channel, and made 
it a child channel in the "Activation Keys" section of the UI, but the channel 
does not show up on the client unless I add the child channel to the system.  
Is there a better way?  Am I missing something?

Thanks a lot,
Guy
___
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

Re: [Spacewalk-list] Best Practice for adding a child Channel?

[William Hongach]

Hello,

If the child channel is already associated with the activation key at the time 
of client registration, the client should subscribe to the base and child 
channels simultaneously if things are working correctly.  If you want to 
retroactively associate previously registered clients with a newly added child 
channel, I think you may have to script something to process this.  For 
example, you can make use of “spacecmd system_addchildchannels” to associate 
the system or system groups with the child channel.

I’m not sure if “Reactivation” within the GUI using the generated key would 
also work, but that is also a possibility to investigate.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Guy Matz
Sent: Tuesday, June 11, 2019 4:21 PM
To: Spacewalk-list@redhat.com
Subject: [Spacewalk-list] Best Practice for adding a child Channel?

Hi!  Is there a best way to add child channels?  I've added a channel, and made 
it a child channel in the "Activation Keys" section of the UI, but the channel 
does not show up on the client unless I add the child channel to the system.  
Is there a better way?  Am I missing something?

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

Re: [Spacewalk-list] FW: Spacewalk 2.9 clients

[William Hongach]

Hi Gerald,

Thank you for the clarification.  I see it being controlled by the system timer 
now.  Does this mean that /etc/sysconfig/rhn/rhnsd is no longer used i.e. rhnsd 
ignores this file now?


-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Gerald Vogt
Sent: Thursday, April 25, 2019 12:12 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] FW: Spacewalk 2.9 clients

2.9 is using a systemd timer which runs the rhnsd.service, i.e. rhn_check:

$ systemctl status rhnsd.timer
● rhnsd.timer - Spacewalk periodic check timer
Loaded: loaded (/usr/lib/systemd/system/rhnsd.timer; enabled; vendor
preset: disabled)
Active: active (waiting) since Tue 2019-04-16 09:17:42 CEST; 1 weeks
2 days ago

$ systemctl status rhnsd
● rhnsd.service - Spacewalk Server daemon
Loaded: loaded (/usr/lib/systemd/system/rhnsd.service; static; vendor 
preset: disabled)
Active: inactive (dead) since Thu 2019-04-25 16:23:01 CEST; 1h 47min ago
   Process: 113537 ExecStart=/usr/sbin/rhn_check (code=exited,
status=0/SUCCESS)
  Main PID: 113537 (code=exited, status=0/SUCCESS)

$ cat /usr/lib/systemd/system/rhnsd.timer
[Unit]
Description=Spacewalk periodic check timer

[Timer]
OnCalendar=00/4:00
RandomizedDelaySec=30min

[Install]
WantedBy=timers.target

-Gerald

On 25.04.19 18:05, William Hongach wrote:
> Hello again,
> 
> Following up on yesterday's inquiry regarding compatibility, I installed the 
> 2.9 client on a test SLES 12 SP4 machine.  This is my first experience with 
> 2.9 and I noticed something interesting.  Following the online Spacewalk 
> documentation, I installed all necessary packages for SLES successfully, 
> including rhnsd yet there is no rhnsd binary installed on the system.  Did 
> something go wrong with the install?
> 
> The 2.8 client package installed a binary /usr/sbin/rhnsd that started as 
> rhnsd.service under systemd.  This obviously called rhn_check at the 
> frequency detailed in /etc/sysconfig/rhn/rhnsd.  Our 2.9 installation of the 
> rhnsd package on SLES 12 SP4 did not install the binary nor is rhnsd.service 
> running.  The system is checking in at the expected frequency according to 
> the Spacewalk server, yet no scheduled tasks queued on the server are being 
> picked up by this client.  Running rhn_check manually picks up queued tasks.
> 
> I am looking for some feedback with someone familiar with the 2.9 client 
> install on SLES 12 SP4.  Is this a bug with the rhnsd package, problem with 
> installation, or perhaps things work differently now?  Thanks in advance.
> 
> 
> -Original Message-----
> From: spacewalk-list-boun...@redhat.com 
>  On Behalf Of William Hongach
> Sent: Wednesday, April 24, 2019 9:53 AM
> To: spacewalk-list@redhat.com
> Subject: [Spacewalk-list] Spacewalk 2.9 clients
> 
> Hello,
> 
> Can anyone confirm if Spacewalk 2.9 clients can communicate with a Spacewalk 
> 2.8 server?  I ask because we currently have a 2.8 environment, but we are 
> ready to deploy some SLES 12 SP4 servers.  The client available at 
> download.opensuse.org for SLES 12 SP4 is version 2.9.
> 
> The majority of our SLES environment remains SLES 12 SP3 at this time so we 
> would prefer to keep our Spacewalk server at 2.8 until we plan for a future 
> migration.  Any insight into the 2.9 client backwards compatibility would be 
> appreciated.  Thanks.
> 
> ___
> 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

[Spacewalk-list] Spacewalk 2.9 clients

[William Hongach]

Hello,

Can anyone confirm if Spacewalk 2.9 clients can communicate with a Spacewalk 
2.8 server?  I ask because we currently have a 2.8 environment, but we are 
ready to deploy some SLES 12 SP4 servers.  The client available at 
download.opensuse.org for SLES 12 SP4 is version 2.9.

The majority of our SLES environment remains SLES 12 SP3 at this time so we 
would prefer to keep our Spacewalk server at 2.8 until we plan for a future 
migration.  Any insight into the 2.9 client backwards compatibility would be 
appreciated.  Thanks.

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

Re: [Spacewalk-list] Spacewalk Postgres database

[William Hongach]

Hi,

You can back up the database using:

db-control online-backup $filename

And this Perl script should pull in the credentials that Robert referenced in 
your /etc/rhn/rhn.conf file.  There should be no need to log into the postgres 
database manually.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Elizabeth Graf
Sent: Tuesday, April 9, 2019 10:58 AM
To: Spacewalk-list 
Subject: [Spacewalk-list] Spacewalk Postgres database

I was looking at instructions for upgrading our spacewalk 2.7 instance and the 
instructions stressed backing up the database.  Problem is when I installed 
spacewalk I let it install itself and it created the database with no input 
from me.  So I don’t know what user I could login as to do backups.  Does 
anyone know if this automated install uses a generic username/password?  I 
followed the how to install page on github to let spacewalk setup Postgres.

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

Re: [Spacewalk-list] Help with Visually Identifying a Spacewalk Server

[William Hongach]

An alternative that I prefer would be to modify spacewalk.css on each server to 
place an image or name value relating to the specific server in the header 
class.  This way that change would propagate to every page within the Spacewalk 
portal as feedback to the user regarding which server they were interacting 
with.

A basic modification to a page header or site header should suffice.  Hope that 
helps.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Larry Clegg
Sent: Wednesday, March 20, 2019 6:27 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Help with Visually Identifying a Spacewalk Server

Greetings Spacers:

Base OS:  Centos 7.6
Spacewalk: 2.9

I have multiple Spacewalk servers in various data centers.  I am trying to 
figure out a way to visually identify a SW server in the GUI.

Here’s the dilemma:  a user goes to a URL like 
spacewalk.us3.cloud.kyriba.com and is 
presented the standard SW login screen.  Nowhere on that screen does it 
indicate the name of the server, e.g. spacewalk.us3. The user may have typo’d 
and gone to 
spacewalk.us2.cloud.kyriba.com by 
mistake. Unless they are paying close attention to the URL then they may be on 
the wrong server.

I would like the “Welcome to Spacewalk” on the main login page to say something 
like “Welcome to the US3 Spacewalk Server”……to better visually identify the 
specific server.

So far I have not found a solution to this.  Anyone have an idea?

Thanks

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

Re: [Spacewalk-list] New to Spacewalk and Linux

[William Hongach]

Welcome,

I cannot answer any specifics regarding Oracle Linux as I do not have that 
distribution in our Spacewalk environment, but here is a link to the Spacewalk 
user documentation which you may find useful regarding its features:

https://spacewalkproject.github.io/documentation.html


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Jason Ferris
Sent: Wednesday, March 20, 2019 10:14 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] New to Spacewalk and Linux

Hello,

I apologize for being a newb but I've been tasked to setup a Linux patching 
system and Spacewalk seemed like a solution I could manage. I'm a fairly green 
Linux admin and am not an expert on Linux systems.

Our environment consists of Oracle Enterprise Linux systems. I setup spacewalk 
2.9 on a fresh install of Oracle Enterprise Linux UEK. And used the directions 
from this page 
https://oracle-base.com/articles/linux/spacewalk-installation-on-oracle-linux#server-prerequisites

Now that I have a GUI I have many questions about what the options mean on the 
pages etc. Is there anything that can explain what these options are in 
specifics? Also I guess I'm wondering if this is going to work with our 
environment since we use Oracle Enterprise Linux UEK.. Or do I need to 
revert to using Ksplice?

Thank you for any help!
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Queueing a hardware refresh

[William Hongach]

Good Morning All,

I noticed something interesting in the web gui of our Spacewalk 2.8 server.  
I'm actually surprised that I did not notice it sooner.  If I change the IP 
address of a client, this change is not reflected in Systems > Details > 
Overview > System Info.  This same outdated information for network interfaces 
is also reflected on the Hardware > Networking tab as well.  

Our clients check in hourly but this information is not getting updated on the 
server.  For some reason I assumed it would, but this is not the case because 
the check in is only looking for scheduled tasks.  I discovered that I needed 
to visit the Hardware tab and click "Schedule Hardware Refresh" to queue a push 
of this information from the client.

This can also be accomplished on the command line using "spacecmd 
system_schedulehardwarerefresh" so I leave this here as a tip for our newer 
users after stumbling upon the issue myself.  Have a good day.

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

Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

[William Hongach]

Hi Harald,

Do you have SELinux enabled on these systems?  If so, have you verified that 
rhn_check has the correct context and it is allowed to run?  Check the 
audit.log on these systems for details.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Wachauer Harald
Sent: Wednesday, February 13, 2019 11:18 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi  all,

I have the problem that most of my systems (CentOS 6 & 7) are going offline 
after approximately one day.
Only if I run rhn_check the systems come online again, but only for short time.

I have tried to install osad service, the service is running but nerveless the 
client is going offline.

Any help would be very appreciated.


Best regards,

Harald






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

Re: [Spacewalk-list] Spacewalk and Ubuntu

[William Hongach]

Hi Robert,

Thank you very much for taking the time to send along this information.  I was 
able to successfully register and manage Debian 9 clients using the details you 
have provided.  Have a great day.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Robert Paschedag
Sent: Sunday, January 6, 2019 10:49 AM
To: spacewalk-list@redhat.com; James Krych 
Subject: Re: [Spacewalk-list] Spacewalk and Ubuntu

On 1/4/19 6:06 PM, James Krych wrote:
> Thanks William!
> 
> I have figured as much. Nothing on youtube either!
> 
> Best,
> 
> James
> 
https://www.redhat.com/archives/spacewalk-list/2018-September/msg00059.html

This messages point to a custom "repo" for Debian / Ubuntu clients with the 
"latest" (2.8) spacewalk tools needed.

Thenthe things needed are the same as for every other distribution.

You need

 - the tools (packages).
 - the CA certificate of your spacewalk server. (The certificate, that "signed" 
the cert of the spacewalk "web server"! This is the RHN-TRUSTED-ORG-SSL.CERT 
file that should be found within
/var/www/html/pub/)
 - an activation key for the systems you want to register. This activation key 
should "contain" the "channels", that clients should subscribe, when they 
register with this specific "activation key"
 - channels: of course you need to create "software channels" for your Ubuntu 
clients (where you sync the packages to)

Normally, ("traditional xmlrpc clients") there are so called "boostrap scripts" 
created by the spacewalk server which are used on a client to

 - get all needed packages from a "bootstrap repo" needed to get in touch with 
the spacewalk server
 - download the CA certificate to verify SSL/TLS certificates
 - register the system with a - possibly - predefined "activation key"

For Ubuntu / Debian, these default bootstrap scripts do not work. You have to 
create your own.

I describe the steps (from my mind) you need to do on "one" test client.

- Add the repo as mentioned in the old spacewalk mailing archive message 
(mentioned above) to your client (so you are able to install the needed 
spacewalk packages). Make sure, you are able to reach the main Ubuntu repos.

- Download the CA certificate (RHN-TRUSTED-ORG-SSL-CERT file) from the 
spacewalk server and "install" it as "trusted CA certificate" on the system. 
The instructions vary from distro to distro. See 
http://manpages.ubuntu.com/manpages/trusty/man8/update-ca-certificates.8.html
for Ubuntu

- Test the connection (so SSL/TLS communication works as expected) buy running 
something like "curl -v https://". If you get SSL 
verification errors, fix the error. Nothing will work, until this works.

- If not yet present, create an "activation key" within spacewalk server and 
add the "channels" you want the new client to subscribe automatically (I use 
the name "1-ubuntu18" here for example)

- Install the needed packages (read mentioned archive message above)

- Register the system with "rhnreg_ks --activationkey=1-ubuntu18 
--serverUrl=https:///XMLRPC"

That should be it.

Robert

> --
> --
> James W. Krych
> CCNP, CCNA, Net+, Security+, A+, Linux+
> Mobile: 843-847-1446
> james.w.kr...@gmail.com
> 
> 
> On Fri, Jan 4, 2019 at 11:56 AM William Hongach 
> 
> wrote:
> 
>> Hi James,
>>
>>
>>
>> I posted a similar inquiry a few weeks ago.  I have difficulty 
>> getting Debian clients to play nicely with Spacewalk and I haven’t 
>> found an over abundance of related documentation online for managing 
>> Debian/Ubuntu.  From previous list traffic, I know we have some 
>> active users out there, so if anyone can weigh in with tips or a 
>> documented process for managing updates, configuration files, remote 
>> commands, etc. or any of the other relevant Spacewalk features, it would be 
>> greatly appreciated.
>>
>>
>>
>> *From:* spacewalk-list-boun...@redhat.com < 
>> spacewalk-list-boun...@redhat.com> *On Behalf Of *James Krych
>> *Sent:* Friday, January 4, 2019 8:39 AM
>> *To:* spacewalk-list@redhat.com
>> *Subject:* [Spacewalk-list] Spacewalk and Ubuntu
>>
>>
>>
>> First, my apologies if this has been beaten to death.
>>
>>
>>
>> I did some preliminary research about this and did find some sites 
>> that had up to Ubuntu 16.04 LTS listed as being able to utilize 
>> Spacewalk. Is there a collection of steps that shows how this can be 
>> done -- especially with Ubuntu 18 now?
>>
>>
>>
>> Very respectfully,
>>
>>
>>
>> James
>>
>>
>>
>> --
>> --
&

Re: [Spacewalk-list] Spacewalk and Ubuntu

[William Hongach]

Hi James,

I posted a similar inquiry a few weeks ago.  I have difficulty getting Debian 
clients to play nicely with Spacewalk and I haven’t found an over abundance of 
related documentation online for managing Debian/Ubuntu.  From previous list 
traffic, I know we have some active users out there, so if anyone can weigh in 
with tips or a documented process for managing updates, configuration files, 
remote commands, etc. or any of the other relevant Spacewalk features, it would 
be greatly appreciated.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of James Krych
Sent: Friday, January 4, 2019 8:39 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk and Ubuntu

First, my apologies if this has been beaten to death.

I did some preliminary research about this and did find some sites that had up 
to Ubuntu 16.04 LTS listed as being able to utilize Spacewalk. Is there a 
collection of steps that shows how this can be done -- especially with Ubuntu 
18 now?

Very respectfully,

James

--
--
James W. Krych
CCNP, CCNA, Net+, Security+, A+, Linux+
Mobile: 843-847-1446
james.w.kr...@gmail.com
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Managing Debian

[William Hongach]

Good Afternoon,

I am currently managing RHEL and SLES within Spacewalk, but I would like to 
expand this to Debian clients as well.  I did some initial research and I have 
discovered documentation that is either out of date or expired/broken links.

Can someone direct me to useful, reasonably up-to-date documentation regarding 
Spacewalk package installation and registration of Debian clients?  Thanks in 
advance.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] remove package in spacewalk repo

[William Hongach]

Hello,

To clarify, are you referring to packages that have been downloaded locally and 
pushed to Spacewalk?  If so, an unwanted package that is no longer part of a 
software channel can be listed and removed as follows:

spacecmd package_listorphans
spacecmd package_removeorphans

This will check for dependencies and remove it from both the Spacewalk database 
as well as the filesystem.  You can also check the filesystem against the 
database and vice versa as follows:

spacewalk-data-fsck -f
spacewalk-data-fsck -d

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Jérôme Meyer
Sent: Thursday, December 13, 2018 11:16 AM
To: 'spacewalk-list@redhat.com' 
Subject: [Spacewalk-list] remove package in spacewalk repo

Hi,

It is possible to remove unwanted package in spacewalk repository?
In my dev-epel channel there's a package that is no longer available 
(libmspack-0.7).

Could I delete it? Can it result a dependency problem?...and how to do that?

Thank in advance
Regards,
J.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Patch notifications and logs

[William Hongach]

Hello,

Have you checked to see if this is an selinux issue?  If you have selinux set 
to enforcing, you can look for messages relating to rhnsd and rhn_check in 
/var/log/audit/audit.log.

The context for rhnsd should be rhnsd_exec_t and rhn_check should be rpm_exec_t.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Ventrapragada, Anand
Sent: Monday, December 10, 2018 8:52 AM
To: 'spacewalk-list@redhat.com' 
Subject: [Spacewalk-list] Patch notifications and logs

Hello spacewalk Team-

When I am patching RHEL 7 nodes using  spacewalk UI , patch process is getting 
into pending state for a longer time.

-Is there any way to find out the insights, what exactly is happening 
during the process(Im looking for somewhere we can  find logs for this)

-Is there any way we can initiate  automatic mail alerts before 
patching process to start and after the completion of patching 
process(success/Failure )

Thanks
Anand vamsi.






DISCLAIMER: This e-mail message and any attachments are intended solely for the 
use of the individual or entity to which it is addressed and may contain 
information that is confidential or legally privileged. If you are not the 
intended recipient, you are hereby notified that any dissemination, 
distribution, copying or other use of this message or its attachments is 
strictly prohibited. If you have received this message in error, please notify 
the sender immediately and permanently delete this message and any attachments.


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

Re: [Spacewalk-list] Metadata backups

[William Hongach]

Hi Michael,

Thank you for the prompt reply.  I was not aware db-control but this is exactly 
what I was looking for.  I will read up further on its usage.  Have a great day.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Michael Mraka
Sent: Wednesday, December 5, 2018 9:25 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Metadata backups

William Hongach:
> Good Morning,
> 
> I am looking to back up the pgsql database that stores Spacewalk metadata.  I 
> used most (if not all) of the default options upon installation, and I want 
> to make sure that I dump the correct databases during back up.
> 
> Will a dump of the "postgres" and "rhnschema" databases be sufficient for 
> recovery if we need to restore the Spacewalk metadata to a specific point in 
> time?  The physical file system that Spacewalk uses is already being backed 
> up.
> 
> Should template0 and template1 also be backed up?  Thanks in advance.

Hello William,

Spacewalk contains 'db-control' script for database manipulation. You can just 
use
  # db-control backup /backupdir
or
  # db-control online-backup  /backupdir/dbbackup.dump

and
  # db-control restore /backupdir/dbbackup.dump


Regards,

--
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] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 Servers

[William Hongach]

Hi Jeff,

Yes, it is a two-step process but it is a workaround to the Spacewalk server 
not having the subscription to other distributions (or even major releases).  
For example, if your Spacewalk server is RHEL 7, and you want to download/push 
RHEL 6 packages using a local machine you can script the following:

Download:
Create a local directory
reposync –n –repoid=rhel-6-server-rpms
reposync –n –repod=rhel-6-server-optional-rpms

Push:
rhnpush –v –channel=$CHANNEL –server=http://$SERVER/APP –dir=./local-dir

My cron job runs this monthly since that is the anticipated patch frequencey 
for our test and dev servers.  While our software channels are created ahead of 
time, you can script creation of these channels before the push as well, using 
the “spacecmd softwarechannel_create” command.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Irwin, Jeffrey
Sent: Tuesday, November 27, 2018 9:09 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers


​HTH,

That sounds better than my solution by far.  Well, same solution but more 
streamlined.  So you do a reposync using a script, then use rhnpush to push to 
satellite?  Is that right?



Jeff




From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of William Hongach 
mailto:william.hong...@marist.edu>>
Sent: Tuesday, November 27, 2018 9:03 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Phil,

I use Spacewalk to centrally manage multiple distributions and different major 
releases within each distribution, as you are seeking to accomplish.  
Understanding that the Linux server running Spacewalk would not have access to 
all of the different proprietary subscriptions, this was achieved by setting up 
repository download servers for each distribution/release that required a 
separate subscription.  Updates are downloaded by a scripted cron job on each 
local repo server and pushed to the central Spacewalk server using rhnpush.

To script update downloads on a local repo server, the reposync command can be 
used for RHEL, the smt-mirror command can be used for SUSE, etc.  With this 
method, you do not need to worry about URLs.  You can download repositories by 
their ID/name.

HTH.

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
Sent: Tuesday, November 27, 2018 4:17 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Jeffrey

Thanks for your reply. It seems I would have been better off by starting with 
installing Spacewalk on a RHEL 7 server rather than an OL 7 server then? Can 
you just clarify/confirm what URL’s you’ve configured for the RHEL 6/7 
repositories please (obviously, for the RHEL 6 local, just take out any 
sensitive information)?

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com<mailto:jeffrey.ir...@rivertechllc.com>
Sent: 26 November 2018 19:58
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers


I have been able to do this by building a rhel 6 server and creating a local 
repo mirror.  I then created a rhel 7 and installed spacewalk.  That way i have 
the entitlements for rhel 6 and 7 covered.  From there, I set up the channels 
and pointed the rhel 7 to the redhat network, and the rhel 6 was pointed to my 
local repo server.  I can now get all the rhel 6 and 7 patches into spacewalk.


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
mailto:p.cook...@bham.ac.uk>>
Sent: Monday, November 26, 2018 7:20 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [EXTERNAL] [Spacewalk-list] Spacewalk 2.8 - Patching RHEL 6/7 Servers

Good afternoon

I’m currently looking in to options for introducing a single centralised 
patching solution for both Oracle Linux 6/7 and RHEL 6/7 systems. There are 
about 100 Oracle Linux servers and 50 RHEL servers. I’m starting with the 
Spacewalk product and therefore, built a proof of concept environment by 
installing Spacewalk 2.8 on an Oracle 7 system. Subsequently, I’ve added 
channels/repositories for Oracle 6/7 and successfully patched a number of test 

Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 Servers

[William Hongach]

Hi Phil,

I use Spacewalk to centrally manage multiple distributions and different major 
releases within each distribution, as you are seeking to accomplish.  
Understanding that the Linux server running Spacewalk would not have access to 
all of the different proprietary subscriptions, this was achieved by setting up 
repository download servers for each distribution/release that required a 
separate subscription.  Updates are downloaded by a scripted cron job on each 
local repo server and pushed to the central Spacewalk server using rhnpush.

To script update downloads on a local repo server, the reposync command can be 
used for RHEL, the smt-mirror command can be used for SUSE, etc.  With this 
method, you do not need to worry about URLs.  You can download repositories by 
their ID/name.

HTH.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of p.cook...@bham.ac.uk
Sent: Tuesday, November 27, 2018 4:17 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Jeffrey

Thanks for your reply. It seems I would have been better off by starting with 
installing Spacewalk on a RHEL 7 server rather than an OL 7 server then? Can 
you just clarify/confirm what URL's you've configured for the RHEL 6/7 
repositories please (obviously, for the RHEL 6 local, just take out any 
sensitive information)?

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com
Sent: 26 November 2018 19:58
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers


I have been able to do this by building a rhel 6 server and creating a local 
repo mirror.  I then created a rhel 7 and installed spacewalk.  That way i have 
the entitlements for rhel 6 and 7 covered.  From there, I set up the channels 
and pointed the rhel 7 to the redhat network, and the rhel 6 was pointed to my 
local repo server.  I can now get all the rhel 6 and 7 patches into spacewalk.


From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk 
mailto:p.cook...@bham.ac.uk>>
Sent: Monday, November 26, 2018 7:20 AM
To: spacewalk-list@redhat.com
Subject: [EXTERNAL] [Spacewalk-list] Spacewalk 2.8 - Patching RHEL 6/7 Servers

Good afternoon

I'm currently looking in to options for introducing a single centralised 
patching solution for both Oracle Linux 6/7 and RHEL 6/7 systems. There are 
about 100 Oracle Linux servers and 50 RHEL servers. I'm starting with the 
Spacewalk product and therefore, built a proof of concept environment by 
installing Spacewalk 2.8 on an Oracle 7 system. Subsequently, I've added 
channels/repositories for Oracle 6/7 and successfully patched a number of test 
client systems.
However, I can't seem to obtain clear instructions for how to patch RHEL 6/7 
systems using Spacewalk. I believe the functionality of Red Hat Satellite and 
Spacewalk is basically the same but the ability to connect directly to RHN to 
synchronize software repositories and errata's has been disabled. I've seen 
some tentative clues that this can be circumvented as well as some reference to 
using "mrepo" but the latter just seems over complicated really.

Alternatively, if Red Hat Satellite is purchased to patch the RHEL 6/7 servers, 
has anyone had success with using it to patch Oracle 6/7 servers?

In addition to patching, I also need to investigate their provisioning 
capabilities too.

Regards
Phil

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

Re: [Spacewalk-list] Missing RPMs for SLE_15

[William Hongach]

Hi Michael,

The python3 packages (noarch) installed successfully and I am now able to 
manage SLES 15 nodes via Spacewalk 2.8 on s390x architecture.  Thank you for 
your assistance.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Michael Calmer
Sent: Wednesday, September 12, 2018 4:14 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15

Hi

I think it should be fixed now and you just need to wait a bit until the 
rebuild is finished and the repo is published.

Am Mittwoch, 12. September 2018, 09:27:00 CEST schrieb Klaus Kaempf:
> * William Hongach  [Sep 11. 2018 14:21]:
> > Hi Klaus,
> > 
> > Any progress on the python3-usix libraries?  If I can assist with 
> > testing, let me know.
> The Uyuni team is working on it and should be finished by end of this 
> week.
> 
> Klaus


--
Regards

Michael Calmer

--
Michael Calmer
SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg
T: +49 (0) 911 74053 0
F: +49 (0) 911 74053575  - e-mail: michael.cal...@suse.com
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
 HRB 21284 (AG Nürnberg)




___
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] Missing RPMs for SLE_15

[William Hongach]

Klaus,

Sounds good.  Thanks for the update!

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Klaus Kaempf
Sent: Wednesday, September 12, 2018 3:27 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15

* William Hongach  [Sep 11. 2018 14:21]:
> Hi Klaus,
> 
> Any progress on the python3-usix libraries?  If I can assist with testing, 
> let me know.

The Uyuni team is working on it and should be finished by end of this week.

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 
(AG Nürnberg)

___
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] Missing RPMs for SLE_15

[William Hongach]

Hi Klaus,

Any progress on the python3-usix libraries?  If I can assist with testing, let 
me know.


-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Klaus Kaempf
Sent: Friday, August 31, 2018 2:33 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15

The python3-newt dependency is already fixed. Building -usix for
python3 needs a bit more work and should be ready sometime next week.

Klaus
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 
(AG Nürnberg)

___
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] Missing RPMs for SLE_15

[William Hongach]

Hi Klaus,

Sounds great.  I will check back next week and let you know when it is tested 
successfully on our system.

Thank you!

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Klaus Kaempf
Sent: Friday, August 31, 2018 2:33 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15

* William Hongach  [Aug 30. 2018 15:20]:
> 
> Will these fixes be uploaded to the Spacewalk 2.8 repo at 
> download.opensuse.org, or will they be slated for the future release of 
> Spacewalk 2.9?  Let me know if I can assist with testing.  Thanks.
> 

The python3-newt dependency is already fixed. Building -usix for
python3 needs a bit more work and should be ready sometime next week.

Klaus
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 
(AG Nürnberg)

___
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] Missing RPMs for SLE_15

[William Hongach]

Hi Klaus,

No worries.  SLE_15 is sufficiently new that we expected some issues with open 
source packages.  We are currently still in the testing phase with regards to 
our SLE_15 image.  

Will these fixes be uploaded to the Spacewalk 2.8 repo at 
download.opensuse.org, or will they be slated for the future release of 
Spacewalk 2.9?  Let me know if I can assist with testing.  Thanks.


-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Klaus Kaempf
Sent: Thursday, August 30, 2018 3:34 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15

* William Hongach  [Aug 28. 2018 20:36]:

> Problem: nothing provides python3-spacewalk-usix needed by 
> python3-rhncfg-5.10.122-4.2.noarch

That's another packaging bug since there's no python3-variant being build.

Sorry for the mess.

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 
(AG Nürnberg)

___
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] Missing RPMs for SLE_15

[William Hongach]

Hi Javier,

I am guessing the python3-spacewalk-usix issue only affects rhncfg as you have 
discovered.  The rest of the suite probably works fine.  Unfortunately, we make 
use of Spacewalk's configuration management so I will need to get it working.  
I considered changing the spec file's requirements for SUSE and rebuilding 
rhncfg with python2, but it looks like Klaus is working on a fix.  So I am 
hopeful we can get this worked on using python3 going forward.


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Flores, Javier (D4\INF\IT ID)
Sent: Wednesday, August 29, 2018 3:50 AM
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15

Hi William

I ran into similar issues and decided to build the packages for SLES 15 by 
myself.

Yes, newt-python3 should be python3-newt. Not sure, but I guess Red Hat and 
Suse have different naming conventions for packages. This is easy to fix in the 
.spec file

The spacewalk-usix rpm was built with python2-spacewalk-usix. However, I didn't 
install these packages and was able to register my SLES 15 system and work with 
it as usual. I am not saying this packages are unnecessary, they just might be 
needed for spacewalk functionality I don't use.

Regards,
Javier

Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Dienstag, 28. August 2018 22:35
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: [Spacewalk-list] Missing RPMs for SLE_15

Hi All,

I'm trying to install/build Spacewalk 2.8 for SLE_15 running on s390x.  Most of 
the RPMs in noarch and/or src get the job done, but I am missing two in 
particular as follows:

2 Problems:
Problem: nothing provides newt-python3 needed by 
python3-rhn-setup-2.8.25-3.5.noarch
Problem: nothing provides python3-spacewalk-usix needed by 
python3-rhncfg-5.10.122-4.2.noarch

I'm using the standard repo at: 
http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8/SLE_15/

I noticed that the server has the "python3-newt" package installed, so the 
first error might be a typo in the dependency that it is checking (server also 
has full newt package installed).  However, I definitely cannot locate a source 
RPM or noarch RPM for python3-spacewalk-usix.

I do have python2-spacewalk-usix installed.  Will this suffice?  If not, can 
someone point me in the right direction to obtain the python3 version?  It 
seems like our SLE_12 servers were happy using the python2 libraries, but 
SLE_15 wants to use the python3 libraries for all of these Spacewalk 2.8 RPMs.

Any assistance would be greatly appreciated.  I understand most of the SLE 
binaries will be for x86_64, so I'm happy to obtain the source RPMs and build 
our own for s390x.

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

Re: [Spacewalk-list] rhncfg-actions in SW 2.8?

[William Hongach]

Hello,

This may depend on what distribution you are using.  For example, I can confirm 
that the spacewalk-client 2.8 repo has the rhncfg-actions package for RHEL 6, 
RHEL 7 and SLES 12 (noarch), but not sure about other distros.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Guy Matz
Sent: Thursday, July 26, 2018 2:28 PM
To: Spacewalk-list@redhat.com
Subject: [Spacewalk-list] rhncfg-actions in SW 2.8?

Hi!  I have a bunch of servers with SW 2.7 client installed, which includes 
rhncfg-actions . . .  Looking at the SW 2.8 repo I don't see rhncfg-actions, 
and when I install SW 2.8 client on a server I see in the SW server UI for that 
machine, under Remote Command:
You must enable Remote Command execution on the target system by installing the 
rhncfg-actions RPM.
How do I get Remote Commands to work under 2.8?  Is there an equivalent package 
under 2.8 that I should be installing instead?
Thanks!!
Guy
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.8 clients not checking in

[William Hongach]

Hi Jason,

The check-in interval is controlled by the INTERVAL variable in 
/etc/sysconfig/rhn/rhnsd.  By default, I believe it is set to INTERVAL=240 (4 
hrs).  Have you checked this value on the affected clients to determine if it 
is behaving as configured?

I believe rhnsd will -not- check in at reboot, unless you configure it to do so 
(rhn_check in crontab, etc.).  It will check in at rhnsd_start_time + interval. 
 This is the behavior I have observed with 2.8.

Hope this helps.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Jason W. Lewis
Sent: Wednesday, July 18, 2018 4:36 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.8 clients not checking in

Hi All,

I just upgraded to 2.8 (server and some clients) and now the clients that have 
been upgraded aren’t checking in anymore.  I’ve tried restarting the rhnsd 
service, even rebooted the system, and still nothing.  I’ve looked at 
/var/log/up2date, and there’s no activity since the time rhnsd was last 
started.  It looks like rhn_check just isn’t getting run.  I ran it manually 
and the system checked in and picked up the chain I had waiting for it.

Is anyone familiar with this enough to provide a solution, or at least know 
enough to help me get started troubleshooting this?

Thank you,
--
Jason Lewis
Senior Systems Engineer @Micro Electronics, Inc.
P: 614.777.2728 | M: jwle...@microcenter.com


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

[Spacewalk-list] OpenSCAP scanning for SLES

[William Hongach]

Hi All,

I ran into a snag getting OpenSCAP scanning to work for our SLES 12SP3 clients. 
 I ran "zypper install spacewalk-oscap" and receive the following error:

"Problem: nothing provides openscap-scanner needed by 
spacewalk-oscap-2.8.8-4.1.noarch"

Our architecture is s390x so it is using the noarch RPM which seems to be 
missing this "openscap-scanner" dependency.  I also receive the same error 
message if I try to install the python2-spacewalk-oscap.

I have the following SUSE packages already installed on the same client, but 
this does not help:

openscap, openscap-content, openscap-utils, libopenscap8

The SUSE packages above include the "oscap" binary to run scans from the CLI on 
the client, but the Spacewalk server does not recognize the SLES clients' 
ability to run scans without the spacewalk-oscap package being installed.  
Therefore, the workaround is to install the SUSE openscap packages (including 
openscap-utils) first, then force the installation of spacewalk-oscap without 
resolving the dependency.

Going forward, I think the noarch build should look for either openscap-scanner 
(RHEL specific?) OR openscap-utils (SUSE) dependency during installation and 
that should avoid user confusion.

With the following workaround, OpenSCAP scanning works successfully for 
Spacewalk 2.8 and SLES 12 clients:

---
zypper install openscap openscap-content openscap-utils libopenscap8
zypper install spacewalk-oscap

Refreshing service 'spacewalk'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides openscap-scanner needed by 
spacewalk-oscap-2.8.8-4.1.noarch
Solution 1: do not install spacewalk-oscap-2.8.8-4.1.noarch
Solution 2: break spacewalk-oscap-2.8.8-4.1.noarch by ignoring some of its 
dependencies

Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following 2 NEW packages are going to be installed:
  python2-spacewalk-oscap spacewalk-oscap
---

Hope this helps others who encounter the same issue with the noarch builds.  
Comments/feedback welcome.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Adding SLE_SP3 client

[William Hongach]

Hi Javier,

Thank you for providing this repo.  I can confirm that it works well for the 
s390x architecture.  After successfully installing the client tools, I was able 
to register SLES12 clients with the Spacewalk server and send updates to them.  
This satisfies a proof of concept so I will pursue your advice on building a 
repo for our architecture.

Thank you also for this recommendation.  I will have to start from scratch 
learning OBS, but I believe it will serve us well going forward on this 
architecture.


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Flores, Javier (D4\INF\IT ID)
Sent: Friday, June 29, 2018 8:53 AM
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Adding SLE_SP3 client

Hi William

I had a couple of spare minutes and managed to create the x390 RPMs on OBS.

https://download.opensuse.org/repositories/home:/floritto:/spacewalk-client-2.8/SLE_12_SP3/

I don't if it works as I don't have any x390 systems, but give it a try.

Keep in mind, this is just a quick and dirty build. For production use you 
should really build the packages by yourself.

Regards,
Javier

Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Flores, Javier 
(D4\INF\IT ID)
Gesendet: Donnerstag, 28. Juni 2018 16:15
An: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Betreff: Re: [Spacewalk-list] Adding SLE_SP3 client

Hi William

python2-newt contains a binary file, that is why it is only available for 
x86_64. So, you will have to create all packages containing binaries for x390 
by yourself.

You can either get the source RPMs and build the x390 RPMs on a local system 
with rpmbuild or you can try to build the packages on the openSUSE Build 
Service (OBS).

I just recently started using the OBS and I think that is the better way to go. 
However, it takes some time to understand how everything works.

Regards,
Javier

Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Donnerstag, 28. Juni 2018 15:15
An: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Betreff: Re: [Spacewalk-list] Adding SLE_SP3 client


Hi Javier,



I am pointed to that repository as per the doc for registering SLE12_SP3 
clients found at: 
https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients



However, my SLES is on s390x architecture so zypper is looking at the noarch 
packages.  When I run "zypper install rhn-client-tools" it reports the 
following:



"Problem: nothing provides python-newt needed by 
python2-rhn-client-tools-2.8.25-3.1.noarch"



I see that python2-newt is provided for x86_64 architecture, but nothing for 
noarch packages, and I don't see it included in the source packages either so 
I'm a bit stumped.


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Flores, Javier (D4\INF\IT ID) 
mailto:javier.flo...@gmz.migros.ch>>
Sent: Thursday, June 28, 2018 3:12:37 AM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Adding SLE_SP3 client


Hi



Which repository at opensuse.org are you using?



You can find all the needed packages including python2-newt in this repository:

https://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8/SLE_12_SP3/



Other versions of the spacewalk client can be found here:

https://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/



Regards,

Javier



Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Mittwoch, 27. Juni 2018 21:17
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: [Spacewalk-list] Adding SLE_SP3 client



Hello all,



I have a working Spacewalk server that is able to serve packages to RHEL 
clients.  I am now attempting to get some SLES clients registered with the 
server.  Following the documentation for registering clients, I pointed our 
SLE_SP3 host to the correct zypper repo at opensuse.org, but received the 
following error when attempting to install rhn-client-tools et al:



"Problem: nothing provides python-newt needed by 
python2-rhn-client-tools-2.9.1-1.1.noarch"



I have verified that the python-newt package is not installed on the host.  
However, this is due to the fact that this package is in the "SUSE Manager 
Server 3.x" repo, which requires a separate subscription apart from SLES.  It 
seems counter-intuitive to require a package that comes in the SUSE Manager 
Server repo which is SUSE's proprietary alternative to Spacewalk OSS.  I am 
hoping that I have overlooked something and there is alt

Re: [Spacewalk-list] Adding SLE_SP3 client

[William Hongach]

Hi Javier,


I am pointed to that repository as per the doc for registering SLE12_SP3 
clients found at: 
https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients


However, my SLES is on s390x architecture so zypper is looking at the noarch 
packages.  When I run "zypper install rhn-client-tools" it reports the 
following:


"Problem: nothing provides python-newt needed by 
python2-rhn-client-tools-2.8.25-3.1.noarch"


I see that python2-newt is provided for x86_64 architecture, but nothing for 
noarch packages, and I don't see it included in the source packages either so 
I'm a bit stumped.


From: spacewalk-list-boun...@redhat.com  on 
behalf of Flores, Javier (D4\INF\IT ID) 
Sent: Thursday, June 28, 2018 3:12:37 AM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Adding SLE_SP3 client


Hi



Which repository at opensuse.org are you using?



You can find all the needed packages including python2-newt in this repository:

https://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8/SLE_12_SP3/



Other versions of the spacewalk client can be found here:

https://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/



Regards,

Javier



Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Mittwoch, 27. Juni 2018 21:17
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Adding SLE_SP3 client



Hello all,



I have a working Spacewalk server that is able to serve packages to RHEL 
clients.  I am now attempting to get some SLES clients registered with the 
server.  Following the documentation for registering clients, I pointed our 
SLE_SP3 host to the correct zypper repo at opensuse.org, but received the 
following error when attempting to install rhn-client-tools et al:



“Problem: nothing provides python-newt needed by 
python2-rhn-client-tools-2.9.1-1.1.noarch”



I have verified that the python-newt package is not installed on the host.  
However, this is due to the fact that this package is in the “SUSE Manager 
Server 3.x” repo, which requires a separate subscription apart from SLES.  It 
seems counter-intuitive to require a package that comes in the SUSE Manager 
Server repo which is SUSE’s proprietary alternative to Spacewalk OSS.  I am 
hoping that I have overlooked something and there is alternative access to 
python-newt and any other additional packages (newt, libnewt, etc.) that I may 
need to get the RHN client software working in SLES.



Any insight or assistance with this would be greatly appreciated.  Thanks in 
advance.


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

[Spacewalk-list] Adding SLE_SP3 client

[William Hongach]

Hello all,

I have a working Spacewalk server that is able to serve packages to RHEL 
clients.  I am now attempting to get some SLES clients registered with the 
server.  Following the documentation for registering clients, I pointed our 
SLE_SP3 host to the correct zypper repo at opensuse.org, but received the 
following error when attempting to install rhn-client-tools et al:

"Problem: nothing provides python-newt needed by 
python2-rhn-client-tools-2.9.1-1.1.noarch"

I have verified that the python-newt package is not installed on the host.  
However, this is due to the fact that this package is in the "SUSE Manager 
Server 3.x" repo, which requires a separate subscription apart from SLES.  It 
seems counter-intuitive to require a package that comes in the SUSE Manager 
Server repo which is SUSE's proprietary alternative to Spacewalk OSS.  I am 
hoping that I have overlooked something and there is alternative access to 
python-newt and any other additional packages (newt, libnewt, etc.) that I may 
need to get the RHN client software working in SLES.

Any insight or assistance with this would be greatly appreciated.  Thanks in 
advance.

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