Skip to content

Release 0.6.0
Compare
Choose a tag to compare
@emanoelxavier emanoelxavier released this 23 May 17:54
· 11 commits to 0.6 since this release
v0.6.0
91e5eb9

Known Issues

Issue:
Job Graph is not displayed well if special characters - “{“ and “}” are used in the Manager Connector Name

Work around:
Do not use the special characters “{“ and “}” in the Manager Connector Name

Issue:
Deleting and Creating a Deployment Spec (DS) using Distributed Appliance (DA) with a Cirros image, may create 2 images.

Environment: Newton Openstack

Work around:
Delete the DA and then re-create the DA and DS.
Add the image properties on the new image for accessing Console of Cirros.
openstack image set --property hw_vif_model=virtio --property hw_disk_bus=ide (image-name or id)

Issue:
Creating a Deployment Specification (DS) with the same name, after a delete, fails if flavor, image, or Openstack Security Group with the same DS instance name already exists

Environment: Newton Openstack

Work around:
Delete the Image, Openstack Security Group (SG) and flavor from Newton Openstack. Then you will be able to create the new DS
OR
Delete the Distributed applicance (DA) and re-create the DA. Deleting the DA deletes the image, Openstack SG, and the flavor. Now creating the DS will succeed.

Issue:
Nuage: Creating a Security Group (SG) with no (Virtual Machines) VMs as SG members throws an error - 'A domain was not found for tenant and Security Group'. The empty Security Group cannot be deleted.

Work around:
Force Delete the Security Group. Create another SG with at least one VM as a Security Group Member.

Issue:
Nuage: Deleting a binded Security Group (SG) throws an error 'NoSuchElementException'

Work around:
Force delete the binded SG and clean up the objects (Un-assign and Delete corresponding Policy Groups) on Nuage GUI also

Issue:
Currently we are not identifying the best Distributed Appliance Instance (DAI) to be removed, (i.e.: defective one or least loaded) when the Deployment Specification (DS) count is reduced.

Detailed explanation:
Create a DS with Deployment Count 2 - If you don't have enough resources in your Openstack environment and in case that the result will have one working appliance and one not working appliance (cause the vm instance cannot start)
In such a case adjusting the Deployment Count to 1 - not guaranteed that the non working appliance will be deleted. Hence in some cases the working appliance will be deleted and the non working appliance will stay.

Work around:
Delete the DS and create a new DS with Deployment Count 1

Issue:
ISM - status is always displayed as INSTALL_WAIT on the Plugins page.
Note - No functionality impacted by this failure.

Issue:
Security Group (SG) Bind - SG (VM) Sync not working appropriately (passes when it should have failed) after deleting Inspection interface from the router on Openstack

Work around:
Unbind the SG, Bind again. Now the Job will FAIL as expected

Issue:
Security Group (SG) Bind - SG Sync for 'Network' not working appropriately (passes when it should have failed) after deleting Inspection interface from the router on Openstack

Work around:
Unbind the SG, Bind again. Now the Job will FAIL as expected

Issue:
The 'status' field on 'Appliance Instance Status' page is not visible completely and needs to be scrolled to see the whole wording - The security manager for this appliance instance does not provide appliance status.

Issue:
For ISM Distributed Appliance Instance (DAI), Discovered and Inspection Ready fields blank out periodically. Reappear on refresh after clicking on 'Appliance Instances' and disappear again after sometime

Work around:
Click on Appliance Instance Status button, where it will have values N/A or hard-coded values ‘true’ for Discovered and Inspection Ready fields. Then refresh the DAI page. The correct values will appear now.
NOTE – No functionality impacted

Issue:
Appliance Instance Status not populated with accurate values for certain fields like - Manager IP, DPA PID, DPA Info. Some fields are blank whereas others display ‘null’.
Note – No functionality impacted.

Issue:
OSC Plugins page does not automatically refresh when a plugin is added or deleted.
Note – No functionality impacted

Work around:
Refresh the web page of OSC plugins - and you will be able to see the current plugins.

Issue:
Centos OSC may display inaccurate vmware version with CLI command - show vmware.
Note – No functionality impacted

Issue:
Traffic Policy Mappings display N/A for Failure Policy instead of FAIL_CLOSE.
Note - No functionality impacted

Issue:
No Security Group (SG) Sync Job triggered with network port delete

Issue:
May get IllegalArgumentException when creating a Deployment Spec (DS) on Nuage Environment

Issue:
When creating a Virtualization Connector with a duplicate name, different (inconsistent) error messages are received in API-doc and automation.
Note - No functionality impacted

Issue:
After upload plugins, UI does not do screen refresh to see the result.
Work around:
Manually do a refresh from the browser F5.

Issue:
Adding MC (Manager Connector) with wrong Ip or wrong user name/password throws an inaporopriate error: no route to the host.

Expected Result:
A warning should be displayed suggesting possible reasons for failure, providing an option if the user wants to continue.

Work around:
Make sure values for ip, username and password are accurate.

Issue:
User can install Manager plugins from SDN plugin pane, and it shows up in Manager plugins State: INSTALL_WAIT.

Work around:
Make sure upload SDN plugins in SDN Plugins pane and upload Manager plugins in Manager Plugins pane.

Issue:
Uploading an invalid plugin (e.g. a missing properties plugin) did not display an appropriate error message.

Work around:
Do not upload an invalid plugin file.

Assets 2
Loading