Remove migration orchestrations

SUSE / DeepSea

A collection of Salt files for deploying, managing and automating Ceph.

GNU General Public License v3.0

160 stars 75 forks source link

Closed swiftgist closed 4 years ago

swiftgist commented 4 years ago

The osd.redeploy function does not exist. Neither orchestration has been working for some time.

Checklist:

[ ] Added unittests and or functional tests
[ ] Adapted documentation
[ ] Referenced issues or internal bugtracker
[ ] Ran integration tests successfully (trigger with "@susebot run teuthology" in a GitHub comment; see the wiki for more information)

swiftgist commented 4 years ago

@susebot run teuthology

susebot commented 4 years ago

Commit f25c1dd5995999eddb413ef99ffcc7876fffecdc is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/358/

swiftgist commented 4 years ago

@susebot run teuthology

susebot commented 4 years ago

Commit 8e20ee41478edb1ee05338dcc41b544d1dbbf5c8 is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/359/

swiftgist commented 4 years ago

@susebot run teuthology

swiftgist commented 4 years ago

@susebot run teuthology

susebot commented 4 years ago

Commit 8e20ee41478edb1ee05338dcc41b544d1dbbf5c8 is OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/361/

smithfarm commented 4 years ago

deepsea/tier2/filestore-to-bluestore-migration uses rebuild.node and deepsea/tier2/drive-replacement uses osd.replace so I guess this is OK?

shyukri commented 4 years ago

deepsea/tier2/filestore-to-bluestore-migration uses rebuild.node and deepsea/tier2/drive-replacement uses osd.replace so I guess this is OK?

True. There is no test code calling osd.redeploy