Bug 1768678

Summary: [DDF] This section needs to be more specific as there are two agents that need to be removed. The ovs agent and the nic
Product: Red Hat OpenStack Reporter: Direct Docs Feedback <ddf-bot>
Component: documentationAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED EOL QA Contact: RHOS Documentation Team <rhos-docs>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: cpaquin, igallagh, lmarsh, sbauza, smooney
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-17 12:00:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1788336, 1841011, 1849166, 1946835, 2002099    
Bug Blocks:    

Description Direct Docs Feedback 2019-11-04 23:49:43 UTC 
This section needs to be more specific as there are two agents that need to be removed. The ovs agent and the nic agent.  Something like this might be better for this section and the one above. openstack compute service list --host  and openstack network agent list --host 


Reported by: rhn-gps-cpaquin

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/sect-scaling_the_overcloud#annotations:70046044-6de7-4e93-a6aa-e50931d60a95
Comment 2 Chris Paquin 2019-11-15 03:00:53 UTC 
This specific section has you remove the openvswitch-agent from the compute node when you are scaling back. 

Remove the node’s Open vSwitch agent:

(overcloud) $ openstack network agent list
(overcloud) $ openstack network agent delete [openvswitch-agent-id]


However, there is an additonal network agent (the nic-agent) that needs to be removed as well, so the documentation as it stands is not completely correct.
Comment 3 smooney 2019-11-15 11:22:48 UTC 
That is only true if you deploy the sriov nic agent by default it is not deployed.
that said i do think this could be enhanced with a note as this step would not be required at all
if this was ovn and as you pointed out you would have to addtionally need to remove the sriov nic agent if you deployed
with sriov so i think this can be enhanced with a note to that effect and perhaps cross like to the docs
we have for the different network backends.
Comment 4 Sylvain Bauza 2019-11-15 15:16:09 UTC 
SME: Sean Mooney