[enterprise-3.11] 3.11.82 release notes and latest-tags

install/disconnected_install.adoc

@@ -3,9 +3,9 @@
 {product-author}
 {product-version}
 :major-tag: v3.11
-:latest-tag: v3.11.69
-:latest-int-tag: v3.11.69
-:latest-registry-console-tag: v3.11.69
+:latest-tag: v3.11.82
+:latest-int-tag: v3.11.82
+:latest-registry-console-tag: v3.11.82
 :data-uri:
 :icons:
 :experimental:

install_config/aggregate_logging.adoc

@@ -3,10 +3,10 @@
 {product-author}
 {product-version}
 ifdef::openshift-enterprise[]
-:latest-tag: v3.11.69
+:latest-tag: v3.11.82
 endif::[]
 ifdef::openshift-origin[]
-:latest-tag: v3.11.69
+:latest-tag: v3.11.82
 endif::[]
 :data-uri:
 :icons:

release_notes/ocp_3_11_release_notes.adoc

@@ -2084,3 +2084,83 @@ openshift_openstack_load_balancer_floating_ip: false
 To upgrade an existing {product-title} 3.10 or 3.11 cluster to this latest
 release, see xref:../upgrading/index.adoc#install-config-upgrading-index[Upgrade
 methods and strategies] for instructions.
+
+[[ocp-3-11-82]]
+=== RHBA-2019:0326 - {product-title} 3.11.82 Bug Fix Update
+
+Issued: 2019-02-20
+
+{product-title} release 3.11.82 is now available. The list of packages and
+bug fixes included in the update are documented in the
+link:https://access.redhat.com/errata/RHBA-2019:0326[RHBA-2019:0326] advisory.
+The container images included in the update are provided by the
+link:https://access.redhat.com/errata/RHBA-2019:0327[RHBA-2019:0327] advisory.
+
+Space precluded documenting all of the bug fixes and enhancements for this
+release in the advisory. See the following sections for notes on upgrading and
+details on the bug fixes and enhancements included in this release.
+
+[[ocp-3-11-82-bug-fixes]]
+==== Bug Fixes
+
+* All Docker related packages are not removed during the uninstall process.Docker is not re-installed properly during installation, causing Docker CLI tasks to fail. With this bug fix, all related Docker packages to uninstall are now added. Re-installation succeeds after running the uninstall playbook.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1635254[*BZ#1635254*])
+
+* Polling of quotas resulted in undesirable toast notifications. Now, quota polling errors are suppressed and users no longer see these notifications.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1651090[*BZ#1651090*])
+
+* Previously, running the install playbook multiple times with no changes to the cluster console configuration could cause the cluster console login to stop working. The underlying problem has been fixed, and now running the playbook more than once will correctly roll out a new console deployment. This problem can be worked around without the installer fix by manually deleting the console pods using the command:
++
+----
+$ oc delete --all pods -n openshift-console
+----
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1651632[*BZ#1651632*])
+
+* Certain certificate expiry check playbooks did not call properly initialization functions resulting in an error. Those playbooks have been updated to avoid this problem.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1655183[*BZ#1655183*])
+
+* The OpenShift SDN/OVS DaemonSets were upgraded during control plane
+upgrades with an `updateStrategy` of `RollingUpdate`, an upgrade of the
+pods in the entire cluster was performed. This caused unexpected network
+and application outages on nodes. This bug changed the `updateStrategy` for
+SDN/OVS pods to `OnDelete` in the template, affecting only new
+installations. Control plane upgrade tasks were added to modify SDN/OVS
+daemonsets to use `OnDelete` `updateStrategy`. Node upgrade tasks were
+added to delete all SDN/OVS pods while nodes are drained. Network outages
+for nodes should only occur during the node upgrade when nodes are drained.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1657019[*BZ#1657019*])
+
+* Previously, the 3.11 admin console did not correctly display whether a storage class was the default storage class, as it was checking an out-of-date annotation value. The admin console has been updated to use the `storageclass.kubernetes.io/is-default-class=true` annotation, and service classes are now properly marked as default when that value is set.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1659976[*BZ#1659976*])
+
+* A changed introduced in Kubernetes 1.11 affected nodes with many IP addresses in `vSphere` deployments. Under vSphere, a node hosting several `Egress IPs` or `Router HA` addresses would sporadically lose IP addresses and start using one of the other ones, causing networking problems. Now, if a `node IP` is specified in the node configuration, it will be used correctly, regardless of how many other IP addresses are assigned to the node.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1666820[*BZ#1666820*])
+
+* A type error in the OpenStack code prevented installation on OpenShift nodes without floating IP addresses. This error has been corrected, and installation proceeds as expected.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1667270[*BZ#1667270*])
+
+* Certain certificate expiry check playbooks did not call initialization functions properly, resulting in an error. Those playbooks have been updated to avoid this issue.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1667618[*BZ#1667618*])
+
+* The cluster role `system:image-pruner` was required for all DELETE
+requests to the registry. As a result, the regular client could not cancel
+its uploads, and the `S3 multipart` uploads were accumulating. Now, the
+cluster role `system:image-pruner` will accept DELETE requests for uploads
+from clients who are allowed to write into them.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1668412[*BZ#1668412*])
+
+* If the specified router certificate, key, or CA did not end with a new line character, the router deployment would fail. A new line is now appended to each of the input files ensuring this problem doesn't occur.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1668970[*BZ#1668970*])
+
+* The `volume-config.yaml was not copied to `/etc/origin/node`. As a result, volume quotas were not observed, so local storage size was not limited. Now, the `volume-config.yaml` is copied to `/etc/origin/node`. Volume quotas are observed and local storage size is limited by setting `openshift_node_local_quota_per_fsgroup` in the inventory.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1669555[*BZ#1669555*])
+
+*  `oc` image mirror failed with error `tag: unexpected end of JSON input` when attempting to mirror images from Red Hat registry. This was a result of commits from a dependency were dropped from the product build. The commits have been re-introduced, and the command can now parse the output successfully, as well as mirror from the Red Hat registry.
+(link:https://bugzilla.redhat.com/show_bug.cgi?id=1670551[*BZ#1670551*])
+
+[[ocp-3-11-82-upgrading]]
+==== Upgrading
+
+To upgrade an existing {product-title} 3.10 or 3.11 cluster to this latest
+release, see xref:../upgrading/index.adoc#install-config-upgrading-index[Upgrade
+methods and strategies] for instructions.

upgrading/automated_upgrades.adoc

@@ -2,9 +2,9 @@
 = Performing automated in-place cluster upgrades
 {product-author}
 {product-version}
-:latest-tag: v3.11.69
+:latest-tag: v3.11.82
 :latest-short-tag: v3.11
-:latest-int-tag: v3.11.69
+:latest-int-tag: v3.11.82
 ifdef::openshift-enterprise[]
 :pb-prefix: /usr/share/ansible/openshift-ansible/
 endif::[]