[
https://issues.apache.org/jira/browse/CLOUDSTACK-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247872#comment-15247872
]
ASF GitHub Bot commented on CLOUDSTACK-9268:
--------------------------------------------
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1394#issuecomment-211958527
@koushik-das oh, i understand your question better now. i would like to do
it on every commit. It makes the commit history clearer and it mitigates
conflict issues. when we ask people to rebase their PR we know for sure they
are getting everything that is committed. i would like for us to forward merge
every time we do a commit to previous branches.
In this case I will do the forward merge because I have other commits I
will merge today and if the forward merge is done right after the commit it
makes it easier to verify the forward merge was done when scanning the commit
history.
> Display VM in Load balancing rule in UI
> ---------------------------------------
>
> Key: CLOUDSTACK-9268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9268
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Nitin Kumar Maharana
>
> Steps of Reproducing:
> ==================
> 1:Create VMs
> 2:Make LoadBalancing rule in GUI
> Name:WWW
> PrivatePort:80
> PublicPort:80
> Add VMs:some VMs
> The VMs which has been already assigned is still being listed when you add
> the VM to an existing rule.
> In addition to this, when we remove a VM, and again try to add for that
> rule,it will not list that VM in the list.
> The issue doesn’t occur if you go back to the network tab and view the
> loadbalance rules again.
> A page refresh is solving the issue, but need to resolve this issue without a
> refresh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
