[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328840#comment-16328840
 ] 

Kris Sterckx commented on CLOUDSTACK-9749:
------------------------------------------

I am not clear on what the Apache Jira policy is about "resolved" state. Isn't 
confusing that a ticket is set to Resolved but the fix is not yet merged in ?
It might be just me who is confused.  [~bhaisaab] can you clarify the policy 
about Resolved state in Jira ?

> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9749
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>            Reporter: Raf Smeets
>            Assignee: Frank Maximus
>            Priority: Critical
>             Fix For: 4.10.0.0
>
>         Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to