Bug 1929258 - [DOCS] clarify daemonset rollout while migrating OpenShiftSDN to OVNKubernetes
Summary: [DOCS] clarify daemonset rollout while migrating OpenShiftSDN to OVNKubernetes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Jason Boxman
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 15:02 UTC by Bram Verschueren
Modified: 2024-06-14 00:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-07 15:47:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bram Verschueren 2021-02-16 15:02:56 UTC
Document URL: 
https://docs.openshift.com/container-platform/4.6/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.html#nw-ovn-kubernetes-migration_migrate-from-openshift-sdn

Section Number and Name: 
6. Wait until the Multus daemon set pods restart.

Describe the issue: 
The current description "Wait until the Multus daemon set pods restart." is ambiguous as a pod restart relates to a restart within its lifecycle at a certain revision (which an 'oc get pods' shows). In this case the purpose is to verify if a daemonset has been rolled out to a new revision.

Suggestions for improvement: 

"Wait until the Multus daemon set has been rolled out to a new revision."

Additional information:

Comment 2 Jason Boxman 2021-03-18 03:55:31 UTC
Hi Bram,

Thanks for reporting this. I've created a PR[0] with an update for the text.

[0] https://github.com/openshift/openshift-docs/pull/30634


Note You need to log in before you can comment on or make changes to this bug.