Project

General

Profile

Actions
Copy link

Bug #44883

closed

upgrade to octopus can complain about orchestrator_cli

Added by Sage Weil about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
34272
Crash signature (v1):
Crash signature (v2):

Description

2020-04-01T03:40:49.135 INFO:teuthology.orchestra.run.smithi197.stdout:{"checks":{"MGR_MODULE_ERROR":{"severity":"HEALTH_ERR","summary":{"message":"Module 'orchestrator_cli' has failed: Not found or unloadable"}}},"status":"HEALTH_ERR"}
2020-04-01T03:40:52.136 INFO:teuthology.orchestra.run.smithi197:> true
2020-04-01T03:40:52.142 INFO:teuthology.orchestra.run.smithi197:> sudo adjust-ulimits ceph-coverage /home/ubuntu/cephtest/archive/coverage timeout 120 ceph --cluster ceph --log-early health --format=json
2020-04-01T03:40:52.487 INFO:teuthology.orchestra.run.smithi197.stdout:

/a/sage-2020-03-31_23:26:44-rados-wip-sage3-testing-2020-03-31-1656-distro-basic-smithi/4911418

The module was renamed to 'orchestrator' in octopus. Also, it's always on. I think this only shows up if the prior release explicitly enabled it. In any case, we don't want to see this after upgrade.

Actions
Copy link
 #1

Updated by Sage Weil about 4 years ago

  • Status changed from New to Resolved
  • Pull request ID set to 34272
Actions
Copy link

Also available in: Atom PDF