Remove assertAcked() from updateMinMasterNodes() (#113807)

When we're removing nodes there's a possibility for the cluster state
update to succeed but acking to fail (e.g. if it was waiting for an ack
from a removed node). Really there's no need to check for the acking of
the update here, we're in Zen2-land already.

Author: DaveCTurner

test/framework/src/main/java/org/elasticsearch/test/InternalTestCluster.java

@@ -166,7 +166,6 @@
 import static org.elasticsearch.test.NodeRoles.nonDataNode;
 import static org.elasticsearch.test.NodeRoles.onlyRole;
 import static org.elasticsearch.test.NodeRoles.removeRoles;
-import static org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertAcked;
 import static org.hamcrest.Matchers.equalTo;
 import static org.hamcrest.Matchers.greaterThan;
 import static org.hamcrest.Matchers.greaterThanOrEqualTo;
@@ -2415,12 +2414,11 @@ private void updateMinMasterNodes(int eligibleMasterNodeCount) {
             // there should be at least one master to update
             logger.debug("updating min_master_nodes to [{}]", minMasterNodes);
             try {
-                assertAcked(
-                    client().admin()
-                        .cluster()
-                        .prepareUpdateSettings()
-                        .setTransientSettings(Settings.builder().put(DISCOVERY_ZEN_MINIMUM_MASTER_NODES_SETTING.getKey(), minMasterNodes))
-                );
+                client().admin()
+                    .cluster()
+                    .prepareUpdateSettings()
+                    .setTransientSettings(Settings.builder().put(DISCOVERY_ZEN_MINIMUM_MASTER_NODES_SETTING.getKey(), minMasterNodes))
+                    .get(TimeValue.timeValueSeconds(30));
             } catch (Exception e) {
                 throw new ElasticsearchException(
                     "failed to update minimum master node to [{}] (current masters [{}])",