From a23b3ae5b1ca64c1420323bec97863d5afbd1e91 Mon Sep 17 00:00:00 2001 From: Javeria Khan Date: Tue, 10 May 2016 12:50:55 -0700 Subject: [PATCH] Adding some expected failures - fuel createmirror - adding/removing controllers Change-Id: I9fc0c14de63bc30b47b07790b1bf06e347257ed5 Signed-off-by: Javeria Khan --- doc/plugin_guide/source/troubleshooting.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/plugin_guide/source/troubleshooting.rst b/doc/plugin_guide/source/troubleshooting.rst index 43a8551..038f629 100644 --- a/doc/plugin_guide/source/troubleshooting.rst +++ b/doc/plugin_guide/source/troubleshooting.rst @@ -19,6 +19,11 @@ Troubleshooting service plumgrid status service plumgrid start +#. After removing or adding a Controller node, the following steps must be performed on the active Controllers to avoid re-deployment failures: + :: + + pip uninstall pbr + rmmod iovisor Expected Failures ----------------- @@ -26,3 +31,5 @@ Expected Failures #. Some health checks are expected to fail due to the default networks and routers created during the deployment being deleted, after PLUMgrid plugin is installed. These are created before PLUMgrid is enabled as the network backend, hence the PLUMgrid ONS platform has no knowledge of these previously created routers/networks and they are therefore removed. #. *Check pacemaker status* will also fail on OVS checks, as OVS is not used in a PLUMgrid based environment. + +#. Using *fuel createmirror* is not supported since the PLUMgrid plugin requires a specific version of certain packages on trusty that are not hosted by the partial mirror created by this tool. Furthermore, for an enviroment with the PLUMgrid plugin enabled, it will fail to set repositories as defaults for new environments; however it will update the current ones in the Fuel UI Settings --> Repositories to the local links.