7023370: spacewalk-schema-upgrade fails with “[susemanager-schema-3.1.19] Was not able to find upgrade path in directory [/etc/sysconfig/rhn/schema-upgrade]”.

This document (7023370) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3.1

SUSE Manager 3.2

Situation

While upgrading spacewalk’s schema from version 3.1.19 to version 3.2 from SUSE Manager 3.1 to 3.2 the following error occurs :
# spacewalk-schema-upgrade
Schema upgrade: [susemanager-schema-3.1.19-2.30.1] -> [susemanager-schema-3.2.12-3.3.1] Searching for upgrade path to: [susemanager-schema-3.2.12-3.3.1] Searching for upgrade path to: [susemanager-schema-3.2.12] Searching for start path: [susemanager-schema-3.1.19-2.30.1]
Searching for start path: [susemanager-schema-3.1.19] Was not able to find upgrade path in directory [/etc/sysconfig/rhn/schema-upgrade].

Resolution

Workaround is to create the missing folder:
# mkdir /etc/sysconfig/rhn/schema-upgrade/susemanager-schema-3.1.19-to-susemanager-schema-3.2.0

This issue is fixed in an upcoming maintenance update (eta : end of the September 2018).

Cause

The following rpm :
susemanager-schema-3.1.19-to-susemanager-schema-3.2.0
has a missing folder in it’s path :
/etc/sysconfig/rhn/schema-upgrade/

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7023121: SUSE Manager database schema fails with ERROR: syntax error at or near “on”

This document (7023121) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3

SUSE Manager 3.1

SUSE Manager 3.2

Situation

After upgrade from SUSE Manager 3.0* to 3.1 or 3.2 the database spacewalk schema upgrade fails:
/var/log/spacewalk/schema-upgrade/schema-from-<date-time>-to-susemanager-schema-<version>.log

psql:<stdin>:46: ERROR: syntax error at or near "on"

LINE 27: on conflict do nothing;

Another indicator is following log message in /var/log/boot:


Apr 11 10:55:26 xxdevmon postgresql-init[1701]: Your database files were created by PostgreSQL version 9.4.

Apr 11 10:55:26 xxdevmon postgresql-init[1701]: Using the executables in /usr/lib/postgresql94/bin.

Resolution

PostgreSQL database needs to be upgraded as outlined within the release notes:

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

Related:

7013242: How to unregister SUSE Manager Client

Traditional client

NOTE: This process is only for SUSE Manager clients, do not run it on the SUSE Manager itself.

First, please stop osad client on the system:

SLES 11:
rcosad stop

SLES12:

systemctl stop osad

In order to unregister a SUSE Manager client, several rpms must be removed. Try the following method first:

zypper rm -u spacewalksd spacewalk-check zypp-plugin-spacewalk spacewalk-client-tools osad

This will show the following:

Refreshing service ‘spacewalk’.

Loading repository data…

Reading installed packages…

Resolving package dependencies…

The following packages are going to be REMOVED:

spacewalk-check spacewalk-client-setup spacewalksd zypp-plugin-python zypp-plugin-spacewalk osad

5 packages to remove.

After the operation, 301.0 KiB will be freed.

Continue? [y/n/?] (y):

The above 5 rpm packages are client specific, and should be removed.

If this fails, please remove them manually. Do not use the following “rpm -e” commands unless the “zypper rm” command above failed.

rpm -e spacewalk-client-setup

rpm -e spacewalksd

rpm -e spacewalk-check

rpm -e zypp-plugin-spacewalk

rpm -e zypp-plugin-python

rpm -e osad

After this is complete, remove /etc/sysconfig/rhn/systemid.

That file only exists on a client machine and is used to register itself with SUSE Manager.

When this is done, refresh the repositories on the server (zypper ref -s), and then list them out (zypper lr) and make sure everything looks good.

If any repositories pointing to spacewalk still exist, remove them using the following:

zypper repos -d

zypper removerepo <ID of the repo in the output from previous command>

Salt client
Stop salt minion:
on SLES 12 stop the salt minion service using:

systemctl stop salt-minion

and on SLES 11 based systems

rcsalt-minion stop

Remove repositories and configs:
rm /etc/zypp/repos.d/susemanager:channels.repo

rm -r /etc/salt/
Delete the client RPMs of salt (as the channel data was removed before, rpm -e needs to be used here):

rpm -e salt salt-minion

Now the system can be removed from the inventory using the webUI, or from command line using spacecmd:

spacecmd system_delete FQDN

salt-key -d FQDN

Related:

7023121: SUSE Manager database schema upgrade fails after upgrade from 3.0 to 3.1*

This document (7023121) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3

SUSE Manager 3.1

Situation

After upgrade from SUSE Manager 3.0* to 3.1 or 3.2 the database spacewalk schema upgrade fails:
/var/log/spacewalk/schema-upgrade/schema-from-<date-time>-to-susemanager-schema-<version>.log

psql:<stdin>:46: ERROR: syntax error at or near "on"

LINE 27: on conflict do nothing;

Another indicator is following log message in /var/log/boot.log:
Apr 11 10:55:26 xxdevmon postgresql-init[1701]: Your database files were created by PostgreSQL version 9.4.

Apr 11 10:55:26 xxdevmon postgresql-init[1701]: Using the executables in /usr/lib/postgresql94/bin.

Resolution

PostgreSQL database needs to be upgraded as outlined within the release notes:

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022656: zypper se -s shows installed packages as (System Packages)

This document (7022656) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3.1

Situation

When searching for packages using zypper se -s <packagename>, the package is listed first as (System Packages) and second with the repository name:

sles12sp3:~ # zypper se -s mcelog

[…]

Loading repository data…

Reading installed packages…

S | Name | Type | Version | Arch | Repository

–+——–+———+———–+——–+—————————

i | mcelog | package | 1.48-1.13 | x86_64 | (System Packages)

v | mcelog | package | 1.48-1.13 | x86_64 | SLES12-SP3-Pool for x86_64

In addition, when running “zypper dup” the command lists a bunch of packages to be reinstalled despite the fact they are at the latest level.

This could possibly lead to a broken system.

Resolution

Fixed as of spacewalk-backend >= 2.7.73.12-2.16.2.

https://download.suse.com/Download?buildid=giNV9QlhhSE~

– Use GTM for rpm build_time (bsc#1078056)

Cause

Different package timestamps in the database and repository metadata.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022894: SUSE Manager Proxy system ID does not match a Spacewalk Proxy Server

Complete error message from /var/log/apache2/error_log:

Thu Apr 26 12:48:33.171992 2018] [wsgi:error] [pid 11788] SUSE Manager 11788 2018/04/26 12:48:33 +02:00: (‘<Fault -1002: \’\\nError Message:\\n Spacewalk Proxy service not enabled for server profile: “sumaproxy.domain.lan”\\nError Class Code: 1002\\nError Class Info: \\n SUSE Manager Proxy system ID does not match a Spacewalk Proxy Server\\n in the database.\\nExplanation: \\n An error has occurred while processing your request. If this problem\\n persists please enter a bug report at scc.suse.com.\\n If you choose to submit the bug report, please be sure to include\\n details of what you were trying to do when this error occurred and\\n details on how to reproduce this problem.\\n\’>’,)

[Thu Apr 26 12:48:33.173176 2018] [wsgi:error] [pid 11788] Exception reported from sumaproxy

[Thu Apr 26 12:48:33.173192 2018] [wsgi:error] [pid 11788] Time: Thu Apr 26 12:48:33 2018

[Thu Apr 26 12:48:33.173201 2018] [wsgi:error] [pid 11788] Exception type <class ‘xmlrpclib.Fault’>

[Thu Apr 26 12:48:33.173208 2018] [wsgi:error] [pid 11788] Exception while handling function ProxyAuth.login (Fault) – SUSE Manager Proxy not able to log in.

[Thu Apr 26 12:48:33.173216 2018] [wsgi:error] [pid 11788]

[Thu Apr 26 12:48:33.173223 2018] [wsgi:error] [pid 11788] Exception Handler Information

[Thu Apr 26 12:48:33.173231 2018] [wsgi:error] [pid 11788] Traceback (most recent call last):

[Thu Apr 26 12:48:33.173238 2018] [wsgi:error] [pid 11788] File “/usr/share/rhn/proxy/rhnProxyAuth.py”, line 249, in login

[Thu Apr 26 12:48:33.173245 2018] [wsgi:error] [pid 11788] token = server.proxy.login(self.__systemid)

[Thu Apr 26 12:48:33.173253 2018] [wsgi:error] [pid 11788] File “/usr/lib/python2.7/site-packages/rhn/rpclib.py”, line 662, in __call__

[Thu Apr 26 12:48:33.173260 2018] [wsgi:error] [pid 11788] return self._send(self._name, args)

[Thu Apr 26 12:48:33.173268 2018] [wsgi:error] [pid 11788] File “/usr/lib/python2.7/site-packages/rhn/rpclib.py”, line 394, in _request

[Thu Apr 26 12:48:33.173275 2018] [wsgi:error] [pid 11788] self._handler, request, verbose=self._verbose)

[Thu Apr 26 12:48:33.173283 2018] [wsgi:error] [pid 11788] File “/usr/lib/python2.7/site-packages/rhn/transports.py”, line 194, in request

[Thu Apr 26 12:48:33.173290 2018] [wsgi:error] [pid 11788] return self._process_response(fd, connection)

[Thu Apr 26 12:48:33.173297 2018] [wsgi:error] [pid 11788] File “/usr/lib/python2.7/site-packages/rhn/transports.py”, line 222, in _process_response

[Thu Apr 26 12:48:33.173312 2018] [wsgi:error] [pid 11788] return self.parse_response(fd)

[Thu Apr 26 12:48:33.173320 2018] [wsgi:error] [pid 11788] File “/usr/lib/python2.7/site-packages/rhn/transports.py”, line 246, in parse_response

[Thu Apr 26 12:48:33.173327 2018] [wsgi:error] [pid 11788] return u.close()

[Thu Apr 26 12:48:33.173335 2018] [wsgi:error] [pid 11788] File “/usr/lib64/python2.7/xmlrpclib.py”, line 800, in close

[Thu Apr 26 12:48:33.173342 2018] [wsgi:error] [pid 11788] raise Fault(**self._stack[0])

[Thu Apr 26 12:48:33.173350 2018] [wsgi:error] [pid 11788] Fault: <Fault -1002: ‘\nError Message:\n

Related:

7022839: spacewalk-schema-upgrade fails with “relation “suseimageinfopackage” does not exist”

This document (7022839) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3.1

Situation

When applying latest schema upgrades to the SUSE Manager database, the process fails with messages similar to:

[…]

Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20180410-174141-to-susemanager-schema-3.0.25.log].

(1/7) apply upgrade [susemanager-schema-3.0.22-to-susemanager-schema-3.0.23/001-may_take_long-fix-rhn_pe_v_r_e_uq.sql.postgresql]

Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/schema-from-20180410-174141-to-susemanager-schema-3.0.25.log].

While looking at /var/log/spacewalk/schema-upgrade/schema-from-20180410-174141-to-susemanager-schema-3.0.25.log the following error is found:

[…]

DROP INDEX

DROP INDEX

CREATE FUNCTION

DROP TRIGGER

psql:<stdin>:88: ERROR: relation “suseimageinfopackage” does not exist

LINE 1: update suseImageInfoPackage set evr_id = original.id where e…

^

QUERY: update suseImageInfoPackage set evr_id = original.id where evr_id = duplicate.id

CONTEXT: PL/pgSQL function fix_rhn_pe_v_r_e_uq() line 70 at SQL statement

Resolution

When experiencing this issue, please contact SUSE Technical Services for a Program Temporary Fix (PTF).

Cause

A problem in the schema update trying to update a table that does no longer exist.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7012610: SUSE Manager Master TID.

This document (7012610) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3

SUSE Manager 2.1

SUSE Manager 1.7

SUSE Manager 1.2

Situation

This is a collection of available TIDs and documentation about SUSE Manager known issues and its usage.

Resolution

On-line documentation

https://www.suse.com/documentation/suse_manager/

Technical Information Documents


TID 7021393 – Creating Child Channel for Red Hat Base Media in SUSE Manager 3.1

TID 7018748 – Command “zypper ref” returns an HTTP 400 error in SUSE Manager 3.0 client

TID 7019020 – SUSE Manager schema-upgrade to susemanager-schema-3.0.19-21.2 fails after maintenance update

TID 7018625 – /var/log/cobbler/tasks occupies high amount of disk space

TID 7018395 – SUSE Manager 2.1 mgr-sync refresh returns a 500 Internal Server Error

TID 7018123 – Steps to Create a Salt SUSE Manager Client

TID 7018018 – Bootstrap fails with ImportError: cannot import name idn_pune_to_unicode

TID 7017994 – Attempt to bootstrap a client to a SUSE Manager 3 Server returns “Internal Server Error”

TID 7017746 – smdba space-overview reporting >100% Use

TID 7017577 – Steps to Create a SUSE Manager Client

TID 7017307 – SUSE Manager client bootstrap fails with checksum error for python-six package

TID 7017278 – Autoinstallation of a SLES/SLED 12 SP1 fails in SUSE Manager with “unknown module cobbler” error

TID 7017147 – zypper commands return “SSL certificate problem: unable to get local issuer certificate” on a SLES 12 SUSE Manager Client

TID 7016303 – Registering a SLES 10 SP2 server with SUSE Manager

TID 7016161 – SUMA 2.1 Migration to SCC Can Result in Duplicate Product_ids

TID 7016022 – Migrating a SUSE Manager 2.1 Server with an oracle db to SCC results in an unhandled internal exception: null error

TID 7015878 – jabberd initialization fails with “db: couldn’t open environment: Resource temporarily unavailable”

TID 7015781 – SUSE Manager Postgresql DB backup produces an increasing number of backup files

TID 7015751 – spacewalk-schema-upgrade fails during migration from SUSE Manager 1.7 to 2.1

TID 7015465 – Unexpected Error occurs when clicking on the SUSE Products tab in the SUSE Manager webUI

TID 7015464 – API calls fail to execute after online update to spacecmd-2.1.25.3-0.7.6

TID 7015427 – Service osa-dispatcher fails to load when starting SUSE Manager in a restored environment

TID 7015415 – Wagon upgrade: “This system is managed by SUSE Manager. YaST wagon module cannot migrate systems managed by SUSE Manager

TID 7015412 – rhnpush stops with Packahe Upload Failed error code 55

TID 7015362 – SUMA imported channel (inter-server sync) cannot be used for SP-Migration

TID 7015286 – logfile rhn_web_api.log not rotated

TID 7015067 – How to sync SUSE Manager via SMT

TID 7015050 – SUSE Manager 1.7 disk space requirements

TID 7015063 – mgr-ssh-push-init fails with generic connection error if remote ssh host key has changed

TID 7015059 – SUSE MANAGER mgr-ncc-sync fails with “Couldnt resolve proxy ‘http'”

TID 7015040 – SUSE manager system overview shows different naming schemes for hostnames

TID 7014990 – configure-proxy.sh fails on SUSE Manager Proxy with NPBootstrap error

TID 7014956 – Bootstrapping full virtualized client prints libvirt: XML-RPC error

TID 7014931 – mgr-ncc-sync -l returns empty data

TID 7014921 – Error when performing a “spacewalk-service status” or “rcjabberd status”

TID 7014814 – Necessary changes in SUSE Manager to point to a different external Oracle database

TID 7014570 – Unable to run Service Pack Migration for SLED 11 SP2 with cloned channels

TID 7014341 – SUSE Manager clients have seen slowness during patching

TID 7014178 – SUSE Manager system entitlements not matching Novell Customer Center subscriptions

TID 7014066 – SSH pub key of nocpulse not available in SUSE Manager WebUI

TID 7014059 – SUSE Manager channel sync problems

TID 7014024 – SUSE Manager webinterface shows internal server error after applying online updates

TID 7014012 – osad unable to connect to jabber servers

TID 7004532 – Scheduling Service Pack migration on SUSE manager fails with internal server error

TID 7011819 – Client fails to register with SUSE Manager

TID 7013366 – How to clean up an accidental bootstrap run on SUSE Manager

TID 7013242 – How to unregister SUSE Manager Client

TID 7013245 – mgr-ncc-sync hangs on command line or fails to sync channels in SSH Push enabled environments

TID 7012889 – Unable to remove System Profiles via GUI or Command Line

TID 7012639 – spacewalk-clone-by-date quits with AttributeError: DepSolver instance has no attribute ‘_override_sigchecks’

TID 7012650 – spacewalk-clone-by-date quits with AttributeError: ‘NoneType’ object has no attribute ‘date’

TID 7012623 – JAVA core dumps occupy disk space in /usr/sbin

TID 7012621 – mgr-register-bunch single run fails with scheduling service appears down

TID 7012610 – SUSE Manager Master TID

TID 7012605 – Activation Key Config Auto-Deploy fails during bootstrap

TID 7012598 – Taskomatic reports out of JAVA heap space

TID 7012597 – ssh push to client fails with query did not return a unique result

TID 7012512 – SUSE Manager taskomatic reports “ORA-00979: not a GROUP_BY expression”

TID 7012490 – New product channels not available in SUSE Manager

TID 7012485 – SUSE Manager UI display Internal Server Error

TID 7012366 – SUSE Manager client fails to complete scheduled package installation

TID 7012170 – A registered client system disappeared from SUSE Manager

TID 7011819 – Client fails to register with SUSE Manager

TID 7011749 – Install update package in a custom repo using a Manager/Proxy setup

TID 7011670 – How to assign Long Term Service Pack repositories to installed systems

TID 7011633 – SUSE Manager 1.7 client shows “Service network is missed in runlevel 4 to use service rhnsd” when insserv command is run

TID 7010991 – 504 Gateway timeout when executing smt-ncc-sync

TID 7010797 – How to upgrade SUSE Manager 1.2 to version 1.7

TID 7010526 – Synchronization with spacewalk-repo-sync works, but not with mgr-ncc-sync

TID 7010351 – Leap second issues – June 30, 2012

TID 7005356 – SUSE Manager client registration of a SLES10SP4 fails with Internal Server Error

TID 701920 – SUSE Manager schema-upgrade to susemanager-schema-3.0.19-21.2 fails after maintenance update

Wiki related resources

A wiki with configuration examples is available at https://wiki.novell.com/index.php/SUSE_Manager.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022435: Task stuck in SUMA webUI – Task Engine Status.

This document (7022435) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3

Situation

In SUMA webUI, “Admin – Task Engine Status – Runtime Status” running tasks are still observed, although in the taskomatic logs, it is clear that the job has actually already finished.

Example:
INFO | jvm 1 | 2017/11/30 05:44:00 | 2017-11-30 05:44:00,143 [DefaultQuartzScheduler_Worker-1] INFO com.redhat.rhn.taskomatic.task.ChannelRepodata – In the queue: 1
INFO | jvm 1 | 2017/11/30 05:44:00 | 2017-11-30 05:44:00,162 [Thread-15686] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter – File Modified Date:2017-11-28 05:46:36 CET
INFO | jvm 1 | 2017/11/30 05:44:00 | 2017-11-30 05:44:00,162 [Thread-15686] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter – Channel Modified Date:2017-11-30 05:43:43 CET
INFO | jvm 1 | 2017/11/30 05:44:00 | 2017-11-30 05:44:00,190 [Thread-15686] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter – Generating new repository metadata for channel ‘sles11-sp4-updates-x86_64′(sha1) 2953 packages, 637 errata
INFO | jvm 1 | 2017/11/30 05:44:05 | 2017-11-30 05:44:05,809 [Thread-15678] INFO com.redhat.rhn.taskomatic.task.RepoSyncTask – 05:43:53 ======================================
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:43:53 | Channel: sle11-sdk-sp4-pool-x86_64
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:43:53 ======================================
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:43:53 Sync of channel started.
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:43:57 Repo URL: https://updates.suse.com/repo/$RCE/SLE11-SDK-SP4-Pool/sle-11-x86_64/?gGVRvB0TGIi90EruqJIS-SgUkyJc58JLsoI1WmvTVXNNNDKjy1g2HumK5ntSNzcOePLGuSk9kEXRfWo5TEylglQPDCpC_aVv3PPKcg4btjfOcX97lvPEqEKljPz1QOppxiT9mXygiRrT
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:43:57 Packages in repo: 2752
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:44:05 No new packages to sync.
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:44:05 Repo https://updates.suse.com/repo/$RCE/SLE11-SDK-SP4-Pool/sle-11-x86_64/?gGVRvB0TGIi90EruqJIS-SgUkyJc58JLsoI1WmvTVXNNNDKjy1g2HumK5ntSNzcOePLGuSk9kEXRfWo5TEylglQPDCpC_aVv3PPKcg4btjfOcX97lvPEqEKljPz1QOppxiT9mXygiRrT has 0 patches.
INFO | jvm 1 | 2017/11/30 05:44:05 | 05:44:05 Sync completed.

Resolution

To resolve this properly, the following must be fixed directly in SQL (only restarting spacewalk is not sufficient !).

Example :

spacewalk-service stop

spacewalk-sql – <<<“UPDATE rhnTaskoRun SET status = ‘FINISHED’, end_time = now() WHERE status = ‘RUNNING’ OR end_time IS NULL;”

spacewalk-service start

Cause

Tasks that were already finished were incorrectly identified as still running.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022173: OSAD clients not taking actions immediately after a migration or upgrade in SUSE Manager

In the SUSE Manager Server, the jabberd DB should be recreated:

# spacewalk-service stop

# rm -Rf /var/lib/jabberd/db/*

# spacewalk-service start

The same applies for the proxies:

# spacewalk-proxy stop

# rm -Rf /var/lib/jabberd/db/*

# spacewalk-proxy start

In the clients, the osad-auth.conf file should be deleted:

# rcosad stop

# rm -f /etc/sysconfig/rhn/osad-auth.conf

# rcosad start

Obviously this step can be automated through SUSE Manager, specially in the case of having several clients. The task will be eventually run after a maximum of 4 hours. It can also be forced by running the following in the client:

# rhn_check

However, this requires logging into every client.

Related: