Originally reported in BZ https://bugzilla.redhat.com/show_bug.cgi?id=2061062 we developed a fix to ensure no static revision is rolled out when it could break qourum.

Since we have a dedicated test suite now for vertical scaling, developed in https://github.com/openshift/origin/pull/27444

We can add a new test to also exercise this scenario with:

• delete a node, keep its member
• ensure that api and etcd were available the whole time
• adding a new member then should work with the vertical scaling feature without impacting the availability again