[jira] [Updated] (CLOUDSTACK-9225) Isolation in Advanced Zone using PVLANs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja updated CLOUDSTACK-9225: Fix Version/s: 4.9.0 > Isolation in Advanced Zone using PVLANs > > > Key: CLOUDSTACK-9225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9225 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 > Environment: CentOS 6.x CS 4.5.2 >Reporter: Keerthiraja > Fix For: 4.8.0, 4.9.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN > With reference to above WiKi tried out to setup PVLAN it didn't work > Where I could see ovs plugin issue. > This is been already identfied not sure on which tracker we are following. > But still I could see the problem existis in 4.6 & 4.7 too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9225) Isolation in Advanced Zone using PVLANs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja updated CLOUDSTACK-9225: Fix Version/s: 4.8.0 > Isolation in Advanced Zone using PVLANs > > > Key: CLOUDSTACK-9225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9225 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 > Environment: CentOS 6.x CS 4.5.2 >Reporter: Keerthiraja > Fix For: 4.8.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN > With reference to above WiKi tried out to setup PVLAN it didn't work > Where I could see ovs plugin issue. > This is been already identfied not sure on which tracker we are following. > But still I could see the problem existis in 4.6 & 4.7 too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9225) Isolation in Advanced Zone using PVLANs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124178#comment-15124178 ] Keerthiraja commented on CLOUDSTACK-9225: - Will there be any plan to workaround this on 4.8 > Isolation in Advanced Zone using PVLANs > > > Key: CLOUDSTACK-9225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9225 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 > Environment: CentOS 6.x CS 4.5.2 >Reporter: Keerthiraja > Fix For: 4.8.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN > With reference to above WiKi tried out to setup PVLAN it didn't work > Where I could see ovs plugin issue. > This is been already identfied not sure on which tracker we are following. > But still I could see the problem existis in 4.6 & 4.7 too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9225) Isolation in Advanced Zone using PVLANs
Keerthiraja created CLOUDSTACK-9225: --- Summary: Isolation in Advanced Zone using PVLANs Key: CLOUDSTACK-9225 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9225 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.2 Environment: CentOS 6.x CS 4.5.2 Reporter: Keerthiraja https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN With reference to above WiKi tried out to setup PVLAN it didn't work Where I could see ovs plugin issue. This is been already identfied not sure on which tracker we are following. But still I could see the problem existis in 4.6 & 4.7 too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7446) Openvswitch plugin has duplicate names
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031568#comment-15031568 ] Keerthiraja commented on CLOUDSTACK-7446: - As per on below link doc PVLAN setup is not working on the CS 4.5.2 https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN let this will be updated on upcoming version 4.5.3 and 4.6.1 > Openvswitch plugin has duplicate names > -- > > Key: CLOUDSTACK-7446 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7446 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.4.0 > Environment: Ubuntu 14.04 LTS >Reporter: Vadim Kim. > Attachments: network_providers.jpg > > > Openvswitch plugin at Network Service Providers has duplicate names - "Ovs" > and "OVS". > 1. Pushing "OVS" does nothing. Management server log does not log anything > 2. Pushing "Ovs" generate error at managment server log: > Api Discovery plugin was unable to find an api by that name or process -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8836) Cloudstack 4.5.2 Not starting on Fresh install on MariaDB-server-10.0.21-1
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742533#comment-14742533
]
Keerthiraja commented on CLOUDSTACK-8836:
-
This issue been identified and able to resolve this by below method.
stop cloud-management
stop MariaDB
Need to comment the query and update the new one mention below.
/usr/share/cloudstack-management/setup/db/schema-421to430.sql
#realhostip changes, before changing table and adding default value
#UPDATE `cloud`.`configuration` SET value = CONCAT("*.",(SELECT
`temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE
`name`="consoleproxy.url.domain") AS `temptable` WHERE
`temptable`.`name`="consoleproxy.url.domain")) WHERE
`name`="consoleproxy.url.domain";
#UPDATE `cloud`.`configuration` SET `value` = CONCAT("*.",(SELECT
`temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE
`name`="secstorage.ssl.cert.domain") AS `temptable` WHERE
`temptable`.`name`="secstorage.ssl.cert.domain")) WHERE
`name`="secstorage.ssl.cert.domain";
UPDATE `cloud`.`configuration` SET value=CONCAT("*.",value) WHERE
`name`="consoleproxy.url.domain" OR `name`="consoleproxy.url.domain";
UPDATE `cloud`.`configuration` SET value=CONCAT("*.",value) WHERE
`name`="secstorage.ssl.cert.domain" OR `name`="secstorage.ssl.cert.domain";
Then redeploy the cloudstack-database
Then start the service all seems to be working fine without any issue.
Not sure will this be patched very soon no the version 4.5.3 and 4.6.
> Cloudstack 4.5.2 Not starting on Fresh install on MariaDB-server-10.0.21-1
> --
>
> Key: CLOUDSTACK-8836
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8836
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.5.2
> Environment: CentOS 6.7 with MariaDB-server-10.0.21-1.el6.x86_64.
>Reporter: Keerthiraja
>Priority: Blocker
> Fix For: 4.5.3
>
>
> After the successful installation along with cloudstack-setup-database.
> I tried to start the cloudstack services. During the time I could see the
> tomcat fails to start. Pasted the ERROR below.
> Kindly can someone help me out on this as soon as possible. I am right now in
> client place to implement for production setup.
> Error
>
> ERROR
> ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
> `cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
> FROM (SELECT * FROM `cloud`.`configuration` WHERE
> `name`="consoleproxy.url.domain") AS `temptable` WHERE
> `temptable`.`name`="consoleproxy.url.domain")) WHERE
> `name`="consoleproxy.url.domain"
> ERROR [c.c.u.d.ScriptRunner] (main:null)
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> The last packet successfully received from the server was 25 milliseconds
> ago. The last packet sent successfully to the server was 25 milliseconds ago.
> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> Caused by: java.net.SocketException: Broken pipe
> ... 61 more
> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the
> database
> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
> ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> I did this test number of times by allocating fresh box.
> Thanks,
> Keerthi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8836) Cloudstack 4.5.2 Not starting on Fresh install on MariaDB-server-10.0.21-1
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keerthiraja updated CLOUDSTACK-8836:
Summary: Cloudstack 4.5.2 Not starting on Fresh install on
MariaDB-server-10.0.21-1 (was: Cloudstack 4.5.2 Not starting on Fresh install)
> Cloudstack 4.5.2 Not starting on Fresh install on MariaDB-server-10.0.21-1
> --
>
> Key: CLOUDSTACK-8836
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8836
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.5.2
> Environment: CentOS 6.7 with MariaDB-server-10.0.21-1.el6.x86_64.
>Reporter: Keerthiraja
>Priority: Blocker
> Fix For: 4.5.3
>
>
> After the successful installation along with cloudstack-setup-database.
> I tried to start the cloudstack services. During the time I could see the
> tomcat fails to start. Pasted the ERROR below.
> Kindly can someone help me out on this as soon as possible. I am right now in
> client place to implement for production setup.
> Error
>
> ERROR
> ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
> `cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
> FROM (SELECT * FROM `cloud`.`configuration` WHERE
> `name`="consoleproxy.url.domain") AS `temptable` WHERE
> `temptable`.`name`="consoleproxy.url.domain")) WHERE
> `name`="consoleproxy.url.domain"
> ERROR [c.c.u.d.ScriptRunner] (main:null)
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> The last packet successfully received from the server was 25 milliseconds
> ago. The last packet sent successfully to the server was 25 milliseconds ago.
> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> Caused by: java.net.SocketException: Broken pipe
> ... 61 more
> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the
> database
> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
> ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> I did this test number of times by allocating fresh box.
> Thanks,
> Keerthi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8836) Cloudstack 4.5.2 Not starting on Fresh install
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keerthiraja updated CLOUDSTACK-8836:
Description:
After the successful installation along with cloudstack-setup-database.
I tried to start the cloudstack services. During the time I could see the
tomcat fails to start. Pasted the ERROR below.
Kindly can someone help me out on this as soon as possible. I am right now in
client place to implement for production setup.
Error
ERROR
ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
`cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
FROM (SELECT * FROM `cloud`.`configuration` WHERE
`name`="consoleproxy.url.domain") AS `temptable` WHERE
`temptable`.`name`="consoleproxy.url.domain")) WHERE
`name`="consoleproxy.url.domain"
ERROR [c.c.u.d.ScriptRunner] (main:null)
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
The last packet successfully received from the server was 25 milliseconds ago.
The last packet sent successfully to the server was 25 milliseconds ago.
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
Caused by: java.net.SocketException: Broken pipe
... 61 more
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
at
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
I did this test number of times by allocating fresh box.
Thanks,
Keerthi
was:
After the successful installation along with cloudstack-setup-database.
I tried to start the cloudstack services. During the time I could see the
tomcat fails to start. Pasted the ERROR below.
Kindly can some address this as soon as possible. I am right now in client
place to implement production setup.
Error
ERROR
ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
`cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
FROM (SELECT * FROM `cloud`.`configuration` WHERE
`name`="consoleproxy.url.domain") AS `temptable` WHERE
`temptable`.`name`="consoleproxy.url.domain")) WHERE
`name`="consoleproxy.url.domain"
ERROR [c.c.u.d.ScriptRunner] (main:null)
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
The last packet successfully received from the server was 25 milliseconds ago.
The last packet sent successfully to the server was 25 milliseconds ago.
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
Caused by: java.net.SocketException: Broken pipe
... 61 more
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
at
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
I did this test number of times by allocating fresh box.
Thanks,
Keerthi
> Cloudstack 4.5.2 Not starting on Fresh install
> --
>
> Key: CLOUDSTACK-8836
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8836
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.5.2
> Environment: CentOS 6.7 with MariaDB-server-10.0.21-1.el6.x86_64.
>Reporter: Keerthiraja
>Priority: Blocker
> Fix For: 4.5.3
>
>
> After the successful installation along with cloudstack-setup-database.
> I tried to start the cloudstack services. During the time I could see the
> tomcat fails to start. Pasted the ERROR below.
> Kindly can someone help me out on this as soon as possible. I am right now in
> client place to implement for production setup.
> Error
>
> ERROR
> ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
> `cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
> FROM (SELECT * FROM
[jira] [Created] (CLOUDSTACK-8836) Cloudstack 4.5.2 Not starting on Fresh install
Keerthiraja created CLOUDSTACK-8836:
---
Summary: Cloudstack 4.5.2 Not starting on Fresh install
Key: CLOUDSTACK-8836
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8836
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Install and Setup
Affects Versions: 4.5.2
Environment: CentOS 6.7 with MariaDB-server-10.0.21-1.el6.x86_64.
Reporter: Keerthiraja
Priority: Blocker
Fix For: 4.5.3
After the successful installation along with cloudstack-setup-database.
I tried to start the cloudstack services. During the time I could see the
tomcat fails to start. Pasted the ERROR below.
Kindly can some address this as soon as possible. I am right now in client
place to implement production setup.
Error
ERROR
ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
`cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
FROM (SELECT * FROM `cloud`.`configuration` WHERE
`name`="consoleproxy.url.domain") AS `temptable` WHERE
`temptable`.`name`="consoleproxy.url.domain")) WHERE
`name`="consoleproxy.url.domain"
ERROR [c.c.u.d.ScriptRunner] (main:null)
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
The last packet successfully received from the server was 25 milliseconds ago.
The last packet sent successfully to the server was 25 milliseconds ago.
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
Caused by: java.net.SocketException: Broken pipe
... 61 more
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
at
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
I did this test number of times by allocating fresh box.
Thanks,
Keerthi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8836) Cloudstack 4.5.2 Not starting on Fresh install
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740871#comment-14740871
]
Keerthiraja commented on CLOUDSTACK-8836:
-
This is seems to be issue only when we try to connect via MariaDB.
I tried the same with by uninstall the MariaDB and try with MYSQL
Things went well.
Kindly need to check on this.
> Cloudstack 4.5.2 Not starting on Fresh install
> --
>
> Key: CLOUDSTACK-8836
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8836
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.5.2
> Environment: CentOS 6.7 with MariaDB-server-10.0.21-1.el6.x86_64.
>Reporter: Keerthiraja
>Priority: Blocker
> Fix For: 4.5.3
>
>
> After the successful installation along with cloudstack-setup-database.
> I tried to start the cloudstack services. During the time I could see the
> tomcat fails to start. Pasted the ERROR below.
> Kindly can someone help me out on this as soon as possible. I am right now in
> client place to implement for production setup.
> Error
>
> ERROR
> ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: UPDATE
> `cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value`
> FROM (SELECT * FROM `cloud`.`configuration` WHERE
> `name`="consoleproxy.url.domain") AS `temptable` WHERE
> `temptable`.`name`="consoleproxy.url.domain")) WHERE
> `name`="consoleproxy.url.domain"
> ERROR [c.c.u.d.ScriptRunner] (main:null)
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> The last packet successfully received from the server was 25 milliseconds
> ago. The last packet sent successfully to the server was 25 milliseconds ago.
> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> Caused by: java.net.SocketException: Broken pipe
> ... 61 more
> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the
> database
> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
> ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> I did this test number of times by allocating fresh box.
> Thanks,
> Keerthi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626340#comment-14626340 ] Keerthiraja commented on CLOUDSTACK-3367: - Will this be taken care on current 4.5.2 release When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage. -- Key: CLOUDSTACK-3367 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3367 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.1.0, 4.2.0, 4.5.0, 4.3.1 Environment: CentOS 6.3, XenServer 6.0.2 + all hotfixes, CloudStack 4.1.0 Reporter: France Assignee: Abhinandan Prateek Fix For: Future As the title says: if only one of the primary storages fails, all XenServer hosts get rebooted one by one. Because i have many primary storages, which are/were running fine with other VMs, rebooting XenServer Hipervisor is an overkill. Please disable this or implement just stopping/killing the VMs running on that storage and try to re-attach that storage only. Problem was reported on the mailing list, as well as a workaround for XenServer. So i'm not the only one hit by this bug/feature. Workaround for now is as follows: 1. Modify /opt/xensource/bin/xenheartbeat.sh on all your Hosts, commenting out the two entries which have reboot -f 2. Identify the PID of the script - pidof -x xenheartbeat.sh 3. Restart the Script - kill pid 4. Force reconnect Host from the UI, the script will then re-launch on reconnect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8573) Manage CoreOS
Keerthiraja created CLOUDSTACK-8573: --- Summary: Manage CoreOS Key: CLOUDSTACK-8573 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8573 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Reporter: Keerthiraja Fix For: Future, 4.6.0 Hi All, I would like bring up an idea to manage to support the CoreOS to Manage via Cloudstack. This will be our next major focus on Dockers -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8474) Consider VR SSVM on Debian 8.0 for ACS 4.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja updated CLOUDSTACK-8474: Labels: cloudstack (was: ) Consider VR SSVM on Debian 8.0 for ACS 4.6 -- Key: CLOUDSTACK-8474 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8474 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM, Virtual Router Affects Versions: 4.6.0 Environment: ACS 4.6 Reporter: Keerthiraja Labels: cloudstack Fix For: 4.6.0 Hi All, I would like to bring notice that the newer version of ACS 4.6 needs to be consider upgrading the SystemVM and VirtualRouter to be on Debian 8.0 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8474) Consider VR SSVM on Debian 8.0 for ACS 4.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574484#comment-14574484 ] Keerthiraja commented on CLOUDSTACK-8474: - Consider to install xentools on VR router to check performance during the system template I hope we can install the xenserver 6.2 xenserver tools will work perfectly for xenserver 6.2 and 6.5. This will help us more Without the tools installed, you will not be able to do any the following: Cleanly shut down, reboot or suspend a VM. View VM performance data in XenCenter. Migrate a running VM Create quiesced snapshots or snapshots with memory (checkpoints), or revert to snapshots. Adjust the number of vCPUs on a running Linux VM (Windows VMs require a reboot for this to take effect). All the above are we use cloudstack performance via xen API Kindly consider installing xentool on the systemVM. Thanks, Keerthi Consider VR SSVM on Debian 8.0 for ACS 4.6 -- Key: CLOUDSTACK-8474 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8474 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM, Virtual Router Affects Versions: 4.6.0 Environment: ACS 4.6 Reporter: Keerthiraja Labels: cloudstack Fix For: 4.6.0 Hi All, I would like to bring notice that the newer version of ACS 4.6 needs to be consider upgrading the SystemVM and VirtualRouter to be on Debian 8.0 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8474) Consider VR SSVM on Debian 8.0 for ACS 4.6
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565834#comment-14565834 ] Keerthiraja commented on CLOUDSTACK-8474: - Is there this will be considerable. Consider VR SSVM on Debian 8.0 for ACS 4.6 -- Key: CLOUDSTACK-8474 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8474 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM, Virtual Router Affects Versions: 4.6.0 Environment: ACS 4.6 Reporter: Keerthiraja Fix For: 4.6.0 Hi All, I would like to bring notice that the newer version of ACS 4.6 needs to be consider upgrading the SystemVM and VirtualRouter to be on Debian 8.0 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8473) Deprecate older version of Hypervisor ACS 4.6
Keerthiraja created CLOUDSTACK-8473: --- Summary: Deprecate older version of Hypervisor ACS 4.6 Key: CLOUDSTACK-8473 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8473 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.1 Reporter: Keerthiraja Fix For: Future, 4.6.0 Hi I would like to bring up some idea that we can deprecate the xenserver 5.x 6.0 instead of we can only make the code little simple and can focus on improving the xenserver only latest version 6.2 6.5 and upcoming version of dundee. Where this will really help us to improve to focus on xenserver and cloudstack to improve and make the code and API simple rather than to support of all version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6413) VirtualRouter Custom Disk Offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546035#comment-14546035 ] Keerthiraja commented on CLOUDSTACK-6413: - Is this will be consider on 4.5.2 or upcoming version. VirtualRouter Custom Disk Offering Key: CLOUDSTACK-6413 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6413 Project: CloudStack Issue Type: New Feature Components: Virtual Router Affects Versions: 4.5.0 Environment: Cloudstack Virtual Router Custom Disk Offering Reporter: Keerthiraja I would like to suggest to bring up a new features. Virtual Router custom disk offering or to increase the disk space from default of 2GB to 4GB since when I did small test to collect the Virtual Router static using collectd I tried to install some package but unfortunately /usr partition seem to be full. Why can we increase the default disk space to 4GB or else at least create the partition with lvm so that we can increase the disk partition whenever we need. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8404) cloudstack-management not able to start the App
Keerthiraja created CLOUDSTACK-8404: --- Summary: cloudstack-management not able to start the App Key: CLOUDSTACK-8404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8404 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: 4.5.1 Reporter: Keerthiraja I installed the ACS in my VirtualBox. After I install the CS with 4GB base memory I could not able to start the server. I scale the memory upto 12GB still I could not able to start the ACS. In /var/log/cloudstack/management/catalina.out I could see error as Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Is I missing anything. In the default file of below I could see the java value as default. tomcat6.conf - /etc/cloudstack/management/tomcat6-nonssl.conf JAVA_OPTS=-Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers I even tried by increasing the -Xmx2g into 4g still I don't see any improvement. After the long investigation I found the issue. If i start the app using /etc/init.d/cloudstack-management start I could see error as catalina.out as Can't start up: not enough memory if I do the same using /etc/init.d/tomcat.sh start I able to start the app. But @ the same time when I check the browser I don't see the cloudstack UI. If I cross check the /usr/share/tomcat6/webapps location I don't see any files inside. Tested the App from the repo http://packages.bhaisaab.org/cloudstack/testing/centos/4.5/ cloudstack-awsapi-4.5.1-shapeblue3.el6.x86_64 cloudstack-management-4.5.1-shapeblue3.el6.x86_64 cloudstack-common-4.5.1-shapeblue3.el6.x86_64 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8404) cloudstack-management not able to start the App
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513752#comment-14513752 ] Keerthiraja commented on CLOUDSTACK-8404: - Issue been resolved its because of the Java issue on CentOS 6.6 the OS package pulled the latest java-1.8.0-openjdk-headless-1.8.0.40-25.b25.fc21.x86_64 so I removed the java-1.8 and installed the java-1.7.0-openjdk-1.7.0.79-2.5.5.1.el6_6.x86_64. During the yum install cloudstack-manamgement it pulls the dependencies packages as latest java. cloudstack-management not able to start the App --- Key: CLOUDSTACK-8404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8404 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: 4.5.1 Reporter: Keerthiraja I installed the ACS in my VirtualBox. After I install the CS with 4GB base memory I could not able to start the server. I scale the memory upto 12GB still I could not able to start the ACS. In /var/log/cloudstack/management/catalina.out I could see error as Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Is I missing anything. In the default file of below I could see the java value as default. tomcat6.conf - /etc/cloudstack/management/tomcat6-nonssl.conf JAVA_OPTS=-Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers I even tried by increasing the -Xmx2g into 4g still I don't see any improvement. After the long investigation I found the issue. If i start the app using /etc/init.d/cloudstack-management start I could see error as catalina.out as Can't start up: not enough memory if I do the same using /etc/init.d/tomcat.sh start I able to start the app. But @ the same time when I check the browser I don't see the cloudstack UI. If I cross check the /usr/share/tomcat6/webapps location I don't see any files inside. Tested the App from the repo http://packages.bhaisaab.org/cloudstack/testing/centos/4.5/ cloudstack-awsapi-4.5.1-shapeblue3.el6.x86_64 cloudstack-management-4.5.1-shapeblue3.el6.x86_64 cloudstack-common-4.5.1-shapeblue3.el6.x86_64 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8404) cloudstack-management not able to start the App
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja resolved CLOUDSTACK-8404. - Resolution: Fixed Issue been resolved its because of the Java issue on CentOS 6.6 the OS package pulled the latest java-1.8.0-openjdk-headless-1.8.0.40-25.b25.fc21.x86_64 so I removed the java-1.8 and installed the java-1.7.0-openjdk-1.7.0.79-2.5.5.1.el6_6.x86_64. During the yum install cloudstack-manamgement it pulls the dependencies packages as latest java. cloudstack-management not able to start the App --- Key: CLOUDSTACK-8404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8404 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: 4.5.1 Reporter: Keerthiraja I installed the ACS in my VirtualBox. After I install the CS with 4GB base memory I could not able to start the server. I scale the memory upto 12GB still I could not able to start the ACS. In /var/log/cloudstack/management/catalina.out I could see error as Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Is I missing anything. In the default file of below I could see the java value as default. tomcat6.conf - /etc/cloudstack/management/tomcat6-nonssl.conf JAVA_OPTS=-Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers I even tried by increasing the -Xmx2g into 4g still I don't see any improvement. After the long investigation I found the issue. If i start the app using /etc/init.d/cloudstack-management start I could see error as catalina.out as Can't start up: not enough memory if I do the same using /etc/init.d/tomcat.sh start I able to start the app. But @ the same time when I check the browser I don't see the cloudstack UI. If I cross check the /usr/share/tomcat6/webapps location I don't see any files inside. Tested the App from the repo http://packages.bhaisaab.org/cloudstack/testing/centos/4.5/ cloudstack-awsapi-4.5.1-shapeblue3.el6.x86_64 cloudstack-management-4.5.1-shapeblue3.el6.x86_64 cloudstack-common-4.5.1-shapeblue3.el6.x86_64 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CLOUDSTACK-8404) cloudstack-management not able to start the App
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja updated CLOUDSTACK-8404: Comment: was deleted (was: Issue been resolved its because of the Java issue on CentOS 6.6 the OS package pulled the latest java-1.8.0-openjdk-headless-1.8.0.40-25.b25.fc21.x86_64 so I removed the java-1.8 and installed the java-1.7.0-openjdk-1.7.0.79-2.5.5.1.el6_6.x86_64. During the yum install cloudstack-manamgement it pulls the dependencies packages as latest java. ) cloudstack-management not able to start the App --- Key: CLOUDSTACK-8404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8404 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: 4.5.1 Reporter: Keerthiraja I installed the ACS in my VirtualBox. After I install the CS with 4GB base memory I could not able to start the server. I scale the memory upto 12GB still I could not able to start the ACS. In /var/log/cloudstack/management/catalina.out I could see error as Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Is I missing anything. In the default file of below I could see the java value as default. tomcat6.conf - /etc/cloudstack/management/tomcat6-nonssl.conf JAVA_OPTS=-Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers I even tried by increasing the -Xmx2g into 4g still I don't see any improvement. After the long investigation I found the issue. If i start the app using /etc/init.d/cloudstack-management start I could see error as catalina.out as Can't start up: not enough memory if I do the same using /etc/init.d/tomcat.sh start I able to start the app. But @ the same time when I check the browser I don't see the cloudstack UI. If I cross check the /usr/share/tomcat6/webapps location I don't see any files inside. Tested the App from the repo http://packages.bhaisaab.org/cloudstack/testing/centos/4.5/ cloudstack-awsapi-4.5.1-shapeblue3.el6.x86_64 cloudstack-management-4.5.1-shapeblue3.el6.x86_64 cloudstack-common-4.5.1-shapeblue3.el6.x86_64 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8404) cloudstack-management not able to start the App
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514077#comment-14514077 ] Keerthiraja commented on CLOUDSTACK-8404: - thank you for considering this issue cloudstack-management not able to start the App --- Key: CLOUDSTACK-8404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8404 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: 4.5.1 Reporter: Keerthiraja Assignee: Rohit Yadav I installed the ACS in my VirtualBox. After I install the CS with 4GB base memory I could not able to start the server. I scale the memory upto 12GB still I could not able to start the ACS. In /var/log/cloudstack/management/catalina.out I could see error as Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Can't start up: not enough memory Is I missing anything. In the default file of below I could see the java value as default. tomcat6.conf - /etc/cloudstack/management/tomcat6-nonssl.conf JAVA_OPTS=-Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers I even tried by increasing the -Xmx2g into 4g still I don't see any improvement. After the long investigation I found the issue. If i start the app using /etc/init.d/cloudstack-management start I could see error as catalina.out as Can't start up: not enough memory if I do the same using /etc/init.d/tomcat.sh start I able to start the app. But @ the same time when I check the browser I don't see the cloudstack UI. If I cross check the /usr/share/tomcat6/webapps location I don't see any files inside. Tested the App from the repo http://packages.bhaisaab.org/cloudstack/testing/centos/4.5/ cloudstack-awsapi-4.5.1-shapeblue3.el6.x86_64 cloudstack-management-4.5.1-shapeblue3.el6.x86_64 cloudstack-common-4.5.1-shapeblue3.el6.x86_64 Thanks, Keerthi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8225) Public Network ICON Missing
Keerthiraja created CLOUDSTACK-8225: --- Summary: Public Network ICON Missing Key: CLOUDSTACK-8225 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8225 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Usage Affects Versions: 4.5.0 Environment: VirtualBox 4.3.18 CentOS 6.5 Reporter: Keerthiraja Priority: Blocker Tried testing CS 4.5 on VirtualBox 3.2.18 setup all Network setup done. While creating zone in Advance Network when I proceed the Network Setup I could not able to see the Public Traffic Icon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8225) Public Network ICON Missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja updated CLOUDSTACK-8225: Attachment: Screenshot.png Screenshot during the Zone creation. Public Network ICON Missing Key: CLOUDSTACK-8225 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8225 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Usage Affects Versions: 4.5.0 Environment: VirtualBox 4.3.18 CentOS 6.5 Reporter: Keerthiraja Priority: Blocker Attachments: Screenshot.png Tried testing CS 4.5 on VirtualBox 3.2.18 setup all Network setup done. While creating zone in Advance Network when I proceed the Network Setup I could not able to see the Public Traffic Icon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8222) CentOS Template for 4.5 to be 6.5
Keerthiraja created CLOUDSTACK-8222: --- Summary: CentOS Template for 4.5 to be 6.5 Key: CLOUDSTACK-8222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8222 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.5.0 Environment: Cloudstack 4.5 Reporter: Keerthiraja Fix For: 4.5.0 Default CentOS Template for XenServer 5.6 need to 6.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8221) Testing on CS 4.5 SystemVM Need all Security Vulnerability
Keerthiraja created CLOUDSTACK-8221: --- Summary: Testing on CS 4.5 SystemVM Need all Security Vulnerability Key: CLOUDSTACK-8221 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8221 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.5.0 Environment: Testing on CS 4.5 On CentOS 6.5 MariaDB 10 Reporter: Keerthiraja Fix For: 4.5.0 Need to build SystemVM and RouterVM should fix with all the security variability listed below when we release the 4.5 1. Ghost glibc availability 2. Poodle vulnerability 3. OpenSSL HeartBleed Vulnerability -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6473) Debian 7 Virtual Router ip_conntrack_max not set at boot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299730#comment-14299730 ] Keerthiraja commented on CLOUDSTACK-6473: - Is this been fixed in 4.5 Debian 7 Virtual Router ip_conntrack_max not set at boot Key: CLOUDSTACK-6473 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6473 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.3.0 Environment: XenServer 6.2 CloudStack 4.3.0 Debian 7 SystemVM/Virtual Router Reporter: Logan B Assignee: Sheng Yang Fix For: 4.5.0 The Problem: The Debian 7 Virtual Router VMs for XenServer experiences intermittent connectivity problems. This affects all VMs behind the virtual router in various ways: SSH failures, Apache connections fail, etc. This issue also affects various function within CloudStack that attempt to connect to the Virtual Router (updating firewall rules, NAT, etc.) The Cause: It appears that the issues is being caused by a low default limit for the net.ipv4.netfilter.ip_conntrack_max sysctl. The issue can be easily diagnosed in /var/log/messages: Apr 22 15:45:34 r-5602-VM kernel: [ 1085.117498] nf_conntrack: table full, dropping packet. Apr 22 15:45:34 r-5602-VM kernel: [ 1085.133095] nf_conntrack: table full, dropping packet. Apr 22 15:45:34 r-5602-VM kernel: [ 1085.145440] nf_conntrack: table full, dropping packet. The default setting for ip_conntrack_max is '3796': # sysctl net.ipv4.netfilter.ip_conntrack_max net.ipv4.netfilter.ip_conntrack_max = 3796 As per /etc/sysctl.conf this setting should be '100': net.ipv4.netfilter.ip_conntrack_max=100 It would appear that this setting is not being correctly applied when the virtual router boots. The Solution: - A temporary workaround is to manually set the ip_conntrack_max sysctl to the correct value: # sysctl -w net.ipv4.netfilter.ip_conntrack_max=100 It's likely that this sysctl is being run at boot before the module is loaded, so it doesn't take effect. There are various solutions suggested around the web, any of which should work fine. To resolve this problem a new System VM template should be created. I'm assuming this can be done in between CloudStack releases. I know there is supposed to be a new template released to fix the HeartBleed vulnerability, so this would be a good fix to include with that updated template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6413) VirtualRouter Custom Disk Offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keerthiraja updated CLOUDSTACK-6413: Description: I would like to suggest to bring up a new features. Virtual Router custom disk offering or to increase the disk space from default of 2GB to 4GB since when I did small test to collect the Virtual Router static using collectd I tried to install some package but unfortunately /usr partition seem to be full. Why can we increase the default disk space to 4GB or else at least create the partition with lvm so that we can increase the disk partition whenever we need. was: I would like to suggest to bring up a new features. To bring cloudstack Virtual Router custom disk offering or to increase the disk space from default of 2GB to 4GB since when I did small test to collect the Virtual Router static using collectd I tried to install some package but unfortunately /usr partition seem to be full. Why can we increase the default disk space to 4GB or else at least create the partition with lvm so that we can increase the disk partition whenever we need. Environment: Cloudstack Virtual Router Custom Disk Offering (was: Cloudstack 4.4.0 Virtual Router Custom Disk Offering or Increase disk size or lvm partition ) Affects Version/s: (was: 4.4.0) 4.5.0 Summary: VirtualRouter Custom Disk Offering (was: Cutom Disk Offering VirtualRouter Disk) VirtualRouter Custom Disk Offering Key: CLOUDSTACK-6413 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6413 Project: CloudStack Issue Type: New Feature Components: Virtual Router Affects Versions: 4.5.0 Environment: Cloudstack Virtual Router Custom Disk Offering Reporter: Keerthiraja I would like to suggest to bring up a new features. Virtual Router custom disk offering or to increase the disk space from default of 2GB to 4GB since when I did small test to collect the Virtual Router static using collectd I tried to install some package but unfortunately /usr partition seem to be full. Why can we increase the default disk space to 4GB or else at least create the partition with lvm so that we can increase the disk partition whenever we need. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7254) Cloudstack support of MariaDB
Keerthiraja created CLOUDSTACK-7254: --- Summary: Cloudstack support of MariaDB Key: CLOUDSTACK-7254 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7254 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: Database Reporter: Keerthiraja Hi I would like to suggest while installing cloudstack user should have choice to choose either MySQL or MariaDB. Instead of MYSQL I hope we should consider to move to MariaDB. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6473) Debian 7 Virtual Router ip_conntrack_max not set at boot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997280#comment-13997280 ] Keerthiraja commented on CLOUDSTACK-6473: - is this will be fixed in 4.3.1 Debian 7 Virtual Router ip_conntrack_max not set at boot Key: CLOUDSTACK-6473 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6473 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.3.0 Environment: XenServer 6.2 CloudStack 4.3.0 Debian 7 SystemVM/Virtual Router Reporter: Logan B Fix For: 4.3.1 The Problem: The Debian 7 Virtual Router VMs for XenServer experiences intermittent connectivity problems. This affects all VMs behind the virtual router in various ways: SSH failures, Apache connections fail, etc. This issue also affects various function within CloudStack that attempt to connect to the Virtual Router (updating firewall rules, NAT, etc.) The Cause: It appears that the issues is being caused by a low default limit for the net.ipv4.netfilter.ip_conntrack_max sysctl. The issue can be easily diagnosed in /var/log/messages: Apr 22 15:45:34 r-5602-VM kernel: [ 1085.117498] nf_conntrack: table full, dropping packet. Apr 22 15:45:34 r-5602-VM kernel: [ 1085.133095] nf_conntrack: table full, dropping packet. Apr 22 15:45:34 r-5602-VM kernel: [ 1085.145440] nf_conntrack: table full, dropping packet. The default setting for ip_conntrack_max is '3796': # sysctl net.ipv4.netfilter.ip_conntrack_max net.ipv4.netfilter.ip_conntrack_max = 3796 As per /etc/sysctl.conf this setting should be '100': net.ipv4.netfilter.ip_conntrack_max=100 It would appear that this setting is not being correctly applied when the virtual router boots. The Solution: - A temporary workaround is to manually set the ip_conntrack_max sysctl to the correct value: # sysctl -w net.ipv4.netfilter.ip_conntrack_max=100 It's likely that this sysctl is being run at boot before the module is loaded, so it doesn't take effect. There are various solutions suggested around the web, any of which should work fine. To resolve this problem a new System VM template should be created. I'm assuming this can be done in between CloudStack releases. I know there is supposed to be a new template released to fix the HeartBleed vulnerability, so this would be a good fix to include with that updated template. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6413) Cutom Disk Offering VirtualRouter Disk
Keerthiraja created CLOUDSTACK-6413: --- Summary: Cutom Disk Offering VirtualRouter Disk Key: CLOUDSTACK-6413 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6413 Project: CloudStack Issue Type: New Feature Components: Virtual Router Affects Versions: 4.4.0 Environment: Cloudstack 4.4.0 Virtual Router Custom Disk Offering or Increase disk size or lvm partition Reporter: Keerthiraja I would like to suggest to bring up a new features. To bring cloudstack Virtual Router custom disk offering or to increase the disk space from default of 2GB to 4GB since when I did small test to collect the Virtual Router static using collectd I tried to install some package but unfortunately /usr partition seem to be full. Why can we increase the default disk space to 4GB or else at least create the partition with lvm so that we can increase the disk partition whenever we need. -- This message was sent by Atlassian JIRA (v6.2#6252)
