During the upgrade to SUSE Enterprise Storage 5 salt stage 3 returns an error for time_server

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

Environment

SUSE Enterprise Storage 3
SUSE Enterprise Storage 4
SUSE Enterprise Storage 5

Situation

When running stage 3 of the upgrade procedure as described in the online documentation with step 10. e. the following error is returned:

:~ # salt-run state.orch ceph.stage.3
firewall                 : disabled
apparmor                 : disabled
fsid                     : valid
public_network           : valid
cluster_network          : valid
cluster_interface        : valid
monitors                 : valid
mgrs                     : valid
storage                  : valid
ganesha                  : valid
master_role              : valid
fqdn                     : valid
time_server              : ['master-node01.lab.domain 1xx.1xx.1xx.50 no UCST response after 1 seconds']
[ERROR   ] No highstate or sls specified, no execution made
master-node01.lab.domain_master:
----------
          ID: validate failed
    Function: salt.state
        Name: just.exit
      Result: False
     Comment: No highstate or sls specified, no execution made
     Started: 12:07:51.486263
    Duration: 0.736 ms
     Changes:  

Summary for master-node01.lab.domain_master
------------
Succeeded: 0
Failed:    1
------------
Total states run:     1
Total run time:   0.736 ms

Resolution

Update the DeepSea configuration with the proper time server being used in the environment then re-run stage 3.

See the Additional Information section for details.

Cause

By default DeepSea will use the server specified with the master-role for the time server.

Additional Information

To modify the time server take the following steps:

1. Edit the file "/srv/pillar/ceph/stack/ceph/cluster.yml" and add the following line:

time_server: server_name.domain

Replace "server_name.domain" with the proper time server to be used in the environment.

2. Update the pillar data with the new information with:

:~ # salt '*' saltutil.pillar_refresh

3. Verify the pillar was updated correctly, the adjusted time server should be listed:

:~ # salt '*' pillar.items
...
    time_server:
        server_name.domain
...



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:7022272
  • Creation Date: 03-Nov-2017
  • Modified Date:03-Mar-2020
    • SUSE Enterprise Storage

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

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

Join Our Community

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.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

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

Go to Customer Center