Bug 1768678 - [DDF] This section needs to be more specific as there are two agents that need to be removed. The ovs agent and the nic
Summary: [DDF] This section needs to be more specific as there are two agents that nee...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1788336 1841011 1849166 1946835 2002099
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-04 23:49 UTC by Direct Docs Feedback
Modified: 2022-07-28 18:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-17 12:00:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-1886 0 None None None 2021-12-17 12:09:15 UTC

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


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