Old version kubectl's rolling-update command is compatible with Kubernetes 1.4 and higher only if you specify a new replication controller name. You will need to update to kubectl 1.4 or higher to use the rolling update command against a 1.4 cluster if you want to keep the original name, or you'll have to do two rolling updates.

	VRANGEPD $14, Z23, Z27, K1, Z2                     // 62b3a54150d70e
	VRANGEPD $14, Z9, Z27, K1, Z2                      // 62d3a54150d10e
	VRANGEPD $14, (R14), Z27, K1, Z2                   // 62d3a54150160e
	VRANGEPD $14, -7(DI)(R8*8), Z27, K1, Z2            // 62b3a5415094c7f9ffffff0e
	VRANGEPD $14, Z23, Z25, K1, Z2                     // 62b3b54150d70e

* If you used the [PodDisruptionBudget](http://kubernetes.io/docs/admin/disruptions/) feature in 1.4 (i.e. created `PodDisruptionBudget` objects), then **BEFORE**  upgrading from 1.4 to 1.5, you must delete all `PodDisruptionBudget` objects (`policy/v1alpha1/PodDisruptionBudget`) that you have created. It is not possible to delete these objects after you upgrade, and their presence will prevent...

			accessKey:          credentials.AccessKey,
			secretKey:          credentials.SecretKey,
			expectedRespStatus: http.StatusPreconditionFailed,
		},
		// Test case - 14, copy metadata from newObject1 with wrong modified header format
		14: {
			bucketName:         bucketName,
			newObjectName:      "newObject1",
			copySourceHeader:   url.QueryEscape(SlashSeparator + bucketName + SlashSeparator + objectName),

          <description>
            Specifies that this profile will be activated when a matching JDK is detected.
            For example, {@code 1.4} only activates on JDKs versioned 1.4,
            while {@code !1.4} matches any JDK that is not version 1.4. Ranges are supported too:
            {@code [1.5,)} activates when the JDK is 1.5 minimum.
          </description>
        </field>
        <field>