[jira] [Commented] (CLOUDSTACK-9154) rVPC doesn't recover from cleaning up of network garbage collector

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9154:


Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1259#issuecomment-166401238
  
Hey @wilderrodrigues that's awesome! Would you mind pointing this PR to the 
4.7 branch? I created it today and it finally got mirrored :-)


> rVPC doesn't recover from cleaning up of network garbage collector
> --
>
> Key: CLOUDSTACK-9154
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9154
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.6.0, 4.7.0, 4.6.1, 4.6.2
> Environment: ACS 4.7
>Reporter: Remi Bergsma
>Assignee: Wilder Rodrigues
> Fix For: 4.7.1
>
>
> - deploy a rVPC
> - deploy VM in it
> - make port forwarding (2nd ip, firewall and such)
> - confirm it works
> - stop the vm
> - after some time the network garbage collector will come and tear down the 
> network since there are no more VMs
> - keepalived will enter FAULT state because of missing eth2 nic (which was 
> first network tier)
> - all is left is ethic (link local) and lo0
> - then start the vm again
> - the nics get plugged again and keepalived will decide on a new master
> - the nics are screwed up after this:
> ```
> root@r-1021-VM:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:02:92 brd ff:ff:ff:ff:ff:ff
> inet 169.254.2.146/16 brd 169.254.255.255 scope global eth0
> 5: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:18:34:00:05 brd ff:ff:ff:ff:ff:ff
> inet x.y.238.24/24 brd x.y.238.255 scope global eth1
> inet 10.0.0.51/24 brd 10.0.0.255 scope global eth1
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth1
> 6: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:d5:4e:00:00:1d brd ff:ff:ff:ff:ff:ff
> inet x.y.238.25/24 brd x.y.238.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global eth2
> root@r-1021-VM:~#
> ```
> Public and tier ip addresses are mixed up.
> /etc/cloudstack/ips.json has the wrong info:
> ```
> { 
>   
>  [44/959]
> "eth0": [
> {
> "add": true,
> "broadcast": "169.254.255.255",
> "cidr": "169.254.2.146/16",
> "device": "eth0",
> "gateway": "None",
> "netmask": "255.255.0.0",
> "network": "169.254.0.0/16",
> "nic_dev_id": "0",
> "nw_type": "control",
> "one_to_one_nat": false,
> "public_ip": "169.254.2.146",
> "size": "16",
> "source_nat": false
> }
> ],
> "eth1": [
> {
> "add": true,
> "broadcast": "x.y.238.255",
> "cidr": "x.y.238.24/24",
> "device": "eth1",
> "first_i_p": true,
> "gateway": "x.y.238.1",
> "netmask": "255.255.255.0",
> "network": "x.y.238.0/24",
> "new_nic": false,
> "nic_dev_id": 1,
> "nw_type": "public",
> "one_to_one_nat": false,
> "public_ip": "x.y.238.24",
> "size": "24",
> "source_nat": true,
> "vif_mac_address": "06:fc:da:00:00:1c"
> },
> {
> "add": true,
> "broadcast": "10.0.0.255",
> "cidr": "10.0.0.51/24",
> "device": "eth1",
> "gateway": "10.0.0.1",
> "netmask": "255.255.255.0",
> "network": "10.0.0.0/24",
> "nic_dev_id": "1",
> "nw_type": "guest",
> "one_to_one_nat": false,
> "public_ip": "10.0.0.51",
> "size": "24",
> "source_nat": false
> }
> ],
> "eth2": [
> {
> "add": false,
> "broadcast": "10.0.0.255",
> "cidr": "10.0.0.173/24",
> "device": "eth2",
> "gateway": "10.0.0.1",
> "netmask": "255.255.255.0",
> "network": "10.0.0.0/24",
>

[jira] [Commented] (CLOUDSTACK-9154) rVPC doesn't recover from cleaning up of network garbage collector

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9154:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1259#issuecomment-166383593
  
Hi @remibergsma @miguelaferreira @DaanHoogland @borisroman 

False alarm! After the crash, when I rebooted my Test Environment the 
virbr0.50 was not configured. That's why all the SSH tests are failing.

I ran the following:

```
ifup virbr0.50
iptables -t nat -I POSTROUTING -s 192.168.23.0/24 ! -d 192.168.23.0/24 -j 
MASQUERADE
iptables -A INPUT -s 192.168.22.1/32 -p tcp -m state --state NEW -m 
multiport --dports 111,892,2049,32803 -j REJECT --reject-with 
icmp-port-unreachable
```

And everything seems to be fine:

```
9: virbr0.50@virbr0:  mtu 1500 qdisc 
noqueue state UP 
link/ether 52:54:00:c3:7b:a9 brd ff:ff:ff:ff:ff:ff
inet 192.168.23.1/24 brd 192.168.23.255 scope global virbr0.50
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec3:7ba9/64 scope link 
   valid_lft forever preferred_lft forever
```

```
sbpltk1zffh04:sbp_dev wrodrigues$ ssh root@192.168.23.10
The authenticity of host '192.168.23.10 (192.168.23.10)' can't be 
established.
RSA key fingerprint is 28:fa:ea:f7:27:26:36:27:b0:04:bc:80:0b:ca:6e:c0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.23.10' (RSA) to the list of known hosts.
root@192.168.23.10's password: 
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
13 packets transmitted, 0 packets received, 100% packet loss
# 
```


> rVPC doesn't recover from cleaning up of network garbage collector
> --
>
> Key: CLOUDSTACK-9154
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9154
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.6.0, 4.7.0, 4.6.1, 4.6.2
> Environment: ACS 4.7
>Reporter: Remi Bergsma
>Assignee: Wilder Rodrigues
> Fix For: 4.7.1
>
>
> - deploy a rVPC
> - deploy VM in it
> - make port forwarding (2nd ip, firewall and such)
> - confirm it works
> - stop the vm
> - after some time the network garbage collector will come and tear down the 
> network since there are no more VMs
> - keepalived will enter FAULT state because of missing eth2 nic (which was 
> first network tier)
> - all is left is ethic (link local) and lo0
> - then start the vm again
> - the nics get plugged again and keepalived will decide on a new master
> - the nics are screwed up after this:
> ```
> root@r-1021-VM:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:02:92 brd ff:ff:ff:ff:ff:ff
> inet 169.254.2.146/16 brd 169.254.255.255 scope global eth0
> 5: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:18:34:00:05 brd ff:ff:ff:ff:ff:ff
> inet x.y.238.24/24 brd x.y.238.255 scope global eth1
> inet 10.0.0.51/24 brd 10.0.0.255 scope global eth1
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth1
> 6: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:d5:4e:00:00:1d brd ff:ff:ff:ff:ff:ff
> inet x.y.238.25/24 brd x.y.238.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global eth2
> root@r-1021-VM:~#
> ```
> Public and tier ip addresses are mixed up.
> /etc/cloudstack/ips.json has the wrong info:
> ```
> { 
>   
>  [44/959]
> "eth0": [
> {
> "add": true,
> "broadcast": "169.254.255.255",
> "cidr": "169.254.2.146/16",
> "device": "eth0",
> "gateway": "None",
> "netmask": "255.255.0.0",
> "network": "169.254.0.0/16",
> "nic_dev_id": "0",
> "nw_type": "control",
> "one_to_one_nat": false,
> "public_ip": "169.254.2.146",
> "size": "16",
> "source_nat": false
> }
>

[jira] [Commented] (CLOUDSTACK-9079) ipsec service is not running after restarting virtual router

2015-12-21 Thread Andrei Mikhailovsky (JIRA) 

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

Andrei Mikhailovsky commented on CLOUDSTACK-9079:
-

I've recently upgraded from 4.5.2 to 4.6.2 and have the issue with getting VPN 
to work. However, in my case I am unable to make the VPN work at all. I've 
tried removing and reinstalling the VPN service. I've tried restarting the VR 
and even restarting the network with the Clean up option. Nothing works. 

> ipsec service is not running after restarting virtual router
> 
>
> Key: CLOUDSTACK-9079
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9079
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router
>Affects Versions: 4.6.0
> Environment: ACS 4.5.1 upgraded to 4.6.0
>Reporter: Erik Weber
>Priority: Critical
>  Labels: systemvm, virtualrouter, vpn
>
> after upgrading to 4.6.0 the ipsec service does no longer automatically start 
> and as an effect vpn does not work.
> manually starting the ipsec service, or doing any vpn related configuration 
> (adding/deleting users) remedies the problem.
> Steps to reproduce:
> 1) Install ACS 4.6.0
> 2) Configure a VPC (I haven't tested with normal isolated networks)
> 3) Enable remote access VPN, configure a user
> 4) Confirm that VPN works
> 5) Restart the VR
> 6) Confirm that VPN does NOT work, either by trying to connect or by issuing 
> 'service ipsec status' on the VR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-21 Thread Nitin Kumar Maharana (JIRA) 

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

Nitin Kumar Maharana edited comment on CLOUDSTACK-9192 at 12/21/15 10:27 AM:
-

Hi [~weizhou], Sorry I saw your comment now. I have already created one. Thank 
you.


was (Author: nitin.maharana):
Hi [~ustcweiz...@gmail.com], Sorry I saw your comment now. I have already 
created one. Thank you.

> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-21 Thread Nitin Kumar Maharana (JIRA) 

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

Nitin Kumar Maharana commented on CLOUDSTACK-9192:
--

Hi [~ustcweiz...@gmail.com], Sorry I saw your comment now. I have already 
created one. Thank you.

> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9042:


GitHub user resmo opened a pull request:

https://github.com/apache/cloudstack/pull/1266

[4.4] CLOUDSTACK-9042: VR: DHCP: fix missing DHCP host enties

cherry-picked e7291fd600ce922a76b1fe9cd2c120a40d4cbc18 for 4.4 so bug can 
be closed after merging into 4.4.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/resmo/cloudstack fix/4.4/CLOUDSTACK-9042

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1266.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1266


commit fcdbc94a30607a0d90f4a4a3dc1b326970b029ee
Author: Rene Moser 
Date:   2015-11-06T11:25:10Z

CLOUDSTACK-9042: VR: DHCP: fix missing DHCP host enties

in /etc/dhcpentries.txt we had:

02:00:1e:07:01:53,set:10_102_92_5,10.102.92.5,songlog-1,infinite
02:00:0b:a2:00:3d,set:10_102_92_234,10.102.92.234,log-1,infinite

This sed matched unexpectetly "songlog-1" as well when "log-1" was 
processed, resulting
missing dhcp entry for songlog-1.

Also fixed other potenials problems relating to sed matching.




> VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
> ---
>
> Key: CLOUDSTACK-9042
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.4.4, 4.5.2
>Reporter: René Moser
>Assignee: René Moser
>Priority: Critical
> Fix For: 4.4.5, 4.5.3
>
>
> VR advanced networking.
> We experienced an issue when a few VMs were started at a time, some of them 
> and always the same ones did not receive a IP from DHCP. 
> After a debuging, we identified the problem in this sed command in 
> ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh
> the VM which was not in /etc/dhcphosts.txt was named:
> songlog-1
> When another VM was started named "log-1" the "songlog-1" entry was removed 
> unexpectedly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9193) Once password has been fetched, the state does not get updated to "saved_password"

2015-12-21 Thread Fred Neubauer (JIRA) 
Fred Neubauer created CLOUDSTACK-9193:
-

 Summary: Once password has been fetched, the state does not get 
updated to "saved_password"
 Key: CLOUDSTACK-9193
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9193
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.6.0
Reporter: Fred Neubauer
 Fix For: 4.4.4


When we deploy a vm for the first time the generated password is applied.

When we change the password and reboot, the changed password gets reset to the 
initially generated password or a newly generated on.

On the router vm the password file in /var/cache/cloud looks like this:

10.1.1.199=coth6harf2oG and stays that way even after the fetch.

On Cloudstack 4.4 the file gets updated like this once the password was fetched:

10.1.1.199=saved_password




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8867) Improve console proxy experience

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-8867:


GitHub user anshul1886 opened a pull request:

https://github.com/apache/cloudstack/pull/1269

CLOUDSTACK-8867: Added retry logic to reconnect to host on connection 
termination to console

It also improves handling of sessions to hypervisor in console proxy

https://issues.apache.org/jira/browse/CLOUDSTACK-8867


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-8867-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1269.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1269


commit 0f724d50c147429b800f45e77193a1f845ac80be
Author: Anshul Gangwar 
Date:   2015-09-16T04:45:32Z

CLOUDSTACK-8867: Added retry logic to reconnect to host on connection 
termination to console.
It also improves handling of sessions to hypervisor in console proxy




> Improve console proxy experience 
> -
>
> Key: CLOUDSTACK-8867
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8867
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
> Fix For: 4.6.1
>
>
> This bug is to avoid terminate connection errors in VM console in some of 
> following scenarios
> 1. VM reboots
> 2. Some key combinations input



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9164) Consoleproxy does not prevent Firefox Quicksearch when typing slash

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9164:


GitHub user anshul1886 opened a pull request:

https://github.com/apache/cloudstack/pull/1271

CLOUDSTACK-9164: Prevent firefox's quick search from opening in VM console

https://issues.apache.org/jira/browse/CLOUDSTACK-9164

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-9164

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1271.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1271


commit 8fe1f6d2900ffd45be9c82929fff67eca7816129
Author: Anshul Gangwar 
Date:   2015-12-22T06:29:09Z

CLOUDSTACK-9164: Prevent firefox's quick search from opening in VM console




> Consoleproxy does not prevent Firefox Quicksearch when typing slash
> ---
>
> Key: CLOUDSTACK-9164
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9164
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Usage
>Affects Versions: 4.5.2, 4.6.0
> Environment: ACS 4.6.0 w/ XenServer 6.5 running advanced Networking
>Reporter: Stephan Seitz
>  Labels: easyfix, patch
> Fix For: 4.6.0
>
>
> At least with recent Firefox-Browsers using the Consoleproxy results in 
> Firefox Quicksearch when typing slash ( / ).
> Furthermore, using a shell via Consoleproxy shows typical typing patterns 
> like slash,tab,return to get autocompetion of files.
> One has to be very attentive not to get into the Quicksearch ( / ), moving to 
> the ctrl-alt-del (tab) and reboot the VM without confirmation (return).
> The external lilnk points to a patch for ajaxviewer.js, mitigation that issue.
> Sorry for not cloning the project on github so far.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8867) Improve console proxy experience

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-8867:


Github user anshul1886 commented on the pull request:

https://github.com/apache/cloudstack/pull/835#issuecomment-166514436
  
Opening new PR with better handling of sessions.


> Improve console proxy experience 
> -
>
> Key: CLOUDSTACK-8867
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8867
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
> Fix For: 4.6.1
>
>
> This bug is to avoid terminate connection errors in VM console in some of 
> following scenarios
> 1. VM reboots
> 2. Some key combinations input



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9194) Allow resizable windows in IE for VM console

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9194:


GitHub user anshul1886 opened a pull request:

https://github.com/apache/cloudstack/pull/1270

CLOUDSTACK-9194:  Making the console popup window resizable in IE to make 
sure the focus is not lost

https://issues.apache.org/jira/browse/CLOUDSTACK-9194

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-9194

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1270.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1270


commit e985db90573accb2abb391c75223d111cb17a664
Author: Anshul Gangwar 
Date:   2015-05-08T10:29:54Z

CLOUDSTACK-9194:  Making the console popup window resizable in IE to make 
sure the focus is not lost.




> Allow resizable windows in IE for VM console
> 
>
> Key: CLOUDSTACK-9194
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9194
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>
> This will fix issues where VM console is bigger than browser window which 
> could lead to proper focus issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8867) Improve console proxy experience

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-8867:


Github user anshul1886 closed the pull request at:

https://github.com/apache/cloudstack/pull/835


> Improve console proxy experience 
> -
>
> Key: CLOUDSTACK-8867
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8867
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
> Fix For: 4.6.1
>
>
> This bug is to avoid terminate connection errors in VM console in some of 
> following scenarios
> 1. VM reboots
> 2. Some key combinations input



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9142) Migrate VM changes xmlDesc in an unsafe way

2015-12-21 Thread David Amorim Faria (JIRA) 

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

David Amorim Faria commented on CLOUDSTACK-9142:


As consequence, instances migrated to the first kvm node (the one that fully 
matches the mon_host string) cannot be migrated to other kvm nodes.

> Migrate VM changes xmlDesc in an unsafe way
> ---
>
> Key: CLOUDSTACK-9142
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9142
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server
>Affects Versions: 4.6.0, 4.7.0
>Reporter: David Amorim Faria
>Priority: Critical
>
> This issue appears with commit 
> https://github.com/apache/cloudstack/commit/a709f34ff93579981afbd4df0f4334b61ada29a8
> where xmlDesc has some content replaced: {code}
> xmlDesc = 
> dm.getXMLDesc(xmlFlag).replace(libvirtComputingResource.getPrivateIp(), 
> command.getDestinationIp());
> {code}
> This line from LibvirtComputingResource.java was refactored into 
> LibvirtMigrateCommandWrapper.java in commit 
> https://github.com/apache/cloudstack/commit/28e55462f15bdd8699e97b668c4ffc01735a533d
> Example, node1 is 10.0.0.1, node2 is 10.0.0.2, rbd mon_host is 10.0.0.13.
> VM is running on kvm node1 and this happened when migrating a VM from node1 
> to node2, where the kvm nodes and the RBD mon nodes (mon_host) use IP 
> addresses in the same range, and the mon_host has an ip address that 
> partially matches the ip address (string) of the first kvm node.
> In the process list one can see that the mon_host changes from 10.0.0.13 to 
> 10.0.0.23 in the destination host, blocking the migration after a timeout due 
> to primary storage not being available.
> {code}
> root 25206  1.8  0.0 440184 17188 ?Sl   13:33   0:00 
> /usr/libexec/qemu-kvm -name r-74-VM -S -machine 
> pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu 
> host,+rdtscp,+pdpe1gb,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
>  -m 256 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 
> 1a32b655-0acf-424b-8722-9e7f507a3070 -smbios type=1,manufacturer=Apache 
> Software Foundation,product=CloudStack KVM 
> Hypervisor,uuid=1a32b655-0acf-424b-8722-9e7f507a3070 -no-user-config 
> -nodefaults -chardev 
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-r-74-VM/monitor.sock,server,nowait
>  -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
> -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive 
> file=rbd:rbd/15ea00f9-e52e-43cf-9e5e-62188e9da5d2:id=cloudstack:key===:auth_supported=cephx\;none:mon_host=10.0.0.23\:6789,if=none,id=drive-virtio-disk0,format=raw,serial=15ea00f9e52e43cf9e5e,cache=none
>  -device 
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
>  -drive 
> file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw,cache=none
>  -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 
> -netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=33 -device 
> virtio-net-pci,netdev=hostnet0,id=net0,mac=11:11:11:11:11:11,bus=pci.0,addr=0x3,rombar=0,romfile=
>  -netdev tap,fd=34,id=hostnet1,vhost=on,vhostfd=35 -device 
> virtio-net-pci,netdev=hostnet1,id=net1,mac=22:22:22:22:22:22,bus=pci.0,addr=0x4,rombar=0,romfile=
>  -netdev tap,fd=36,id=hostnet2,vhost=on,vhostfd=37 -device 
> virtio-net-pci,netdev=hostnet2,id=net2,mac=33:33:33:33:33:33,bus=pci.0,addr=0x5,rombar=0,romfile=
>  -chardev pty,id=charserial0 -device 
> isa-serial,chardev=charserial0,id=serial0 -chardev 
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/r-74-VM.agent,server,nowait 
> -device 
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=r-74-VM.vport
>  -device usb-tablet,id=input0 -vnc 10.0.0.2:4,password -vga cirrus -incoming 
> tcp:[::]:49152 -msg timestamp=on
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9154) rVPC doesn't recover from cleaning up of network garbage collector

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9154:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1259#issuecomment-166244325
  
I had problems when running the tests: my test environment crashed. Could 
not test it before because I was on my way to France. Will restart the tests 
now.

Cheers,
Wilder


> rVPC doesn't recover from cleaning up of network garbage collector
> --
>
> Key: CLOUDSTACK-9154
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9154
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.6.0, 4.7.0, 4.6.1, 4.6.2
> Environment: ACS 4.7
>Reporter: Remi Bergsma
>Assignee: Wilder Rodrigues
> Fix For: 4.7.1
>
>
> - deploy a rVPC
> - deploy VM in it
> - make port forwarding (2nd ip, firewall and such)
> - confirm it works
> - stop the vm
> - after some time the network garbage collector will come and tear down the 
> network since there are no more VMs
> - keepalived will enter FAULT state because of missing eth2 nic (which was 
> first network tier)
> - all is left is ethic (link local) and lo0
> - then start the vm again
> - the nics get plugged again and keepalived will decide on a new master
> - the nics are screwed up after this:
> ```
> root@r-1021-VM:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:02:92 brd ff:ff:ff:ff:ff:ff
> inet 169.254.2.146/16 brd 169.254.255.255 scope global eth0
> 5: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:18:34:00:05 brd ff:ff:ff:ff:ff:ff
> inet x.y.238.24/24 brd x.y.238.255 scope global eth1
> inet 10.0.0.51/24 brd 10.0.0.255 scope global eth1
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth1
> 6: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:d5:4e:00:00:1d brd ff:ff:ff:ff:ff:ff
> inet x.y.238.25/24 brd x.y.238.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global eth2
> root@r-1021-VM:~#
> ```
> Public and tier ip addresses are mixed up.
> /etc/cloudstack/ips.json has the wrong info:
> ```
> { 
>   
>  [44/959]
> "eth0": [
> {
> "add": true,
> "broadcast": "169.254.255.255",
> "cidr": "169.254.2.146/16",
> "device": "eth0",
> "gateway": "None",
> "netmask": "255.255.0.0",
> "network": "169.254.0.0/16",
> "nic_dev_id": "0",
> "nw_type": "control",
> "one_to_one_nat": false,
> "public_ip": "169.254.2.146",
> "size": "16",
> "source_nat": false
> }
> ],
> "eth1": [
> {
> "add": true,
> "broadcast": "x.y.238.255",
> "cidr": "x.y.238.24/24",
> "device": "eth1",
> "first_i_p": true,
> "gateway": "x.y.238.1",
> "netmask": "255.255.255.0",
> "network": "x.y.238.0/24",
> "new_nic": false,
> "nic_dev_id": 1,
> "nw_type": "public",
> "one_to_one_nat": false,
> "public_ip": "x.y.238.24",
> "size": "24",
> "source_nat": true,
> "vif_mac_address": "06:fc:da:00:00:1c"
> },
> {
> "add": true,
> "broadcast": "10.0.0.255",
> "cidr": "10.0.0.51/24",
> "device": "eth1",
> "gateway": "10.0.0.1",
> "netmask": "255.255.255.0",
> "network": "10.0.0.0/24",
> "nic_dev_id": "1",
> "nw_type": "guest",
> "one_to_one_nat": false,
> "public_ip": "10.0.0.51",
> "size": "24",
> "source_nat": false
> }
> ],
> "eth2": [
> {
> "add": false,
> "broadcast": "10.0.0.255",
> "cidr": "10.0.0.173/24",
> "device": "eth2",
> "gateway": "10.0.0.1",
> "netmask": "255.255.255.0",
>

[jira] [Updated] (CLOUDSTACK-9142) Migrate VM changes xmlDesc in an unsafe way

2015-12-21 Thread David Amorim Faria (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Amorim Faria updated CLOUDSTACK-9142:
---
Priority: Critical  (was: Major)

> Migrate VM changes xmlDesc in an unsafe way
> ---
>
> Key: CLOUDSTACK-9142
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9142
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server
>Affects Versions: 4.6.0, 4.7.0
>Reporter: David Amorim Faria
>Priority: Critical
>
> This issue appears with commit 
> https://github.com/apache/cloudstack/commit/a709f34ff93579981afbd4df0f4334b61ada29a8
> where xmlDesc has some content replaced: {code}
> xmlDesc = 
> dm.getXMLDesc(xmlFlag).replace(libvirtComputingResource.getPrivateIp(), 
> command.getDestinationIp());
> {code}
> This line from LibvirtComputingResource.java was refactored into 
> LibvirtMigrateCommandWrapper.java in commit 
> https://github.com/apache/cloudstack/commit/28e55462f15bdd8699e97b668c4ffc01735a533d
> Example, node1 is 10.0.0.1, node2 is 10.0.0.2, rbd mon_host is 10.0.0.13.
> VM is running on kvm node1 and this happened when migrating a VM from node1 
> to node2, where the kvm nodes and the RBD mon nodes (mon_host) use IP 
> addresses in the same range, and the mon_host has an ip address that 
> partially matches the ip address (string) of the first kvm node.
> In the process list one can see that the mon_host changes from 10.0.0.13 to 
> 10.0.0.23 in the destination host, blocking the migration after a timeout due 
> to primary storage not being available.
> {code}
> root 25206  1.8  0.0 440184 17188 ?Sl   13:33   0:00 
> /usr/libexec/qemu-kvm -name r-74-VM -S -machine 
> pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu 
> host,+rdtscp,+pdpe1gb,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
>  -m 256 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 
> 1a32b655-0acf-424b-8722-9e7f507a3070 -smbios type=1,manufacturer=Apache 
> Software Foundation,product=CloudStack KVM 
> Hypervisor,uuid=1a32b655-0acf-424b-8722-9e7f507a3070 -no-user-config 
> -nodefaults -chardev 
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-r-74-VM/monitor.sock,server,nowait
>  -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
> -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive 
> file=rbd:rbd/15ea00f9-e52e-43cf-9e5e-62188e9da5d2:id=cloudstack:key===:auth_supported=cephx\;none:mon_host=10.0.0.23\:6789,if=none,id=drive-virtio-disk0,format=raw,serial=15ea00f9e52e43cf9e5e,cache=none
>  -device 
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
>  -drive 
> file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw,cache=none
>  -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 
> -netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=33 -device 
> virtio-net-pci,netdev=hostnet0,id=net0,mac=11:11:11:11:11:11,bus=pci.0,addr=0x3,rombar=0,romfile=
>  -netdev tap,fd=34,id=hostnet1,vhost=on,vhostfd=35 -device 
> virtio-net-pci,netdev=hostnet1,id=net1,mac=22:22:22:22:22:22,bus=pci.0,addr=0x4,rombar=0,romfile=
>  -netdev tap,fd=36,id=hostnet2,vhost=on,vhostfd=37 -device 
> virtio-net-pci,netdev=hostnet2,id=net2,mac=33:33:33:33:33:33,bus=pci.0,addr=0x5,rombar=0,romfile=
>  -chardev pty,id=charserial0 -device 
> isa-serial,chardev=charserial0,id=serial0 -chardev 
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/r-74-VM.agent,server,nowait 
> -device 
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=r-74-VM.vport
>  -device usb-tablet,id=input0 -vnc 10.0.0.2:4,password -vga cirrus -incoming 
> tcp:[::]:49152 -msg timestamp=on
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9192:


Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1264#issuecomment-166258585
  
Hi @ustcweizhou, The error function is not necessary but it is good to 
write this in call. Here the request doesn't fail but throws an error. Thanks 
for the comment, I will update.


> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-8302:


Github user dmytro-shevchenko commented on the pull request:

https://github.com/apache/cloudstack/pull/1230#issuecomment-166261539
  
Full snapshot path added into log messages.


> Cleanup snapshot on KVM with RBD
> 
>
> Key: CLOUDSTACK-8302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot, Storage Controller
>Affects Versions: 4.4.0, 4.4.1, 4.4.2
> Environment: CloudStack 4.4.2 + KVM on CentOS 6.6 + Ceph/RBD 0.80.8
>Reporter: Star Guo
>Assignee: Wido den Hollander
>Priority: Critical
>
> I just build a lab with CloudStack 4.4.2 + CentOS 6.6 KVM + Ceph/RBD 0.80.8.
> I deploy an instance on RBD and I create the ROOT volume snapshots. When 
> delete a snapshot the UI show OK, but the snapshot of the volume in the RBD 
> pool is still exist.
> And I find the code in 
> com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java: 
> …
> @Override
> public Answer deleteSnapshot(DeleteCommand cmd) {
> return new Answer(cmd);
> }
> …
> deleteSnapshot() does not be implememented. And I also find the code:
> ...
> @Override
> public Answer createTemplateFromSnapshot(CopyCommand cmd) {
> return null;  //To change body of implemented methods use File | 
> Settings | File Templates.
> }
> ...
> So does createTenokateFromSnapshot(). I just look for it in MASTER branch but 
> not do that yet. Will CloudStack Dev Team plan to do that ? Thanks .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9194) Allow resizable windows in IE for VM console

2015-12-21 Thread Anshul Gangwar (JIRA) 
Anshul Gangwar created CLOUDSTACK-9194:
--

 Summary: Allow resizable windows in IE for VM console
 Key: CLOUDSTACK-9194
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9194
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Anshul Gangwar
Assignee: Anshul Gangwar


This will fix issues where VM console is bigger than browser window which could 
lead to proper focus issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-6448) VPC router won't be created when a private gateway is defined.

2015-12-21 Thread Anton Opgenoort (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Opgenoort updated CLOUDSTACK-6448:

Affects Version/s: 4.7.1
   4.7.0
   4.5.2
   4.6.0

> VPC router won't be created when a private gateway is defined. 
> ---
>
> Key: CLOUDSTACK-6448
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6448
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices, Virtual Router
>Affects Versions: 4.3.0, 4.4.0, 4.3.1, 4.5.2, 4.6.0, 4.7.0, 4.7.1
>Reporter: Anton Opgenoort
>Assignee: Saksham Srivastava
>
> Reproduce by creating a VPC, adding a gateway, and destroy the associated 
> virtual router. Then try to start a VM in one of the VPC network tiers; this 
> results in message below, and routerVM is not started for VPC network. 
> Then remove the private gateway, and start a VM again. Now the routerVM is 
> started normally, and the VM is being provisioned. 
> 2014-04-18 10:35:04,895 DEBUG [c.c.v.VirtualMachineManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) VM is being created in podId: 1
> 2014-04-18 10:35:04,907 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Network id=1143 is already 
> implemented
> 2014-04-18 10:35:04,943 DEBUG [c.c.n.NetworkModelImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Service SecurityGroup is not 
> supported in the network id=1143
> 2014-04-18 10:35:04,958 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Changing active number of nics 
> for network id=1143 on 1
> 2014-04-18 10:35:04,973 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Asking VpcVirtualRouter to 
> prepare for Nic[98879-15684-e51a9969-e1f1-4c45-ad65-761e51435b90-10.1.1.98]
> 2014-04-18 10:35:04,979 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Deploying Virtual Router in VPC 
> [VPC [313-mccoat1]
> 2014-04-18 10:35:05,006 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Adding nic for Virtual Router in 
> Control network 
> 2014-04-18 10:35:05,014 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Found existing network 
> configuration for offering [Network Offering 
> [5-Control-System-Control-Network]: Ntwk[202|Control|5]
> 2014-04-18 10:35:05,014 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Releasing lock for 
> Acct[5083d876-e429-4aa4-bb9a-1958ad753f18-system]
> 2014-04-18 10:35:05,016 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Adding nic for Virtual Router in 
> Public network 
> 2014-04-18 10:35:05,026 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Found existing network 
> configuration for offering [Network Offering 
> [1-Public-System-Public-Network]: Ntwk[200|Public|1]
> 2014-04-18 10:35:05,026 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Releasing lock for 
> Acct[5083d876-e429-4aa4-bb9a-1958ad753f18-system]
> 2014-04-18 10:35:05,055 ERROR [c.c.v.VirtualMachineManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Failed to start instance 
> VM[User|antontest-cloud-1600]
> java.lang.NullPointerException
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createPrivateNicProfileForGateway(VpcVirtualNetworkApplianceManagerImpl.java:1290)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createVpcRouterNetworks(VpcVirtualNetworkApplianceManagerImpl.java:1231)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVpcRouter(VpcVirtualNetworkApplianceManagerImpl.java:344)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:234)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:183)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
>

[jira] [Reopened] (CLOUDSTACK-6448) VPC router won't be created when a private gateway is defined.

2015-12-21 Thread Anton Opgenoort (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Opgenoort reopened CLOUDSTACK-6448:
-

Re-tested this with ACS 4.7.0, and the issue is still present. 
This is done with a non-redundant VPC router, and a private gateway 
configuration with provider NiciraNvp. 



> VPC router won't be created when a private gateway is defined. 
> ---
>
> Key: CLOUDSTACK-6448
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6448
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices, Virtual Router
>Affects Versions: 4.3.0, 4.4.0, 4.3.1
>Reporter: Anton Opgenoort
>Assignee: Saksham Srivastava
>
> Reproduce by creating a VPC, adding a gateway, and destroy the associated 
> virtual router. Then try to start a VM in one of the VPC network tiers; this 
> results in message below, and routerVM is not started for VPC network. 
> Then remove the private gateway, and start a VM again. Now the routerVM is 
> started normally, and the VM is being provisioned. 
> 2014-04-18 10:35:04,895 DEBUG [c.c.v.VirtualMachineManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) VM is being created in podId: 1
> 2014-04-18 10:35:04,907 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Network id=1143 is already 
> implemented
> 2014-04-18 10:35:04,943 DEBUG [c.c.n.NetworkModelImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Service SecurityGroup is not 
> supported in the network id=1143
> 2014-04-18 10:35:04,958 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Changing active number of nics 
> for network id=1143 on 1
> 2014-04-18 10:35:04,973 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Asking VpcVirtualRouter to 
> prepare for Nic[98879-15684-e51a9969-e1f1-4c45-ad65-761e51435b90-10.1.1.98]
> 2014-04-18 10:35:04,979 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Deploying Virtual Router in VPC 
> [VPC [313-mccoat1]
> 2014-04-18 10:35:05,006 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Adding nic for Virtual Router in 
> Control network 
> 2014-04-18 10:35:05,014 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Found existing network 
> configuration for offering [Network Offering 
> [5-Control-System-Control-Network]: Ntwk[202|Control|5]
> 2014-04-18 10:35:05,014 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Releasing lock for 
> Acct[5083d876-e429-4aa4-bb9a-1958ad753f18-system]
> 2014-04-18 10:35:05,016 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Adding nic for Virtual Router in 
> Public network 
> 2014-04-18 10:35:05,026 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Found existing network 
> configuration for offering [Network Offering 
> [1-Public-System-Public-Network]: Ntwk[200|Public|1]
> 2014-04-18 10:35:05,026 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Releasing lock for 
> Acct[5083d876-e429-4aa4-bb9a-1958ad753f18-system]
> 2014-04-18 10:35:05,055 ERROR [c.c.v.VirtualMachineManagerImpl] 
> (Job-Executor-74:ctx-37d3b587 ctx-641440ee) Failed to start instance 
> VM[User|antontest-cloud-1600]
> java.lang.NullPointerException
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createPrivateNicProfileForGateway(VpcVirtualNetworkApplianceManagerImpl.java:1290)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createVpcRouterNetworks(VpcVirtualNetworkApplianceManagerImpl.java:1231)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVpcRouter(VpcVirtualNetworkApplianceManagerImpl.java:344)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:234)
> at 
> com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:183)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
>

[jira] [Commented] (CLOUDSTACK-9154) rVPC doesn't recover from cleaning up of network garbage collector

2015-12-21 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9154:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1259#issuecomment-166357140
  
Ping @remibergsma @miguelaferreira @DaanHoogland @borisroman 

The changes in this PR affected a couple of of RVRs. I got tests failing 
(default allow/deny egress and routing). Tried to do the same manually and it 
did not work.

Will investigate and submit fixes. Please, do not merge this.

Cheers,
Wilder


> rVPC doesn't recover from cleaning up of network garbage collector
> --
>
> Key: CLOUDSTACK-9154
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9154
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.6.0, 4.7.0, 4.6.1, 4.6.2
> Environment: ACS 4.7
>Reporter: Remi Bergsma
>Assignee: Wilder Rodrigues
> Fix For: 4.7.1
>
>
> - deploy a rVPC
> - deploy VM in it
> - make port forwarding (2nd ip, firewall and such)
> - confirm it works
> - stop the vm
> - after some time the network garbage collector will come and tear down the 
> network since there are no more VMs
> - keepalived will enter FAULT state because of missing eth2 nic (which was 
> first network tier)
> - all is left is ethic (link local) and lo0
> - then start the vm again
> - the nics get plugged again and keepalived will decide on a new master
> - the nics are screwed up after this:
> ```
> root@r-1021-VM:~# ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 0e:00:a9:fe:02:92 brd ff:ff:ff:ff:ff:ff
> inet 169.254.2.146/16 brd 169.254.255.255 scope global eth0
> 5: eth1:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:18:34:00:05 brd ff:ff:ff:ff:ff:ff
> inet x.y.238.24/24 brd x.y.238.255 scope global eth1
> inet 10.0.0.51/24 brd 10.0.0.255 scope global eth1
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth1
> 6: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 06:d5:4e:00:00:1d brd ff:ff:ff:ff:ff:ff
> inet x.y.238.25/24 brd x.y.238.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global eth2
> root@r-1021-VM:~#
> ```
> Public and tier ip addresses are mixed up.
> /etc/cloudstack/ips.json has the wrong info:
> ```
> { 
>   
>  [44/959]
> "eth0": [
> {
> "add": true,
> "broadcast": "169.254.255.255",
> "cidr": "169.254.2.146/16",
> "device": "eth0",
> "gateway": "None",
> "netmask": "255.255.0.0",
> "network": "169.254.0.0/16",
> "nic_dev_id": "0",
> "nw_type": "control",
> "one_to_one_nat": false,
> "public_ip": "169.254.2.146",
> "size": "16",
> "source_nat": false
> }
> ],
> "eth1": [
> {
> "add": true,
> "broadcast": "x.y.238.255",
> "cidr": "x.y.238.24/24",
> "device": "eth1",
> "first_i_p": true,
> "gateway": "x.y.238.1",
> "netmask": "255.255.255.0",
> "network": "x.y.238.0/24",
> "new_nic": false,
> "nic_dev_id": 1,
> "nw_type": "public",
> "one_to_one_nat": false,
> "public_ip": "x.y.238.24",
> "size": "24",
> "source_nat": true,
> "vif_mac_address": "06:fc:da:00:00:1c"
> },
> {
> "add": true,
> "broadcast": "10.0.0.255",
> "cidr": "10.0.0.51/24",
> "device": "eth1",
> "gateway": "10.0.0.1",
> "netmask": "255.255.255.0",
> "network": "10.0.0.0/24",
> "nic_dev_id": "1",
> "nw_type": "guest",
> "one_to_one_nat": false,
> "public_ip": "10.0.0.51",
> "size": "24",
> "source_nat": false
> }
> ],
> "eth2": [
> {
> "add": false,
> "broadcast": "10.0.0.255",
>