search

openshift / openshift-docs

OpenShift 3 and 4 product and community documentation
https://docs.openshift.com
Apache License 2.0
764 stars 1.76k forks source link

OCP 4.9 Release Notes Tracker #33497

Closed jeana-redhat closed 3 years ago

jeana-redhat commented 3 years ago

Please leave comments here for anything that should be highlighted in the 4.9 release notes. If possible, provide a link to the Jira or BZ related to your item. Thank you!

Update 21 September

A note about known issues All Bugzilla items that need to be documented as known issues in the release notes should have Doc Type = Known Issue and the Doc Text field populated accordingly. Before adding a known issue to this tracker:

  1. Ensure the Doc Type and Doc Text fields are filled in correctly.
  2. See if your issue shows up in the query we will use to populate the release notes.
  3. If the fields are set correctly, and the issue is not in the query, add it here.

Resources

Key to reactions

:eyes: ACK :+1: Done :-1: Not going in 4.9 rel notes

lbarbeevargas commented 3 years ago

The Metering Operator was deprecated in 4.6. If it is still scheduled to be removed in 4.9:

OSDOCS-2249 tracks this release note.

damemi commented 3 years ago

Descheduler Operator v1beta1 API has been removed for v1 https://github.com/openshift/cluster-kube-descheduler-operator/pull/199

dulek commented 3 years ago

OpenShift on OpenStack: In order to support LoadBalancer Services using OpenStack Octavia with OVN provider, the security group rules allowing NodePort traffic to master and worker nodes are now changed to open 0.0.0.0/0 and not just the cluster CIDR. This is because OVN loadbalancers are preserving the original source IP of the traffic, so for LoadBalancer services it can be anything. This wasn't required to support Amphora Octavia provider as Amphora loadbalancers change source IP to the IP of the LB itself which is guaranteed to be in the cluster CIDR.

Maybe a more detailed explanation: https://github.com/openshift/installer/pull/5052#issue-681980588

mandre commented 3 years ago

OpenShift on OpenStack: The openstack cloud provider LoadBalancer configuration now defaults to 'use-octavia=True', unless deploying with Kuryr, in which case 'use-octavia' is set to false.

Context: https://github.com/openshift/installer/pull/5047/

bgilbert commented 3 years ago

Nodes installed with coreos-installer previously retained the installation Ignition config in /boot/ignition/config.ign. Starting with the OpenShift 4.9 install image, that file is removed when the node is provisioned. This change currently does not affect clusters that were originally installed on previous OpenShift versions, and are thus using an older bootimage.

mikemckiernan commented 3 years ago

MetalLB and the MetalLB Operator for a platform-native load balancer implementation on bare metal: https://github.com/openshift/openshift-docs/pull/35705

SNiemann15 commented 3 years ago

PR for IBM Z and IBM Power Systems input https://github.com/openshift/openshift-docs/pull/35828

tmalove commented 3 years ago

PR to support etcd to the list of control plane components. https://github.com/openshift/openshift-docs/pull/35923

bparees commented 3 years ago

we need loud and clear discussion of all the k8s beta apis that are being removed in this release. Just putting them in the table probably isn't even enough (but i don't see them listed as removed in the current tables, either)

cc @mfojtik @deads2k @sttts

bparees commented 3 years ago

We are also going to require explicit manual admin acks regarding the removed apis before a 4.8 cluster can be upgraded to 4.9, so that should be called out as well.

@wallylewis you're driving the product docs on that, maybe you can help with the wording here as well.

jeana-redhat commented 3 years ago

@bparees thanks - that's super critical content. Just to clarify, are you referring to the table in the draft Rel Notes I just sent out, or to the one linked above? Not everything has gotten into the draft Rel Notes version of the table yet, but we will be working from the Google Sheet as a source for updates, so getting it correct in there would be a great (and hopefully easy) first step :slightly_smiling_face:

damemi commented 3 years ago

Descheduler Operator: Users should update to the latest 4.8 operator before updating to the 4.9 operator to ensure proper conversion of existing Descheduler CRDs (https://github.com/openshift/cluster-kube-descheduler-operator/pull/215)

bparees commented 3 years ago

@bparees thanks - that's super critical content. Just to clarify, are you referring to the table in the draft Rel Notes I just sent out, or to the one linked above?

I was looking at https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html

which has, for example, CRDs:

image

so at a minimum that 4.9 column will need to say "removed", but again i think we need more explicit wording than just hoping someone sees it in the table.

tmalove commented 3 years ago

Support the automatic rotation of etcd certificates. https://issues.redhat.com/browse/OSDOCS-2348

jeana-redhat commented 3 years ago

@bparees ok, I think we are on the same page here. Typically, we also include some content below the table about things that have changed, so that would be a normal part of the Rel Notes process. We will definitely want to make sure that this is super obvious to folks.

romfreiman commented 3 years ago

@jeana-redhat we should add documentation about Single Node Openshift

jiajliu commented 3 years ago

About the upgrade to v4.9, afaik we have several new updates here. we need announce them in the release note for users.

  1. we provide a new way performing a canary rollout update , related prs are https://github.com/openshift/openshift-docs/pull/35420, https://github.com/openshift/openshift-docs/pull/34445

  2. About the v4.8 to v4.9 upgrade, we have added several gate/check to block the upgrade. One is about https://bugzilla.redhat.com/show_bug.cgi?id=1978376, which admin need ack the admin-gates to unblock the upgrade. Another is about the etcdbackup is needed to be done before upgrading to v4.9, more info refers to https://issues.redhat.com/browse/OTA-464.

cc @jianlinliu @shellyyang1989 if any missing part to be added for v4.9 release notes.

xiaojiey commented 3 years ago

About the Rhel8 scaleup for GCP platform, there is a known issue that when fips mode enabled, scaleup Rhel8 will fail due to fail to install packages from the default RHUI. Seen from https://bugzilla.redhat.com/show_bug.cgi?id=1997516. cc: @gpei @pdhamdhe

xiaojiey commented 3 years ago

About the Rhel8 scaleup for GCP platform, there is a known issue that when fips mode enabled, scaleup Rhel8 will fail due to fail to install packages from the default RHUI. Seen from https://bugzilla.redhat.com/show_bug.cgi?id=1997516. cc: @gpei @pdhamdhe

Create a tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=2001464 for OCP to track the status.

lihongan commented 3 years ago

Routing new features/enhancements are missing, below should be covered in release notes:

cc @quarterpin

jianlinliu commented 3 years ago 
2. About the v4.8 to v4.9 upgrade, we have added several `gate/check` to block the upgrade. One is about https://bugzilla.redhat.com/show_bug.cgi?id=1978376, which admin need ack the admin-gates to unblock the upgrade.

Thanks for @jiajliu raising this. Some more info about the user acknowledge before v4.8 to v4.9 upgrade, it is being tracking in https://bugzilla.redhat.com/show_bug.cgi?id=1999092, which need to be merged in some 4.8.z version, once it is merged, 4.8.z to 4.9 upgrade will be blocked until user manually acknowledge it. Maybe we need to mention that in 4.9 release note somewhere though the 4.8.z bug is not merged yet.

simonpasquier commented 3 years ago

Monitoring:

adambkaplan commented 3 years ago

Builds:

gpei commented 3 years ago

Installer:

jeana-redhat commented 3 years ago

Adding from @cuppett via email: Look into linking to CRI-O 1.22 release notes

dulek commented 3 years ago

We need this note from 4.8 added to 4.9 as well:

An Open Virtual Network (OVN) bug causes persistent connectivity issues with Octavia load balancers. When Octavia load balancers are created, OVN might not plug them into some Neutron subnets. These load balancers might be unreachable for some of the Neutron subnets. This problem affects Neutron subnets, which are created for each OpenShift namespace, at random when Kuryr is configured. As a result, when this problem occurs the load balancer that implements OpenShift Service objects will be unreachable from OpenShift namespaces affected by the issue. Because of this bug, OpenShift Container Platform 4.9 deployments that use Kuryr SDN are not recommended on Red Hat OpenStack Platform (RHOSP) 16.1 with OVN and OVN Octavia configured until the bug is fixed. (BZ#1937392)

Please note that OSP 16.1.7 should be free of the bug and is planned to be released on 2021-10-13. I guess it's worth mentioning that.

dulek commented 3 years ago

Installations on OpenStack with Kuryr will not work if configured with proxy when proxy is required to access OpenStack APIs. This is tracked in BZ 1985486.

kmccarron-rh commented 3 years ago

The Special Resource Operator (SRO) is added per https://issues.redhat.com/browse/OSDOCS-2396 as a technology preview. RN PR: https://github.com/openshift/openshift-docs/pull/36465 Also, Driver Toolkit, that was added to the 4.8 RN post GA, is added to the TP table in 4.9.

yingwang-0320 commented 3 years ago

About creating SR-IOV network node policy, there is a known issue that when users add/delete sriovnetworknodepolicy CR before waiting for all the syncStatus of sriovnetworknodestate CRs turning to 'Succeeded', the sriov network config daemon pod will cordon the node and mark it unschedulable forever.

Workaround: Before adding/deleting one sriovnetworknodepolicy CR, make sure all the syncStatus of sriovnetworknodestate CRs is in 'Succeeded' state.

More detailed info can be found in https://bugzilla.redhat.com/show_bug.cgi?id=2002508

dulek commented 3 years ago

Known issue: Due to a race condition OpenStack cloud provider may not start properly, which may manifest as LoadBalancer Services never getting EXTERNAL-IP set (and Octavia LB created). This can be worked around by restarting kube-controller-manager pods using the procedure described in the BZ 2004542.

jinyunma commented 3 years ago

Starting from ocp4.9, vsphere old version (< 6.3 U2) and virtual hardware version 13 will be deprecated, related doc PR: https://github.com/openshift/openshift-docs/pull/35530. It's better to highlight this in release note. cc: @gnufied @duanwei33 if you have more comments.

jeana-redhat commented 3 years ago

https://issues.redhat.com/browse/OSDOCS-1896 Include a Grafana deprecation notice in release notes and Monitoring documentation @simonpasquier do you know if this item is still relevant/correct? You can respond on the Jira item, I know conversation in the replies to this tracker item can be tedious :)

Update: Not in 4.9

jeana-redhat commented 3 years ago

@romfreiman Re: SNO, sounds like the Telco writing team is planning to add the release note for this, so I am marking it as done from our side.

Thanks @stevsmit & @sjstout for tracking this one down :slightly_smiling_face:

nekop commented 3 years ago

Automatic RHEL Entitlement Management for Builds, 4.9 Tech Preview missing?

siamaksade commented 3 years ago

RHDEVDOCS-3000 Volume support in BuildConfigs is missing

sosiouxme commented 3 years ago

ART-3107 (not a public JIRA) As of 4.9, OLM operators that ship as part of OCP (I hope docs has a good term for these) will go in a stable channel in addition to 4.9, and stable will be the default for this and future releases. Admins are encouraged to prefer this channel so that they will not need to change channels with future upgrades. @adellape

side note: the only channel name mentioned in https://docs.openshift.com/container-platform/4.8/operators/admin/olm-adding-operators-to-cluster.html is stable so I can't see how any docs need changing outside release notes.

jeana-redhat commented 3 years ago

Known issue https://bugzilla.redhat.com/show_bug.cgi?id=1996916 Cc: @kmccarron-rh

rolfedh commented 3 years ago

RHDEVDOCS-3000 Volume support in BuildConfigs is missing @siamaksade WIP: https://github.com/openshift/openshift-docs/pull/37160/

rolfedh commented 3 years ago

Builds:

@adambkaplan WIP: https://github.com/openshift/openshift-docs/pull/37160/files

bburt-rh commented 3 years ago

Monitoring:

Known issue: https://bugzilla.redhat.com/show_bug.cgi?id=2007677#c0

Draft content: Because certain high cardinality monitoring metrics were inadvertently dropped (BZ#207667), the following container performance input and output metrics are not available in this release:

pod qos System

No workaround exists for this issue. To track these metrics for production workloads, do not upgrade to the initial 4.9 release.

adambkaplan commented 3 years ago

Automatic RHEL Entitlement Management for Builds, 4.9 Tech Preview missing?

So the Insights operator will now add the RHEL entitlement to the cluster. However full, seamless support for builds won't be tech preview until 4.10

kmccarron-rh commented 3 years ago

Known issue https://bugzilla.redhat.com/show_bug.cgi?id=1996916 Cc: @kmccarron-rh

This one has been sent for review: https://github.com/openshift/openshift-docs/pull/37263

yunjiang29 commented 3 years ago

@jeana-redhat known issue for installer, should be added in release note: Bug 1997059 - Failed to create cluster in AWS us-east-1 region due to a local zone is used

cc @staebler @codyhoag

jianzhangbjz commented 3 years ago
  1. OLM fails to update the operator immediately when switching the operator channels. Workaround: recreate the corresponding CatalogSource pod. Details: https://bugzilla.redhat.com/show_bug.cgi?id=2002276
  2. opm render doesn't create the olm.bundle.object automatically, this will lead to no packagemanifest display on console or backend. The user has to add it manually for now. Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2003894#c1 Story: https://issues.redhat.com/browse/OLM-2331 PR: https://github.com/operator-framework/operator-registry/pull/807
  3. opm render fails to extract the images defined in the deployment to the relatedImages field, details: https://bugzilla.redhat.com/show_bug.cgi?id=2000379

cc: @kevinrizza

jinyunma commented 3 years ago

Known issue when enabling Tang disk encryption on upi-on-vsphere cluster, need to highlight in release notes. Bug 1975701 - [vsphere][upi] Network is changed to dhcp configuration after second reboot when Tang disk encryption is enabled

Since there is workaround in the bug, it's better to add this workaround in doc Encrypting and mirroring disks during installation

cc @dustymabe if any more comments about this.

zhaozhanqi commented 3 years ago

For users if enabling Tang disk encryption on upi-on-vsphere and OVN kubernetes plugin with version 4.8.z want to upgrade 4.9. there is a known bug as below. Not user if there is user is using this kind of profile until now, I think we need to highlight this issue in case since it will cause worker become not ready when upgrading. Bug 2006756 - Nodes go to NotReady when a both Tang and OVN enabled vSphere cluster is being upgraded to 4.9 from 4.8.12

cc @jcaamano @anuragthehatter

xingxingxia commented 3 years ago

1991448 for epic AUTH-13 may be needed to be documented under "Known issues" section of the release notes. CC @yaoli-redhat , @adambkaplan @alicerum , @s-urbaniak @slaskawi

yunjiang29 commented 3 years ago

@jeana-redhat another known issue for AWS ap-northeast-3 region should be added in release note, please refer to @staebler 's comment , thanks

Bug 1996544 - AWS region ap-northeast-3 is missing in installer prompt

cc @codyhoag

yapei commented 3 years ago

https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html#ocp-4-9-assessing-node-logs-from-the-node-details-page

Node Details page is different from Node Logs page, Node Logs page is where user can view node logs, see attachment

Screen Shot 2021-10-11 at 1 37 01 PM
kasturinarra commented 3 years ago

@jeana-redhat add GA in 4.9 column for oc CLI-Plugins ? Similar as what we have done for 4.8 ? Thanks !! CC @zhouying7780

[1] https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.html#ocp-4-8-technology-preview