You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Cristian Ciobanu (JIRA)" <ji...@apache.org> on 2017/10/13 13:03:00 UTC

[jira] [Created] (CLOUDSTACK-10110) router issue, firewall rules - Upgrade 4.5.2 to 4.9.3 ( VMware - LocalStorage)

Cristian Ciobanu created CLOUDSTACK-10110:
---------------------------------------------

             Summary: router issue, firewall rules - Upgrade 4.5.2 to 4.9.3 ( VMware - LocalStorage) 
                 Key: CLOUDSTACK-10110
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10110
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Install and Setup
    Affects Versions: 4.9.3.0
         Environment: ACS 4.9.3 ( VMware - LocalStorage) 
            Reporter: Cristian Ciobanu


Issue #1

 I was able to update the virtual router only after I have restarted 
 the iptables-persistend form virtual router side, not sure what is 
 wrong with this router version but I don't get the right status if I 
don't restart the iptables from virtual router, I have did multiple tests.

Workaround: 

 -  Reboot router
 -  getting this error : job-3247/job-3248, cmd: CheckSshCommand)
 (logid:6b3de9fa) Trying to connect to 149.56.xxx.xx  ( I see this error in management log )
 - restart iptables from router side
 - works

   In case I destroy/restart the router I have to repeat the same 
 thing, restart iptables...

  

Issue #2

I also tested a new deploy with a template used before on this 
 setup (4.5.2), looks like the password set for new deploy is not working...

After I continued the investigation I found that router is not 
allowing the VM to fetch the password (port 8080) 

Workaround: 

 In order to fix I have added this rule 
"-A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT"  on virtual router..

   Any idea how to fix this, permanent?  In case reinstall the router 
 for sure I will have to do this again.






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)