[sle-beta] UUDI not tested - Wrong Hostname updated --cleanup

Joerg.Reisenweber at btc-it-services.com Joerg.Reisenweber at btc-it-services.com
Fri Apr 6 09:35:30 MDT 2018

Thank you, Vincent! This sounds promising and might come in handy a few times. We will definitely give it a try.

Have a great weekend

Von: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] Im Auftrag von Vincent Moutoussamy
Gesendet: Freitag, 6. April 2018 17:22
An: Waite, Dick (External) <dick.waite at softwareag.com>; SUSE SLE Beta <sle-beta at lists.suse.com>
Betreff: Re: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup


By the way, I recently discovered the tool “clone-master-clean-up”:

# zypper info clone-master-clean-up
Loading repository data...
Reading installed packages...

Information for package clone-master-clean-up:
Repository     : SLE-Module-Server-Applications15-Pool
Name           : clone-master-clean-up
Version        : 1.2-2.6
Arch           : noarch
Vendor         : SUSE LLC <https://www.suse.com/<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.suse.com%2F&data=02%7C01%7Cjoerg.reisenweber%40btc-it-services.com%7Cd05e734ebe864676ebc308d59bd230fe%7Cc064efb078954eebb406a40bc377bc7d%7C0%7C0%7C636586249439292690&sdata=65yOnGynT7CaEdcTTJb6FU9GNH42aUDjzNhcdCk9y2E%3D&reserved=0>>
Support Level  : Level 3
Installed Size : 12.4 KiB
Installed      : No
Status         : not installed
Source package : clone-master-clean-up-1.2-2.6.src
Summary        : Clean up a system for cloning preparation
Description    :
    Clean up a system for cloning preparation by cleaning up usage history and log files, etc.

And you can also find a bit of documentation at:

Please give this tool a try,

Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

On 13 Mar 2018, at 07:28, Thorsten Kukuk <kukuk at suse.de<mailto:kukuk at suse.de>> wrote:

On Tue, Mar 13, Waite, Dick (External) wrote:

Last word and then I shut up...

You can not update / write to a database / registry without any check that the caller is entitled to update / write that field. Even a Hostname check would be better that nothing. The  --cleanup option will be forgotten at some time by someone and then that lowly clone is going to update the SCC of a valuable Mother or maybe even a queen.

Again: the hostname is completly useless for this case in most environments.
Else: all other data used for registration got cloned by you and
is identical on both machines. So any check we can do would tell
us: this is the same machine as registered against SCC.

If you clone a machine, you have to remove all host specific data.
And this is not only the SCC registration stuff, this are also
machine-id, dbus ID, ssh host key, maschine specific certificates, ...
If you don't do that, bad thinks can happen, not only with registration.


Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
sle-beta mailing list
sle-beta at lists.suse.com<mailto:sle-beta at lists.suse.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180406/5c10f930/attachment.htm>

More information about the sle-beta mailing list