[jira] [Commented] (CLOUDSTACK-8380) Add script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493623#comment-14493623 ] ASF subversion and git services commented on CLOUDSTACK-8380: - Commit 469270ab0c6ee2df4d1ece0aa2b8d68fd281cd9a in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=469270a ] CLOUDSTACK-8380: Adding script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed > Add script to testSetupSuccess.py to check VCenter port groups are created > for storage, management and public traffic as soon as zone is deployed > - > > Key: CLOUDSTACK-8380 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8380 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: Future > > > Add script to testSetupSuccess.py to check VCenter port groups are created > for storage, management and public traffic as soon as zone is deployed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8380) Add script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493624#comment-14493624 ] ASF GitHub Bot commented on CLOUDSTACK-8380: Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/159 > Add script to testSetupSuccess.py to check VCenter port groups are created > for storage, management and public traffic as soon as zone is deployed > - > > Key: CLOUDSTACK-8380 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8380 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: Future > > > Add script to testSetupSuccess.py to check VCenter port groups are created > for storage, management and public traffic as soon as zone is deployed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8375) Marvin - Code improvement - VCenter port groups verification
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493618#comment-14493618 ] ASF GitHub Bot commented on CLOUDSTACK-8375: Github user gauravaradhye closed the pull request at: https://github.com/apache/cloudstack/pull/155 > Marvin - Code improvement - VCenter port groups verification > > > Key: CLOUDSTACK-8375 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8375 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Fix For: Future > > > Improving the code related to VCenter port groups modification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8375) Marvin - Code improvement - VCenter port groups verification
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493616#comment-14493616 ] ASF GitHub Bot commented on CLOUDSTACK-8375: Github user srikanteswartalluri commented on the pull request: https://github.com/apache/cloudstack/pull/155#issuecomment-92619011 This is merged. forgot to add 'This closes #155' Gaurav, Please close this PR. > Marvin - Code improvement - VCenter port groups verification > > > Key: CLOUDSTACK-8375 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8375 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Fix For: Future > > > Improving the code related to VCenter port groups modification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6543) Advanced search on instances has domain list unsorted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma closed CLOUDSTACK-6543. > Advanced search on instances has domain list unsorted > - > > Key: CLOUDSTACK-6543 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6543 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Remi Bergsma >Priority: Minor > Fix For: 4.6.0 > > > UI: > go to instances > select little arrow to enter advanced search > the domains in this list are unsorted (listed in the order they were added). > Especially when there are a large number of them, this way of working takes a > lot of time to select the right one. > Please sort this list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6543) Advanced search on instances has domain list unsorted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma resolved CLOUDSTACK-6543. -- Resolution: Fixed Fix Version/s: 4.6.0 > Advanced search on instances has domain list unsorted > - > > Key: CLOUDSTACK-6543 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6543 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Remi Bergsma >Priority: Minor > Fix For: 4.6.0 > > > UI: > go to instances > select little arrow to enter advanced search > the domains in this list are unsorted (listed in the order they were added). > Especially when there are a large number of them, this way of working takes a > lot of time to select the right one. > Please sort this list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-4690) KVM Router - to many ethernet devices created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493564#comment-14493564 ] Remi Bergsma commented on CLOUDSTACK-4690: -- Did you guys find a solution/cause for this yet? > KVM Router - to many ethernet devices created > - > > Key: CLOUDSTACK-4690 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4690 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.1.1 > Environment: Centos 6.4 >Reporter: Paul Edwards >Priority: Critical > Attachments: 20141001-agent.log, 20141001-management-server.log, > management-server.log, router.log > > > We have setup cloudstack with advanced networking. We have a network created > 172.16.24.0/23, called news preprod. This has a number of vms created under > it. When we initially set this up, we noticed that the router we created with > 4 ethernet interfaces. This was unexpected, but didn't seem to be effecting > the running of the router, so we didn't worry about it. The interfaces were: > eth0 172.16.24.14, eth1 169.254.1.91, and both eth2 and eth2 were given the > external ip (xxx.xxx.245.59). We investigated why we were getting 2 > externals, but couldn't figure it out. We also configured the router to have > a redundant, with keepalived. They were working fine. > Now I needed to add another external ip to the network. Did that, and > restarted the network. I now have 8 (eight) eth interfaces. The new external > ip is NOT one of them. Heres the ifconfig output: > root@r-235-VM:~# ifconfig > eth0 Link encap:Ethernet HWaddr 02:00:68:e1:00:1a > inet addr:172.16.24.14 Bcast:172.16.25.255 Mask:255.255.254.0 > inet6 addr: fe80::68ff:fee1:1a/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:5485 errors:0 dropped:0 overruns:0 frame:0 > TX packets:21101 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:325618 (317.9 KiB) TX bytes:1581746 (1.5 MiB) > eth1 Link encap:Ethernet HWaddr 0e:00:a9:fe:01:5b > inet addr:169.254.1.91 Bcast:169.254.255.255 Mask:255.255.0.0 > inet6 addr: fe80::c00:a9ff:fefe:15b/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22118 errors:0 dropped:0 overruns:0 frame:0 > TX packets:21148 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:3942785 (3.7 MiB) TX bytes:4287970 (4.0 MiB) > eth2 Link encap:Ethernet HWaddr 06:16:06:00:01:03 > inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0 > inet6 addr: fe80::416:6ff:fe00:103/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:17331 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3930 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1063053 (1.0 MiB) TX bytes:234546 (229.0 KiB) > eth3 Link encap:Ethernet HWaddr 06:d7:ec:00:01:03 > inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0 > inet6 addr: fe80::4d7:ecff:fe00:103/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13603 errors:0 dropped:0 overruns:0 frame:0 > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:792907 (774.3 KiB) TX bytes:704 (704.0 B) > eth4 Link encap:Ethernet HWaddr 06:8b:5a:00:01:03 > inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0 > inet6 addr: fe80::48b:5aff:fe00:103/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13319 errors:0 dropped:0 overruns:0 frame:0 > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:779753 (761.4 KiB) TX bytes:704 (704.0 B) > eth5 Link encap:Ethernet HWaddr 06:7e:68:00:01:03 > inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0 > inet6 addr: fe80::47e:68ff:fe00:103/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13080 errors:0 dropped:0 overruns:0 frame:0 > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:762111 (744.2 KiB) TX bytes:704 (704.0 B) > eth6 Link encap:Ethernet HWaddr 06:7e:68:00:01:03 > inet addr:xxx.xxx.245.59 Bcas
[jira] [Commented] (CLOUDSTACK-6885) system-vm rsyslog logs rotation does not work properly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492915#comment-14492915
]
ASF subversion and git services commented on CLOUDSTACK-6885:
-
Commit 78f4acd9d57b11cf2d19599191de8b48834ac75b in cloudstack's branch
refs/heads/4.5 from Rene Moser
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=78f4acd ]
CLOUDSTACK-6885: fix logrotate on VR to depend on size
In 6ac06e5e5e3ceed4a3e3a86ea5f82ffb59c266f2 logrotate was changed to run hourly.
Some logrotate configs still have set `daily` only which results in logs not
rotated hourly. The only way to ensure the log is rotated is to use size.
This closes #162
(cherry picked from commit 0ada08aa85b305ef931298654f7b41a7db28b03b)
Signed-off-by: Rohit Yadav
> system-vm rsyslog logs rotation does not work properly
> --
>
> Key: CLOUDSTACK-6885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6885
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.3.0
>Reporter: JF Vincent
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.6.0, 4.5.1
>
>
> rsyslog reload synthax is bad in the logrotate.d/rsyslog setting resulting in
> potential FULL on /var/ and critical failures on the VR.
> See below please :
> root@r-1346-SANDBOX:/var/log# more /etc/logrotate.d/rsyslog
> /var/log/syslog
> {
> rotate 7
> daily
> missingok
> notifempty
> delaycompress
> compress
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> /var/log/mail.info
> /var/log/mail.warn
> /var/log/mail.err
> /var/log/mail.log
> /var/log/daemon.log
> /var/log/kern.log
> /var/log/auth.log
> /var/log/user.log
> /var/log/lpr.log
> /var/log/cron.log
> /var/log/debug
> /var/log/messages
> {
> rotate 10
> daily
> missingok
> notifempty
> compress
> delaycompress
> sharedscripts
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog reload
> Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog rotate
> [ ok ] Closing open files: rsyslogd.
> "reload" argument in the invoke-rc.d line shoud be replaced by "rotate"
> argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6885) system-vm rsyslog logs rotation does not work properly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492910#comment-14492910
]
ASF subversion and git services commented on CLOUDSTACK-6885:
-
Commit 0ada08aa85b305ef931298654f7b41a7db28b03b in cloudstack's branch
refs/heads/master from Rene Moser
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0ada08a ]
CLOUDSTACK-6885: fix logrotate on VR to depend on size
In 6ac06e5e5e3ceed4a3e3a86ea5f82ffb59c266f2 logrotate was changed to run hourly.
Some logrotate configs still have set `daily` only which results in logs not
rotated hourly. The only way to ensure the log is rotated is to use size.
This closes #162
Signed-off-by: Rohit Yadav
> system-vm rsyslog logs rotation does not work properly
> --
>
> Key: CLOUDSTACK-6885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6885
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.3.0
>Reporter: JF Vincent
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.6.0, 4.5.1
>
>
> rsyslog reload synthax is bad in the logrotate.d/rsyslog setting resulting in
> potential FULL on /var/ and critical failures on the VR.
> See below please :
> root@r-1346-SANDBOX:/var/log# more /etc/logrotate.d/rsyslog
> /var/log/syslog
> {
> rotate 7
> daily
> missingok
> notifempty
> delaycompress
> compress
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> /var/log/mail.info
> /var/log/mail.warn
> /var/log/mail.err
> /var/log/mail.log
> /var/log/daemon.log
> /var/log/kern.log
> /var/log/auth.log
> /var/log/user.log
> /var/log/lpr.log
> /var/log/cron.log
> /var/log/debug
> /var/log/messages
> {
> rotate 10
> daily
> missingok
> notifempty
> compress
> delaycompress
> sharedscripts
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog reload
> Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog rotate
> [ ok ] Closing open files: rsyslogd.
> "reload" argument in the invoke-rc.d line shoud be replaced by "rotate"
> argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6885) system-vm rsyslog logs rotation does not work properly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492911#comment-14492911
]
ASF GitHub Bot commented on CLOUDSTACK-6885:
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/162
> system-vm rsyslog logs rotation does not work properly
> --
>
> Key: CLOUDSTACK-6885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6885
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.3.0
>Reporter: JF Vincent
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.6.0, 4.5.1
>
>
> rsyslog reload synthax is bad in the logrotate.d/rsyslog setting resulting in
> potential FULL on /var/ and critical failures on the VR.
> See below please :
> root@r-1346-SANDBOX:/var/log# more /etc/logrotate.d/rsyslog
> /var/log/syslog
> {
> rotate 7
> daily
> missingok
> notifempty
> delaycompress
> compress
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> /var/log/mail.info
> /var/log/mail.warn
> /var/log/mail.err
> /var/log/mail.log
> /var/log/daemon.log
> /var/log/kern.log
> /var/log/auth.log
> /var/log/user.log
> /var/log/lpr.log
> /var/log/cron.log
> /var/log/debug
> /var/log/messages
> {
> rotate 10
> daily
> missingok
> notifempty
> compress
> delaycompress
> sharedscripts
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog reload
> Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog rotate
> [ ok ] Closing open files: rsyslogd.
> "reload" argument in the invoke-rc.d line shoud be replaced by "rotate"
> argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6885) system-vm rsyslog logs rotation does not work properly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492901#comment-14492901
]
ASF GitHub Bot commented on CLOUDSTACK-6885:
Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/162#issuecomment-92467703
great patch @resmo merging now!
> system-vm rsyslog logs rotation does not work properly
> --
>
> Key: CLOUDSTACK-6885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6885
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.3.0
>Reporter: JF Vincent
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.6.0, 4.5.1
>
>
> rsyslog reload synthax is bad in the logrotate.d/rsyslog setting resulting in
> potential FULL on /var/ and critical failures on the VR.
> See below please :
> root@r-1346-SANDBOX:/var/log# more /etc/logrotate.d/rsyslog
> /var/log/syslog
> {
> rotate 7
> daily
> missingok
> notifempty
> delaycompress
> compress
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> /var/log/mail.info
> /var/log/mail.warn
> /var/log/mail.err
> /var/log/mail.log
> /var/log/daemon.log
> /var/log/kern.log
> /var/log/auth.log
> /var/log/user.log
> /var/log/lpr.log
> /var/log/cron.log
> /var/log/debug
> /var/log/messages
> {
> rotate 10
> daily
> missingok
> notifempty
> compress
> delaycompress
> sharedscripts
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog reload
> Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog rotate
> [ ok ] Closing open files: rsyslogd.
> "reload" argument in the invoke-rc.d line shoud be replaced by "rotate"
> argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8335) publish maven artifacts to central repo
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492861#comment-14492861
]
ASF GitHub Bot commented on CLOUDSTACK-8335:
Github user K0zka commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/163#discussion_r28268011
--- Diff: plugins/hypervisors/kvm/pom.xml ---
@@ -45,7 +38,7 @@
${project.version}
- org.libvirt
+ com.github.K0zka
--- End diff --
Hi Rohit,
I updated the group ID to that because I can publish with that group ID
only and not with org.libvirt, unfortunately the libvirt maintainers do not
seem to be interested in pushing their artifacts to central repo.
I agree that the groupId does not look good, but I haven't found another
way. I will try to keep an up to date version in central repo untl libvirt
maintainers accept the changes I have done on the pom.xml and publish to maven
central, but this may take quite some time.
> publish maven artifacts to central repo
> ---
>
> Key: CLOUDSTACK-8335
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8335
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Laszlo Hornyak
>Assignee: Laszlo Hornyak
> Labels: build, release
>
> Publish the cloudstack artifacts to the central maven repository.
> Blocking issues:
> * third party repositories:
>* ceph
>* libvirt
> [Mailing list
> thread|http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201503.mbox/browser]
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8335) publish maven artifacts to central repo
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492813#comment-14492813
]
ASF GitHub Bot commented on CLOUDSTACK-8335:
Github user bhaisaab commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/163#discussion_r28265861
--- Diff: plugins/hypervisors/kvm/pom.xml ---
@@ -45,7 +38,7 @@
${project.version}
- org.libvirt
+ com.github.K0zka
--- End diff --
is this fine? com.github.K0zka?
@K0zka will you be maintaining this repo?
> publish maven artifacts to central repo
> ---
>
> Key: CLOUDSTACK-8335
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8335
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Laszlo Hornyak
>Assignee: Laszlo Hornyak
> Labels: build, release
>
> Publish the cloudstack artifacts to the central maven repository.
> Blocking issues:
> * third party repositories:
>* ceph
>* libvirt
> [Mailing list
> thread|http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201503.mbox/browser]
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8335) publish maven artifacts to central repo
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492765#comment-14492765 ] ASF GitHub Bot commented on CLOUDSTACK-8335: GitHub user K0zka opened a pull request: https://github.com/apache/cloudstack/pull/163 CLOUDSTACK-8335: use libvirt from central repository Signed-off-by: Laszlo Hornyak You can merge this pull request into a Git repository by running: $ git pull https://github.com/K0zka/cloudstack CLOUDSTACK-8335 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/163.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 #163 commit e1cc7897f57e13c9a73b90dd61e2f3551a519a2f Author: Laszlo Hornyak Date: 2015-04-13T16:59:26Z CLOUDSTACK-8335: use libvirt from central repository Signed-off-by: Laszlo Hornyak > publish maven artifacts to central repo > --- > > Key: CLOUDSTACK-8335 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8335 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Laszlo Hornyak >Assignee: Laszlo Hornyak > Labels: build, release > > Publish the cloudstack artifacts to the central maven repository. > Blocking issues: > * third party repositories: >* ceph >* libvirt > [Mailing list > thread|http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201503.mbox/browser] > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6885) system-vm rsyslog logs rotation does not work properly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492718#comment-14492718
]
ASF GitHub Bot commented on CLOUDSTACK-6885:
GitHub user resmo opened a pull request:
https://github.com/apache/cloudstack/pull/162
CLOUDSTACK-6885: fix logrotate on VR to depend on size
In 6ac06e5e5e3ceed4a3e3a86ea5f82ffb59c266f2 logrotate was changed to run
hourly. Some logrotate configs still have set `daily` only which results in
logs not rotated hourly. The only way to ensure the log is rotated is to use
size.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/resmo/cloudstack
fix/conntrackd-logrotate-daily
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/162.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 #162
commit 3dbbc737d6977caf592e1a2261eec2943c4afb32
Author: Rene Moser
Date: 2015-04-13T15:59:13Z
CLOUDSTACK-6885: fix logrotate on VR to depend on size
In 6ac06e5e5e3ceed4a3e3a86ea5f82ffb59c266f2 logrotate was changed to run
hourly. Some logrotate configs still have set `daily` only which results in
logs not rotated hourly. The only way to ensure the log is rotated is to use
size.
> system-vm rsyslog logs rotation does not work properly
> --
>
> Key: CLOUDSTACK-6885
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6885
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.3.0
>Reporter: JF Vincent
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.6.0, 4.5.1
>
>
> rsyslog reload synthax is bad in the logrotate.d/rsyslog setting resulting in
> potential FULL on /var/ and critical failures on the VR.
> See below please :
> root@r-1346-SANDBOX:/var/log# more /etc/logrotate.d/rsyslog
> /var/log/syslog
> {
> rotate 7
> daily
> missingok
> notifempty
> delaycompress
> compress
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> /var/log/mail.info
> /var/log/mail.warn
> /var/log/mail.err
> /var/log/mail.log
> /var/log/daemon.log
> /var/log/kern.log
> /var/log/auth.log
> /var/log/user.log
> /var/log/lpr.log
> /var/log/cron.log
> /var/log/debug
> /var/log/messages
> {
> rotate 10
> daily
> missingok
> notifempty
> compress
> delaycompress
> sharedscripts
> postrotate
> invoke-rc.d rsyslog reload > /dev/null
> endscript
> }
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog reload
> Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
> root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog rotate
> [ ok ] Closing open files: rsyslogd.
> "reload" argument in the invoke-rc.d line shoud be replaced by "rotate"
> argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8385) Donate gstack to CloudStack project
sebastien goasguen created CLOUDSTACK-8385: -- Summary: Donate gstack to CloudStack project Key: CLOUDSTACK-8385 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8385 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen Work through IP clearance to donate gstack to CloudStack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8384) Donate ec2stack to CloudStack project
sebastien goasguen created CLOUDSTACK-8384: -- Summary: Donate ec2stack to CloudStack project Key: CLOUDSTACK-8384 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8384 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen Work trough IP clearance to donate ec2stack to CloudStack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6197) GsoC: Improve GCE and EC2 python bridges to CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6197. Resolution: Fixed fixed through donation of ec2stack and gstack > GsoC: Improve GCE and EC2 python bridges to CloudStack > -- > > Key: CLOUDSTACK-6197 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6197 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: sebastien goasguen > Labels: gsoc2014 > > CloudStack has its own native API which is different than the de-facto > standard that is EC2. Google also announced general availability for GCE. > There is a need to provide an API bridge from EC2/GCE to CloudStack api. > Currently two projects do this: > https://github.com/NOPping/gstack > https://github.com/imduffy15/ec2stack > They are both python and based on Flask microframework. > The project would be to extend these two code base, add APIs not currently > covered and fix existing bugs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6543) Advanced search on instances has domain list unsorted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492329#comment-14492329 ] ASF subversion and git services commented on CLOUDSTACK-6543: - Commit a7f8059fd35dae42a04583b4333b28ec0d68218a in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a7f8059 ] CLOUDSTACK-6543 Sort domain lists in UI As recently discussed on the dev list: This sorts the domain lists based on their path. Especially handy when having a lot of domains, like in a public cloud. > Advanced search on instances has domain list unsorted > - > > Key: CLOUDSTACK-6543 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6543 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Remi Bergsma >Priority: Minor > > UI: > go to instances > select little arrow to enter advanced search > the domains in this list are unsorted (listed in the order they were added). > Especially when there are a large number of them, this way of working takes a > lot of time to select the right one. > Please sort this list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6543) Advanced search on instances has domain list unsorted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492331#comment-14492331 ] ASF GitHub Bot commented on CLOUDSTACK-6543: Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/157 > Advanced search on instances has domain list unsorted > - > > Key: CLOUDSTACK-6543 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6543 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Remi Bergsma >Priority: Minor > > UI: > go to instances > select little arrow to enter advanced search > the domains in this list are unsorted (listed in the order they were added). > Especially when there are a large number of them, this way of working takes a > lot of time to select the right one. > Please sort this list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8380) Add script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492314#comment-14492314 ] ASF GitHub Bot commented on CLOUDSTACK-8380: GitHub user gauravaradhye opened a pull request: https://github.com/apache/cloudstack/pull/159 CLOUDSTACK-8380: Adding script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed This test will be run on vmware zone once the zone is up, if the zone uses vmware DVS. Data Center Details must filled up in config dict. Tested on Vmware and KVM. On KVM it skips. VMware: Test correct VCenter ports are created for all traffic types ... === TestName: test_VCenterPorts | Status : SUCCESS === ok system VMs need to be ready and Running for each zone in cloudstack ... SKIP: skip built-in templates CentOS to be ready ... SKIP: skip -- Ran 3 tests in 25.920s OK (SKIP=2) on KVM: Test correct VCenter ports are created for all traffic types ... SKIP: This test is intended only for vmware system VMs need to be ready and Running for each zone in cloudstack ... SKIP: skip built-in templates CentOS to be ready ... SKIP: skip -- Ran 3 tests in 0.021s OK (SKIP=3) Other Changes: 1. Increases retry count while checking system VM state 2. Fixed import* issues Travis might fail in case the pull request at https://github.com/apache/cloudstack/pull/155 is not closed. Please merge above mentioned pull request first and then try to merge this one. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gauravaradhye/cloudstack 8380 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/159.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 #159 commit 469270ab0c6ee2df4d1ece0aa2b8d68fd281cd9a Author: Gaurav Aradhye Date: 2015-04-13T11:20:38Z CLOUDSTACK-8380: Adding script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed > Add script to testSetupSuccess.py to check VCenter port groups are created > for storage, management and public traffic as soon as zone is deployed > - > > Key: CLOUDSTACK-8380 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8380 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: Future > > > Add script to testSetupSuccess.py to check VCenter port groups are created > for storage, management and public traffic as soon as zone is deployed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8375) Marvin - Code improvement - VCenter port groups verification
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492290#comment-14492290 ] ASF subversion and git services commented on CLOUDSTACK-8375: - Commit 8a5b1e60a4fc75ad57b9b127d1c6f13c202415c4 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8a5b1e6 ] CLOUDSTACK-8375: VCenter port group verification - return as PASS if no physical networks in zone Signed-off-by: SrikanteswaraRao Talluri > Marvin - Code improvement - VCenter port groups verification > > > Key: CLOUDSTACK-8375 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8375 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Fix For: Future > > > Improving the code related to VCenter port groups modification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8375) Marvin - Code improvement - VCenter port groups verification
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492289#comment-14492289 ] ASF subversion and git services commented on CLOUDSTACK-8375: - Commit 4d05c3b966bf709bab820a6f84483d780e204197 in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4d05c3b ] CLOUDSTACK-8375: Marvin - Code Improvement - related to verifying VCenter port groups corresponding to traffic types in a zone Signed-off-by: SrikanteswaraRao Talluri > Marvin - Code improvement - VCenter port groups verification > > > Key: CLOUDSTACK-8375 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8375 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: Future >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Fix For: Future > > > Improving the code related to VCenter port groups modification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8383) [Master Install] Unable to start VM due to error in finalizeStart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raja Pullela updated CLOUDSTACK-8383: - Description: Following Exception is seen in the Management server log - Error finalize start 2015-04-13 08:12:11,018 ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-3:ctx-a3d21009 job-19/job-23 ctx-31b66d8c) Failed to start instance VM[DomainRouter|r-7-VM] com.cloud.utils.exception.ExecutionException: Unable to start VM[DomainRouter|r-7-VM] due to error in finalizeStart, not retrying at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1076) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4503) 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:601) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4659) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:103) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) was: Following DB Exception is seen in the Management server log - DB exception – 2015-04-13 07:49:25,128 ERROR [c.c.u.d.Upgrade410to420] (main:null) migrateDatafromIsoIdInVolumesTable:Exception:Unknown column 'iso_id1' in 'field list' com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'iso_id1' in 'field list' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.upgrade.dao.Upgrade410to420.migrateDatafromIsoIdInVolumesTable(Upgrade410to420.java:2555) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:111) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:338) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:461) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtend
[jira] [Created] (CLOUDSTACK-8383) [Master Install] Unable to start VM due to error in finalizeStart
Raja Pullela created CLOUDSTACK-8383: Summary: [Master Install] Unable to start VM due to error in finalizeStart Key: CLOUDSTACK-8383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8383 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.6.0 Reporter: Raja Pullela Priority: Critical Fix For: 4.6.0 Following DB Exception is seen in the Management server log - DB exception – 2015-04-13 07:49:25,128 ERROR [c.c.u.d.Upgrade410to420] (main:null) migrateDatafromIsoIdInVolumesTable:Exception:Unknown column 'iso_id1' in 'field list' com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'iso_id1' in 'field list' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.upgrade.dao.Upgrade410to420.migrateDatafromIsoIdInVolumesTable(Upgrade410to420.java:2555) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:111) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:338) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:461) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:947) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79) at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70) at org.apache.cloudstack.spring.module.factory.CloudStackSpring
[jira] [Updated] (CLOUDSTACK-8382) [Master Install] DB exception unknown column is seen in Management server log
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raja Pullela updated CLOUDSTACK-8382: - Description: Following DB Exception is seen in the Management server log - DB exception – 2015-04-13 07:49:25,128 ERROR [c.c.u.d.Upgrade410to420] (main:null) migrateDatafromIsoIdInVolumesTable:Exception:Unknown column 'iso_id1' in 'field list' com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'iso_id1' in 'field list' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.upgrade.dao.Upgrade410to420.migrateDatafromIsoIdInVolumesTable(Upgrade410to420.java:2555) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:111) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:338) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:461) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:947) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79) at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:57) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:61) at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52) at org.apache.catalina.core.StandardContext.listene
[jira] [Created] (CLOUDSTACK-8382) [Master Install] DB exception unknown column is seen in Management server log
Raja Pullela created CLOUDSTACK-8382: Summary: [Master Install] DB exception unknown column is seen in Management server log Key: CLOUDSTACK-8382 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8382 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.6.0 Reporter: Raja Pullela Priority: Critical Fix For: 4.6.0 Following error is seen in the Management server log - SQL Exceptions 2015-04-13 07:49:24,872 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert exception: Can't DROP 'last_sent'; check that column/key exists 2015-04-13 07:49:24,872 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key i_alert__last_sent on table alert exception: Can't DROP 'i_alert__last_sent'; check that column/key exists 2015-04-13 07:49:24,881 DEBUG [c.c.u.d.Upgrade410to420] (main:null) Added index i_alert__last_sent for table alert 2015-04-13 07:49:24,888 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_nsp_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,896 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_host_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,902 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_pod_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,908 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_physical_network_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,915 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_nsp_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,921 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_host_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,927 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_pod_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,932 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_physical_network_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,943 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_nsp_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,949 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_host_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,955 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_physical_network_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) >>> 2015-04-13 07:50:08,590 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught (SQL?)Exception: no network_group Table 'cloud.network_group' doesn't exist 2015-04-13 07:55:40,419 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught exception when inserting system account: Duplicate entry '1' for key 'PRIMARY' 2015-04-13 07:55:40,420 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user: Duplicate entry '1' for ke
[jira] [Created] (CLOUDSTACK-8381) [Master Install] SQL exception are seen in Management server log
Raja Pullela created CLOUDSTACK-8381: Summary: [Master Install] SQL exception are seen in Management server log Key: CLOUDSTACK-8381 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8381 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.6.0 Reporter: Raja Pullela Priority: Critical Fix For: 4.6.0 Following error is seen in the Management server log - SQL Exceptions 2015-04-13 07:49:24,872 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert exception: Can't DROP 'last_sent'; check that column/key exists 2015-04-13 07:49:24,872 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key i_alert__last_sent on table alert exception: Can't DROP 'i_alert__last_sent'; check that column/key exists 2015-04-13 07:49:24,881 DEBUG [c.c.u.d.Upgrade410to420] (main:null) Added index i_alert__last_sent for table alert 2015-04-13 07:49:24,888 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_nsp_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,896 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_host_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,902 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_pod_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,908 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_physical_network_id on table baremetal_dhcp_devices exception: Error on rename of './cloud/baremetal_dhcp_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,915 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_nsp_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,921 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_host_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,927 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_pod_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,932 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_dhcp_devices_physical_network_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,943 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_nsp_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,949 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_host_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) 2015-04-13 07:49:24,955 DEBUG [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop foreign key fk_external_pxe_devices_physical_network_id on table baremetal_pxe_devices exception: Error on rename of './cloud/baremetal_pxe_devices' to './cloud/#sql2-a94-15' (errno: 152) >>> 2015-04-13 07:50:08,590 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught (SQL?)Exception: no network_group Table 'cloud.network_group' doesn't exist 2015-04-13 07:55:40,419 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught exception when inserting system account: Duplicate entry '1' for key 'PRIMARY' 2015-04-13 07:55:40,420 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user: Duplicate entry '1' for key 'PRIMARY'
[jira] [Created] (CLOUDSTACK-8380) Add script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed
Gaurav Aradhye created CLOUDSTACK-8380: -- Summary: Add script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed Key: CLOUDSTACK-8380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8380 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: Future Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: Future Add script to testSetupSuccess.py to check VCenter port groups are created for storage, management and public traffic as soon as zone is deployed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8379) add support to marvin to enable deployed zone based on the value provided in config file
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492253#comment-14492253
]
ASF GitHub Bot commented on CLOUDSTACK-8379:
GitHub user srikanteswartalluri opened a pull request:
https://github.com/apache/cloudstack/pull/158
CLOUDSTACK-8379:add support to marvin to enable deployed zone based on t...
...he value provided in config file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srikanteswartalluri/cloudstack enablezone
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/158.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 #158
commit 9dbd28e5fe855a809700ec6246b204e7eb0f7c02
Author: SrikanteswaraRao Talluri
Date: 2015-04-13T10:34:19Z
CLOUDSTACK-8379:add support to marvin to enable deployed zone based on the
value provided in config file
> add support to marvin to enable deployed zone based on the value provided in
> config file
>
>
> Key: CLOUDSTACK-8379
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8379
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: marvin
>Affects Versions: 4.6.0
>Reporter: Srikanteswararao Talluri
>Assignee: Srikanteswararao Talluri
> Fix For: 4.6.0
>
>
> add support to marvin to enable deployed zone based on the value provided in
> config file
> if under zone section, if the 'enabled' element is not mentioned, then zone
> will be enabled otherwise zone will be enabled/disabled based on value
> provided ('false' or 'true') for 'enabled'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7593) For VMWare nics do not nic/card type as specified but default to E1000
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492237#comment-14492237 ] ASF subversion and git services commented on CLOUDSTACK-7593: - Commit a70947f9b1a1e57ed79d082fae29061574df2a20 in cloudstack's branch refs/heads/master from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a70947f ] CLOUDSTACK-7593: in 450to451 upgrade path copy vm_details from template for vmware Signed-off-by: Rohit Yadav (cherry picked from commit 8e1507078052b8068b828d336f8d0358915047e1) Signed-off-by: Rohit Yadav > For VMWare nics do not nic/card type as specified but default to E1000 > -- > > Key: CLOUDSTACK-7593 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7593 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: 4.5.1 > > > VMWare VMs should pick up nic/card types as selected by the user, they > default to E1000 now. > Ref: > https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java#L883 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7593) For VMWare nics do not nic/card type as specified but default to E1000
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav closed CLOUDSTACK-7593. --- Resolution: Fixed > For VMWare nics do not nic/card type as specified but default to E1000 > -- > > Key: CLOUDSTACK-7593 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7593 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: 4.5.1 > > > VMWare VMs should pick up nic/card types as selected by the user, they > default to E1000 now. > Ref: > https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java#L883 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7593) For VMWare nics do not nic/card type as specified but default to E1000
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492230#comment-14492230 ] ASF subversion and git services commented on CLOUDSTACK-7593: - Commit 8e1507078052b8068b828d336f8d0358915047e1 in cloudstack's branch refs/heads/4.5 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8e15070 ] CLOUDSTACK-7593: in 450to451 upgrade path copy vm_details from template for vmware Signed-off-by: Rohit Yadav > For VMWare nics do not nic/card type as specified but default to E1000 > -- > > Key: CLOUDSTACK-7593 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7593 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: 4.5.1 > > > VMWare VMs should pick up nic/card types as selected by the user, they > default to E1000 now. > Ref: > https://github.com/apache/cloudstack/blob/master/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java#L883 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8379) add support to marvin to enable deployed zone based on the value provided in config file
Srikanteswararao Talluri created CLOUDSTACK-8379:
Summary: add support to marvin to enable deployed zone based on
the value provided in config file
Key: CLOUDSTACK-8379
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8379
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: marvin
Affects Versions: 4.6.0
Reporter: Srikanteswararao Talluri
Assignee: Srikanteswararao Talluri
Fix For: 4.6.0
add support to marvin to enable deployed zone based on the value provided in
config file
if under zone section, if the 'enabled' element is not mentioned, then zone
will be enabled otherwise zone will be enabled/disabled based on value provided
('false' or 'true') for 'enabled'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8378) add test setup health check script to the smoke test
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-8378. Resolution: Fixed closing this bug as the script is already available under tools/marvin/marvin > add test setup health check script to the smoke test > > > Key: CLOUDSTACK-8378 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8378 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Affects Versions: 4.6.0 >Reporter: Srikanteswararao Talluri >Assignee: Srikanteswararao Talluri > > add test setup health check script to the smoke test > - which checks for the state of system VMs > - which checks for the state of default builtin template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8378) add test setup health check script to the smoke test
Srikanteswararao Talluri created CLOUDSTACK-8378: Summary: add test setup health check script to the smoke test Key: CLOUDSTACK-8378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8378 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.6.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri add test setup health check script to the smoke test - which checks for the state of system VMs - which checks for the state of default builtin template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
