Bug 1776850
| Summary: | Ansible Networking – no VLANs are set on switch, in case when Trunk network is used to create BM Guest | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Arkady Shtempler <ashtempl> |
| Component: | python-networking-ansible | Assignee: | Dan Radez <dradez> |
| Status: | CLOSED DUPLICATE | QA Contact: | Arkady Shtempler <ashtempl> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 13.0 (Queens) | CC: | jlibosva, michapma |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-26 14:18:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 1774941 *** |
### Prerequisites ### QE setup is up and running with OSP13 (Puddle with Trunk support) ### Scenario ### Try to create BM guest using Trunk network as follow: openstack port create --network tenant-net trunk-parent-port -> Save the ID for {trunk-parent-port id} openstack port create --network tenant-net2 trunk-notparent-port openstack network trunk create --parent-port trunk-parent-port trunk openstack network trunk list (Make sure that "trunk" network is in) and save its ID openstack network trunk show "ID_Of_Trunk_Network" --> get Seg_ID openstack network trunk set --subport port=trunk-notparent-port,segmentation-type=vlan,segmentation-id="Seg_ID" trunk openstack server create --flavor baremetal --image overcloud-full --key default --port {trunk-parent-port id} BM_Guest_1 ### Expected Result ### 1) BM guest is UP and running 2) Switch ports is set to TRUNK + relevant VLANs are set as expected ### Actual Result ### 1) No VLANs and TRUNK are set for physical port on Switches 2) ERRORs in logs 3) In spite of the fact that “Ansible Networking” feuture has failed to configure physical port on Switch, BM guest state is in ACTIVE and not ERROR as it would be expected in such cases. ### Errors in Logs ### ------------------------------ LogPath:/var/log/containers/ IsTracebackBlock:False BlockTuple:(27050, 27050) UniqueCounter:10 BlockLinesSize:1 networking_ansible.ml2.mech_ ------------------------------ LogPath:/var/log/containers/ IsTracebackBlock:True BlockTuple:(27070, 27078) UniqueCounter:10 BlockLinesSize:8 neutron.plugins.ml2.managers [req-cf9ea21b-9e30-471b-93a2- neutron.plugins.ml2.managers Traceback (most recent call last): neutron.plugins.ml2.managers File "/usr/lib/python2.7/site- neutron.plugins.ml2.managers driver.obj.bind_port(context) neutron.plugins.ml2.managers File "/usr/lib/python2.7/site- neutron.plugins.ml2.managers raise ml2_exc.MechanismDriverError( neutron.plugins.ml2.managers MechanismDriverError neutron.plugins.ml2.managers