Browse Source

Adding some expected failures

 - fuel createmirror
 - adding/removing controllers

Change-Id: I9fc0c14de63bc30b47b07790b1bf06e347257ed5
Signed-off-by: Javeria Khan <javeriak@plumgrid.com>
Javeria Khan 2 years ago
parent
commit
a23b3ae5b1
1 changed files with 7 additions and 0 deletions
  1. 7
    0
      doc/plugin_guide/source/troubleshooting.rst

+ 7
- 0
doc/plugin_guide/source/troubleshooting.rst View File

@@ -19,6 +19,11 @@ Troubleshooting
19 19
       service plumgrid status
20 20
       service plumgrid start
21 21
 
22
+#. After removing or adding a Controller node, the following steps must be performed on the active Controllers to avoid re-deployment failures:
23
+  ::
24
+
25
+      pip uninstall pbr
26
+      rmmod iovisor
22 27
 
23 28
 Expected Failures
24 29
 -----------------
@@ -26,3 +31,5 @@ Expected Failures
26 31
 #. 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.
27 32
 
28 33
 #. *Check pacemaker status* will also fail on OVS checks, as OVS is not used in a PLUMgrid based environment.
34
+
35
+#. 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.

Loading…
Cancel
Save