)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":18002,"name":"John Fulton","email":"fulton@redhat.com","username":"fultonj"},"change_message_id":"93f815e77260b8150ead676611ebcb18323e368e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3e8f8266_d95ec2d2","updated":"2024-02-01 13:41:27.000000000","message":"It looks like this checks if the ceph cluster is currently running quincy and prevents the upgrade if it is. That\u0027s not a problem.\n\nDo we need another check though which prevents them from getting to quincy? I.e. should the code which does the check, get the current version that\u0027s running (like you have now) and then check the version they will be upgrading to (from the ceph image paramter) and ensure they\u0027re going to the next version?\n\nI think we had a bug where someone did the following:\n\n1. rolling_update from 4 to 5 (good)\n2. adopt with a 6 image (bad)\n\nWhere step 2, inadvertently upgraded them though it should have just kept them at the same version. Should this have some extra tasks to try to capture that?","commit_id":"038f437109a7946a17b00f8b392a2ea373ab7a25"}]}
