Quote Originally Posted by rich_hanley View Post
Hi there,

I'm just learning RMT and I've got a question on how it updates information contained in the systems and hw_infos tables. I've got an RMT Server running on SLES 15 SP1 and the client I'm registering is a SLES 12 SP4 box.

I install the 12 SP4 OS and on the registration installation screen I select to register the products against my local RMT Server (FQDN: nsi-rmt.netsysint.net). But I neglected to use the "Network Connection" button to define the hostname I wanted (which was supposed to be sles12sp4-rmt.netsysint.net). So the installation completes successfully, the 12 SP4 box is registered with the RMT Server, and when I look in YaST under "Software Repositories" I see all the repos with a URL of https://nsi-rmt.netsysint.net<something>.

So everything appears fine except the host name is linux-<something>. I change the hostname to sles12sp4-rmt.netsysint.net, reboot the box, and wait about 30 minutes.

I use the
mysql -u root -p rmt
command to connect to the RMT Server's database and run
select * from systems;
What I see for a hostname is "install" not "sles12sp4-rmt.netsysint.net".

After more reboots of the SLES 12 SP4 box and more waiting, the RMT Database never reflected the change in the hostname. I finally had to use the
SUSEConnect --url https://nsi-rmt.netsysint.net/
command to re-register the SLES 12 SP4 box with the RMT Server. But when I query the hw_infos table there are two rows that have the exact same uuid; and in the systems table there is still a record for the "install" hostname along with one for the new sles12sp4-rmt registration event.

My questions are as follows:
  1. Is there some RMT client-side code that should run at boot-up to send updated information to the RMT Server? If so what is it?
  2. How often does the RMT server code update / clean-up the rmt database?
  3. And - will RMT ever delete the record information for the "install" hostname or does that have to be cleaned up manually by directly connecting to the database?

Thanks for any insight!

With SUSEConnect, you should be able to delete the data (-d) and then run a cleanup on the client with the --cleanup option, then re-register with the new hostname.