SUSE Support

Here When You Need Us

During the migration to SES 7 the salt adopt state does not containerize any daemons

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

Environment

SUSE Enterprise Storage 6
SUSE Enterprise Storage 7
SUSE Enterprise Storage 7.1

Situation

Following the SES 7 Online documentation to upgrade a SES 6 cluster, after step 2. when "zypper migration" was run on the first MON node and the node rebooted, executing the adopt salt state as per step 3. completes without any errors, however no containers are started / listed when running "podman ps".

When running the command "cephadm ls" on the relevant node, it fails as follows:
 
# /usr/sbin/cephadm ls
Traceback (most recent call last):
  File "/usr/sbin/cephadm", line 6251, in <module>
    r = args.func()
  File "/usr/sbin/cephadm", line 3838, in command_ls
    legacy_dir=args.legacy_dir)
  File "/usr/sbin/cephadm", line 3865, in list_daemons
    legacy_dir=legacy_dir)
  File "/usr/sbin/cephadm", line 1772, in get_legacy_daemon_fsid
    fsid = get_legacy_config_fsid(cluster, legacy_dir=legacy_dir)
  File "/usr/sbin/cephadm", line 1750, in get_legacy_config_fsid
    config = read_config(config_file)
  File "/usr/sbin/cephadm", line 1208, in read_config
    cp.read_file(s_io)
  File "/usr/lib64/python3.6/configparser.py", line 718, in read_file
    self._read(f, source)
  File "/usr/lib64/python3.6/configparser.py", line 1066, in _read
    lineno)
configparser.DuplicateSectionError: While reading from '<???>' [line 14]: section 'global' already exists

Resolution

Remove any duplicate sections from the "/etc/ceph/ceph.conf" file then run the adopt state again. The above example indicates that at least for the [global] section in the file there are multiple entries.

Cause

Duplicate / multiple section entries in the "/etc/ceph/ceph.conf" file.

Additional Information

Since at this stage the cluster is in a partly migrated state, do not use DeepSea but rather manually update the "/etc/ceph/ceph.conf" file and copy it to the cluster node(s).

Disclaimer

This Support Knowledgebase provides a valuable tool for 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.

  • Document ID:000020637
  • Creation Date: 13-Jul-2022
  • Modified Date:13-Jul-2022
    • SUSE Enterprise Storage

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.