[jira] [Commented] (CLOUDSTACK-9779) Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing rule

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9779:
-

Commit feb5fa901e09c6a1638e6398e2543d77ee5aa21b in cloudstack's branch 
refs/heads/master from [~niteshsarda]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=feb5fa9 ]

CLOUDSTACK-9779 : Releasing secondary guest IP fails with error VM nic Ip 
x.x.x.x is mapped to load balancing rule


> Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to 
> load balancing rule
> 
>
> Key: CLOUDSTACK-9779
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9779
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Nitesh Sarda
>
> ISSUE 
> =
> Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to 
> load balancing rule
> REPRO STEPS
> ==
> 1. Create two isolated guest networks with same CIDR
> 2. Deploy VMs on both networks
> 3. Acquire secondary IP on NICs of both VMs and make sure they have the same 
> value, user can input the IP address.
> 4. Configure Loadbalancing rule on one of the secondary IP address and try 
> releasing the other secondary IP address.
> 5. The operation would fail
> EXPECTED BEHAVIOR
> ==
> Secondary IP address should be released if there are no LB rules associated 
> with it.
> ACTUAL BEHAVIOR
> ==
> Releasing secondary IP address even if there are no LB rules associated with 
> it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9762) Management Server UI (VM statistics page) CPU Utilized value is incorrect.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9762:
-

Commit b676a8a7c3fd554d87afdac6328d9ac5d0265308 in cloudstack's branch 
refs/heads/master from Rene Moser
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=b676a8a ]

Bug fix for CLOUDSTACK-9762   Management Server UI (VM statistics page) CPU 
Utilized value is incorrect.


> Management Server UI (VM statistics page) CPU Utilized value is incorrect.
> --
>
> Key: CLOUDSTACK-9762
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9762
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.8.0
> Environment: VMWare version 5.5.0.
>Reporter: jay
> Fix For: 4.10.0.0
>
>
> Management Server UI shows virtual machine  CPU Utilized value greater than 
> 100%.
> Behaviour is observed in VMware hypervisor only.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9630) Cannot use listNics API as advertised

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9630:
-

Commit e7326b10ef1f51b470df6b683e1e06d753fb02f7 in cloudstack's branch 
refs/heads/master from [~sudhansu]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=e7326b1 ]

CLOUDSTACK-9630: Cannot use listNics API as advertised

added missing  details for listNics API response.


> Cannot use listNics API as advertised
> -
>
> Key: CLOUDSTACK-9630
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9630
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Sudhansu Sahu
>
> listNics API for a VM, "type" was not returned within API response. 
> EXPECTED BEHAVIOR
> ==
> The listNics API response return type of NIC (type), as specified in 
> https://cloudstack.apache.org/api/apidocs-4.8/user/listNics.html
>  
> ACTUAL BEHAVIOR
> ==
> The listNics API response does not return type of NIC.
> (local)  > list nics virtualmachineid=a69edaf5-8f21-41ff-8c05-263dc4bd5354 
> count = 1
> nic:
> id = 211e0d46-6b94-4425-99f7-e8e9efea2472
> deviceid = 0
> gateway = 10.1.1.1
> ipaddress = 10.1.1.45
> isdefault = True
> macaddress = 02:00:06:f6:00:01
> netmask = 255.255.255.0
> networkid = c08fddf1-fd77-4810-a062-ea9d03c5c7e6
> virtualmachineid = a69edaf5-8f21-41ff-8c05-263dc4bd5354
>  
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9695:
-

Commit 64776f38d625335afbd3110d8efab36a710fd6d6 in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=64776f3 ]

Merge pull request #1852 from Accelerite/CLOUDSTACK-9695

CLOUDSTACK-9695: VM snapshot is disabled if the VM Instance is off

> For VM in stopped state, disable "Snapshot Memory" option
> -
>
> Key: CLOUDSTACK-9695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Minor
> Fix For: 4.10.0.0
>
>
> For a VM in stopped state, the UI for VM snapshot creation shows an option 
> for 'snapshot memory'. Since this is not a valid option at that point, it 
> should be disabled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9871) MySQL 5.7 compatibility

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9871:
-

Commit cab0869bd4fc0501237797462d3b7f783ad50a56 in cloudstack's branch 
refs/heads/4.9 from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=cab0869 ]

Merge pull request #2037 from wido/sql_mode

CLOUDSTACK-9871: Set SQL Mode in SQL Session for MySQL 5.7 compatibility

> MySQL 5.7 compatibility
> ---
>
> Key: CLOUDSTACK-9871
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9871
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.10.0.0
> Environment: Ubuntu 16.04, MySQL 5.7
>Reporter: Wido den Hollander
>Priority: Minor
>  Labels: jdbc, mysql
>
> MySQL 5.7 comes with a more strict SQL mode by default which causes problems 
> for CloudStack as the queries it executes are not all compatible with MySQL 
> 5.7.
> https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
> A work-around is setting the sql_mode to a more relaxed mode in the my.cnf:
> [mysqld]
> sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> In the future CloudStack should be fully compatible with the new SQL mode.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9871) MySQL 5.7 compatibility

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9871:
-

Commit 0c1c27ba85bbe6812e7d07fe05e999abf0574b33 in cloudstack's branch 
refs/heads/4.9 from [~widodh]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=0c1c27b ]

CLOUDSTACK-9871: Set SQL Mode in SQL Session for MySQL 5.7 compatibility

MySQL 5.7 has a more strict SQL mode by default with which CloudStack
is not compatible.

By setting the SQL Mode to a more relaxed mode on run-time we can
run without changing any SQL server settings.

Admins could also apply this to the [mysqld] section of their my.cnf:

sql_mode = 
'STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'

Signed-off-by: Wido den Hollander 


> MySQL 5.7 compatibility
> ---
>
> Key: CLOUDSTACK-9871
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9871
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.10.0.0
> Environment: Ubuntu 16.04, MySQL 5.7
>Reporter: Wido den Hollander
>Priority: Minor
>  Labels: jdbc, mysql
>
> MySQL 5.7 comes with a more strict SQL mode by default which causes problems 
> for CloudStack as the queries it executes are not all compatible with MySQL 
> 5.7.
> https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
> A work-around is setting the sql_mode to a more relaxed mode in the my.cnf:
> [mysqld]
> sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> In the future CloudStack should be fully compatible with the new SQL mode.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9695:
-

Commit 64776f38d625335afbd3110d8efab36a710fd6d6 in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=64776f3 ]

Merge pull request #1852 from Accelerite/CLOUDSTACK-9695

CLOUDSTACK-9695: VM snapshot is disabled if the VM Instance is off

> For VM in stopped state, disable "Snapshot Memory" option
> -
>
> Key: CLOUDSTACK-9695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Minor
> Fix For: 4.10.0.0
>
>
> For a VM in stopped state, the UI for VM snapshot creation shows an option 
> for 'snapshot memory'. Since this is not a valid option at that point, it 
> should be disabled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9630) Cannot use listNics API as advertised

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9630:
-

Commit 3f6d27faab68ac414859edb3fa3732abf938ad57 in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3f6d27f ]

Merge pull request #1797 from sudhansu7/CLOUDSTACK-9630

CLOUDSTACK-9630: Cannot use listNics API as advertised

> Cannot use listNics API as advertised
> -
>
> Key: CLOUDSTACK-9630
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9630
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Sudhansu Sahu
>
> listNics API for a VM, "type" was not returned within API response. 
> EXPECTED BEHAVIOR
> ==
> The listNics API response return type of NIC (type), as specified in 
> https://cloudstack.apache.org/api/apidocs-4.8/user/listNics.html
>  
> ACTUAL BEHAVIOR
> ==
> The listNics API response does not return type of NIC.
> (local)  > list nics virtualmachineid=a69edaf5-8f21-41ff-8c05-263dc4bd5354 
> count = 1
> nic:
> id = 211e0d46-6b94-4425-99f7-e8e9efea2472
> deviceid = 0
> gateway = 10.1.1.1
> ipaddress = 10.1.1.45
> isdefault = True
> macaddress = 02:00:06:f6:00:01
> netmask = 255.255.255.0
> networkid = c08fddf1-fd77-4810-a062-ea9d03c5c7e6
> virtualmachineid = a69edaf5-8f21-41ff-8c05-263dc4bd5354
>  
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9630) Cannot use listNics API as advertised

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-9630:
-

Commit 3f6d27faab68ac414859edb3fa3732abf938ad57 in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3f6d27f ]

Merge pull request #1797 from sudhansu7/CLOUDSTACK-9630

CLOUDSTACK-9630: Cannot use listNics API as advertised

> Cannot use listNics API as advertised
> -
>
> Key: CLOUDSTACK-9630
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9630
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Sudhansu Sahu
>
> listNics API for a VM, "type" was not returned within API response. 
> EXPECTED BEHAVIOR
> ==
> The listNics API response return type of NIC (type), as specified in 
> https://cloudstack.apache.org/api/apidocs-4.8/user/listNics.html
>  
> ACTUAL BEHAVIOR
> ==
> The listNics API response does not return type of NIC.
> (local)  > list nics virtualmachineid=a69edaf5-8f21-41ff-8c05-263dc4bd5354 
> count = 1
> nic:
> id = 211e0d46-6b94-4425-99f7-e8e9efea2472
> deviceid = 0
> gateway = 10.1.1.1
> ipaddress = 10.1.1.45
> isdefault = True
> macaddress = 02:00:06:f6:00:01
> netmask = 255.255.255.0
> networkid = c08fddf1-fd77-4810-a062-ea9d03c5c7e6
> virtualmachineid = a69edaf5-8f21-41ff-8c05-263dc4bd5354
>  
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)