mib1185 opened a new issue #5202:
URL: https://github.com/apache/cloudstack/issues/5202
<!--
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
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Server
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.15.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
As descripted in #5194, with #4040 changes were made, how the
`broadcast_uri` for private VLAN network is build.
This new approach is the more correct one, but does only apply to newly
created networks (_networks created after upgrade to 4.15_), those already
existent networks keep its old `broadcast_uri` which is not correct, since it
always contains `-i` (_ex. `pvlan://63-i123`_) and those is declared as an
isolated pvlan, even it was configured as community pvlan.
In our case - since all pvlan are of type community - we simple updated all
entries in DB with following SQL statement:
```sql
UPDATE cloud.networks
SET broadcast_uri = REPLACE(broadcast_uri, '-i', '-c')
WHERE removed is null and broadcast_uri like '%pvlan%';
```
But to be more generic, it is needed that the correct pvlan type is gathered
from infrastructure (_ex. VMware portgroup_) and corresponding DB entry is
proper updated.
##### 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 -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
--
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]
