rajujith opened a new issue, #7816:
URL: https://github.com/apache/cloudstack/issues/7816
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
KVM
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
ACS 4.18 , KVM : Ubuntu 22.04, Rocky 8.
Storage traffic configured in the zone with VLAN subnet.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
KVM : Ubuntu 22.04, Rocky 8.
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When SSVM is created in the zone with storage traffic configured and has a
subnet with VLAN the VLAN bridge is not provisioned by cloudstack on the KVM
instead it attaches the `vnet` to the parent bridge instead of creating a VLAN
bridge.
Another issue is that the UI won't show the VLAN ID although it is in the
DB, these could be caused by the same issue?
I could notice that the SSVM start answer has the following information on
the storage NIC:
`
"broadcastType":"Storage","type":"Storage","broadcastUri":"storage://150"`
This should be ideal when compared to public NIC:
`"broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://51"`
The table also has stored the VLAN id differently:
```
select * from dc_storage_network_ip_range;
+----+--------------------------------------+---------------+----------------+---------------+------+---------------+----------------+--------+------------+
| id | uuid | start_ip | end_ip
| gateway | vlan | netmask | data_center_id | pod_id | network_id |
+----+--------------------------------------+---------------+----------------+---------------+------+---------------+----------------+--------+------------+
| 3 | 596ef473-0224-4df2-a630-5c4840213b6b | 192.168.150.2 | 192.168.150.10
| 192.168.150.1 | 150 | 255.255.255.0 | 1 | 1 | 203 |
+----+--------------------------------------+---------------+----------------+---------------+------+---------------+----------------+--------+------------+
```
In the `vlan` table it is of format `vlan://51`. I tried changing the
datatype of column` vlan` in table `dc_storage_network_ip_range` to
VARCHAR(255) but it breaks.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Create a zone with storage traffic configured.
2. Enable the zone to deploy SSVM
3. verify whether SSVM's storage vNIC/vnet is attached to a VLAN-tagged
bridge ( bridge with VLAN interface under it).
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
CloudStack should create a VLAN interface and associate it with a bridge in
KVM when SSVM is deployed in a zone with a storage subnet with VLAN.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
CloudStack is not creating a VLAN interface and associates it with a bridge
in KVM when SSVM is deployed in a zone with a storage subnet with VLAN.
~~~
```
brctl show
bridge name bridge id STP enabled interfaces
brbond1-51 8000.2e79bdd10f08 no bond1.51
vnet30
cloud0 8000.b220e3da90a2 no vnet28
cloudbr0 8000.a2a6f0d66f61 yes bond0
vnet29
cloudbr1 8000.02206b3129f6 yes bond1
vnet31
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
