Documentation survey

SUSE Manager 서버 이름 변경 문제 해결

SUSE Manager 서버의 호스트 이름을 로컬로 변경하면 SUSE Manager 설치가 제대로 작동하지 않습니다. 왜냐하면 데이터베이스에서 변경사항이 적용되지 않아 변경 사항이 클라이언트와 프록시로 전파되지 않기 때문입니다.

1. Rename Server

SUSE Manager 서버의 호스트 이름을 변경해야 하는 경우 spacewalk-hostname-rename 스크립트를 사용하여 변경할 수 있습니다. 이 스크립트는 PostgreSQL 데이터베이스의 설정 및 SUSE Manager의 내부 구조를 업데이트합니다.

1.1. Server Configuration

spacewalk-hostname-rename 스크립트는 spacewalk-utils 패키지의 일부입니다.

The only mandatory parameter for the script is the new fully qualified domain name of the SUSE Manager Server.

절차: SUSE Manager 서버 이름 변경

  1. DNS 서버에서 로컬 및 원격으로 시스템 수준에서 서버의 네트워크 설정을 변경합니다. 역방향 이름 확인을 위한 구성 설정도 제공해야 합니다. 네트워크 설정 변경은 다른 시스템의 이름을 변경할 때와 동일한 방식으로 수행됩니다.

  2. 새 네트워크 구성을 사용하고 호스트 이름이 변경되었는지 확인하려면 SUSE Manager 서버를 재부팅합니다.

  3. On the container host, from the command line, execute the following command to update the settings of the server:

    mgrctl exec -ti -- spacewalk-hostname-rename <NEW-FQDN>

    Be aware that this script refreshes the pillar data for all Salt clients: the time it takes to run depends on the number of registered clients.

In case third party SSL certificates are used on the SUSE Manager server, the server certificate and key need to be recreated with the new FQDN.

Procedure: Renaming SUSE Manager Server with third party certificates

  1. Copy the root certification authority certificate, the new server certificate and key to the SUSE Manager Server host.

  2. Copy them to a temporary folder in the container using mgrctl cp.

  3. Run spacewalk-hostname-rename with parameters to deploy the new certificate.

    mgrctl exec mkdir /tmp/ssl
mgrctl cp ca.crt server:/tmp/ssl/ca.crt
mgrctl cp srv.crt server:/tmp/ssl/srv.crt
mgrctl cp srv.key server:/tmp/ssl/srv.key
mgrctl exec -ti -- spacewalk-hostname-rename <NEW-FQDN> --ssl-ca-cert=/tmp/ssl/ca.crt --ssl-server-cert=/tmp/ssl/srv.crt and --ssl-server-key=/tmp/ssl/srv.key
mgrctl exec rm -r /tmp/ssl

1.2. Directly Managed Clients Reconfiguration

Skip this procedure if clients are managed via a SUSE Manager proxy.

With the following procedure, reconfigure directly managed clients to make them aware of the new hostname and IP address.

Procedure: Reconfiguring Directly Managed Clients

  1. On the every client, in the Salt client configuration file, specify the name of the new Salt master (SUSE Manager Server). The filename is /etc/venv-salt-minion/minion.d/susemanager.conf or, if you do not use the Salt bundle, /etc/salt-minion/minion.d/susemanager.conf:

    master: <new_hostname>

  2. On every client, restart Salt service. Either run:

    systemctl restart venv-salt-minion

    Or, if you do not use the Salt bundle, run:

    systemctl restart salt-minion

1.3. Client Connection with Applying High State

Finally, to fully propagate the hostname to the Salt client configuration, apply the high state. Applying the high state will update the hostname in the repository URLs.

2. Reconfigure Proxy

Every proxy must be reconfigured. The new server certificate and key must be copied to the proxy. For more information, see Install SUSE Manager Proxy.

If you use PXE boot through a proxy, you must check the configuration settings of the proxy. If you use PXE boot through non-containerized SUSE Manager Proxy 4.3, tftpsync needs to be reconfigured.

On the container host, execute:

mgrctl exec -ti -- configure-tftpsync.sh