[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361930#comment-16361930 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - ustcweizhou commented on a change in pull request #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167781635 ## File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql ## @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id BIGINT(20) DEFAULT 0; ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id; DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map; CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map (domain_id, account_id); + +CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` ( + `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id', + `uuid` varchar(255) UNIQUE, + `name` varchar(255) UNIQUE COMMENT 'name of the service package', + `description` varchar(255) COMMENT 'description of the service package', + PRIMARY KEY (`id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8; + +CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` ( + `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id', + `uuid` varchar(255) UNIQUE, + `username` varchar(255) COMMENT 'username of the NCC', + `password` varchar(255) COMMENT 'password of NCC', + `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager', + `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries in ncc for command failure', + PRIMARY KEY (`id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8; + +ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default NULL COMMENT 'Name of the Certificate'; Review comment: @rhtyd thanks for your explanation. LGTM now. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10284) Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361883#comment-16361883 ] ASF GitHub Bot commented on CLOUDSTACK-10284: - niteshsarda commented on issue #2451: CLOUDSTACK-10284:Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM. URL: https://github.com/apache/cloudstack/pull/2451#issuecomment-365164038 @ustcweizhou : I have address your second issue in latest code, but could not understand first point. Can you please provide more clarification around first issue ? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM. > -- > > Key: CLOUDSTACK-10284 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10284 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitesh Sarda >Priority: Major > > ISSUE > Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM. > STEPS TO REPRODUCE > * Create a cloudstack setup with hypervisor other than KVM. > * Create an instance. > * Take Snapshot of that VM. > * Try to take volume snapshot from newly created VM snapshot. > * It will throw an error as hypervisor is not KVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361539#comment-16361539 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-365082774 Trillian test result (tid-2254) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 23691 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2452-t2254-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py Smoke tests completed. 65 look OK, 2 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_privategw_static_routes | `Failure` | 277.99 | test_privategw_acl.py test_hostha_enable_ha_when_host_in_maintenance | `Error` | 3.43 | test_hostha_kvm.py This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CLOUDSTACK-10166) Cannot add a tag to a NetworkACL (rule not list) in CS with a user in a project or in an account
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Khosrow Moossavi resolved CLOUDSTACK-10166.
---
Resolution: Fixed
> Cannot add a tag to a NetworkACL (rule not list) in CS with a user in a
> project or in an account
>
>
> Key: CLOUDSTACK-10166
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10166
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.10.0.0
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.11.0.0
>
>
> From cloudmonkey with non-root credentials
> {code:none}
> > create tags resourcetype=NetworkACL resourceids=SOME_ACL_RULE_ID
> > tags[0].key=tag-key tags[0].value=tag-value
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10263) A new ui framework that easier to extend for new APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361425#comment-16361425 ] Khosrow Moossavi commented on CLOUDSTACK-10263: --- I would suggest to have a new/redesign backend API framework/engine as well, even may be considering version ACS 5.x instead of 4.12.x. > A new ui framework that easier to extend for new APIs > - > > Key: CLOUDSTACK-10263 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10263 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Daan Hoogland >Priority: Major > Labels: gsoc2018 > > As a developer I want to have an easy entry to my new APIs from the UI on the > web. This now involves digging through tons of js code to find the right > place to add widgets for my call. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361384#comment-16361384 ] ASF GitHub Bot commented on CLOUDSTACK-10250: - nvazquez opened a new pull request #2423: CLOUDSTACK-10250: Reinstall VM from bypassed registered template URL: https://github.com/apache/cloudstack/pull/2423 JIRA Ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 This fix allows users to restore a VM from a previously registered template using the Direct Download option (only for KVM currently) NOTE: As Reinstall VM button prompts only featured templates, to be able to restore a vm to a Direct Download template, it should be registered as Featured This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Reinstall VM from bypassed registered template > -- > > Key: CLOUDSTACK-10250 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > This fix allows users to restore a VM from a previously registered template > using the Direct Download option (only for KVM currently) > NOTE: As Reinstall VM button prompts only featured templates, to be able to > restore a vm to a Direct Download template, it should be registered as > Featured -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361373#comment-16361373
]
ASF GitHub Bot commented on CLOUDSTACK-10250:
-
DaanHoogland closed pull request #2423: CLOUDSTACK-10250: Reinstall VM from
bypassed registered template
URL: https://github.com/apache/cloudstack/pull/2423
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/server/src/com/cloud/vm/UserVmManagerImpl.java
b/server/src/com/cloud/vm/UserVmManagerImpl.java
index dab741c3c27..a5bfc47584d 100644
--- a/server/src/com/cloud/vm/UserVmManagerImpl.java
+++ b/server/src/com/cloud/vm/UserVmManagerImpl.java
@@ -313,6 +313,7 @@
import com.cloud.vm.snapshot.VMSnapshotVO;
import com.cloud.vm.snapshot.dao.VMSnapshotDao;
import com.cloud.storage.snapshot.SnapshotApiService;
+import com.cloud.storage.VMTemplateStorageResourceAssoc;
public class UserVmManagerImpl extends ManagerBase implements UserVmManager,
VirtualMachineGuru, UserVmService, Configurable {
private static final Logger s_logger =
Logger.getLogger(UserVmManagerImpl.class);
@@ -6100,10 +6101,8 @@ public UserVm restoreVMInternal(Account caller, UserVmVO
vm, Long newTemplateId)
throw ex;
}
}
-TemplateDataStoreVO tmplStore =
_templateStoreDao.findByTemplateZoneReady(template.getId(),
vm.getDataCenterId());
-if (tmplStore == null) {
-throw new InvalidParameterValueException("Cannot restore the
vm as the template " + template.getUuid() + " isn't available in the zone");
-}
+
+checkRestoreVmFromTemplate(vm, template);
if (needRestart) {
try {
@@ -6217,6 +6216,27 @@ public UserVm restoreVMInternal(Account caller, UserVmVO
vm, Long newTemplateId)
}
+/**
+ * Perform basic checkings to make sure restore is possible. If not,
#InvalidParameterValueException is thrown
+ * @param vm vm
+ * @param template template
+ * @throws InvalidParameterValueException if restore is not possible
+ */
+private void checkRestoreVmFromTemplate(UserVmVO vm, VMTemplateVO
template) {
+TemplateDataStoreVO tmplStore;
+if (!template.isDirectDownload()) {
+tmplStore =
_templateStoreDao.findByTemplateZoneReady(template.getId(),
vm.getDataCenterId());
+if (tmplStore == null) {
+throw new InvalidParameterValueException("Cannot restore the
vm as the template " + template.getUuid() + " isn't available in the zone");
+}
+} else {
+tmplStore = _templateStoreDao.findByTemplate(template.getId(),
DataStoreRole.Image);
+if (tmplStore == null || (tmplStore != null &&
!tmplStore.getDownloadState().equals(VMTemplateStorageResourceAssoc.Status.BYPASSED)))
{
+throw new InvalidParameterValueException("Cannot restore the
vm as the bypassed template " + template.getUuid() + " isn't available in the
zone");
+}
+}
+}
+
private void handleManagedStorage(UserVmVO vm, VolumeVO root) {
if (Volume.State.Allocated.equals(root.getState())) {
return;
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Reinstall VM from bypassed registered template
> --
>
> Key: CLOUDSTACK-10250
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> This fix allows users to restore a VM from a previously registered template
> using the Direct Download option (only for KVM currently)
> NOTE: As Reinstall VM button prompts only featured templates, to be able to
> restore a vm to a Direct Download template, it should be registered as
> Featured
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10147) Disabled Xenserver cluster can still deploy VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361370#comment-16361370 ] ASF GitHub Bot commented on CLOUDSTACK-10147: - DaanHoogland commented on issue #2442: CLOUDSTACK-10147 Disabled Xenserver Cluster can still deploy VM's URL: https://github.com/apache/cloudstack/pull/2442#issuecomment-365043745 @houthuis did you ask the submitter (of CLOUDSTACK-10147) about the validity of the functionality? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Disabled Xenserver cluster can still deploy VMs > > > Key: CLOUDSTACK-10147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.10.0.0, 4.9.2.0 > Environment: Xenserver 6.2, 7 >Reporter: Glenn Wagner >Assignee: Henko Holtzhausen >Priority: Major > > ENVIRONMENT > = > XenServer Version : 6.2 , 7 > ISSUE > == > Disabled Xenserver Cluster can still deploy VM's , hosts in the cluster are > still active > Repro. steps followed > == > Disabled Cluster from UI. > Deploy a new VM > Expected Behavior > === > After disabling the cluster , the hosts should be disabled. and no VM's can > be deployed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361367#comment-16361367
]
ASF GitHub Bot commented on CLOUDSTACK-10250:
-
DaanHoogland closed pull request #2423: CLOUDSTACK-10250: Reinstall VM from
bypassed registered template
URL: https://github.com/apache/cloudstack/pull/2423
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/server/src/com/cloud/vm/UserVmManagerImpl.java
b/server/src/com/cloud/vm/UserVmManagerImpl.java
index dab741c3c27..a5bfc47584d 100644
--- a/server/src/com/cloud/vm/UserVmManagerImpl.java
+++ b/server/src/com/cloud/vm/UserVmManagerImpl.java
@@ -313,6 +313,7 @@
import com.cloud.vm.snapshot.VMSnapshotVO;
import com.cloud.vm.snapshot.dao.VMSnapshotDao;
import com.cloud.storage.snapshot.SnapshotApiService;
+import com.cloud.storage.VMTemplateStorageResourceAssoc;
public class UserVmManagerImpl extends ManagerBase implements UserVmManager,
VirtualMachineGuru, UserVmService, Configurable {
private static final Logger s_logger =
Logger.getLogger(UserVmManagerImpl.class);
@@ -6100,10 +6101,8 @@ public UserVm restoreVMInternal(Account caller, UserVmVO
vm, Long newTemplateId)
throw ex;
}
}
-TemplateDataStoreVO tmplStore =
_templateStoreDao.findByTemplateZoneReady(template.getId(),
vm.getDataCenterId());
-if (tmplStore == null) {
-throw new InvalidParameterValueException("Cannot restore the
vm as the template " + template.getUuid() + " isn't available in the zone");
-}
+
+checkRestoreVmFromTemplate(vm, template);
if (needRestart) {
try {
@@ -6217,6 +6216,27 @@ public UserVm restoreVMInternal(Account caller, UserVmVO
vm, Long newTemplateId)
}
+/**
+ * Perform basic checkings to make sure restore is possible. If not,
#InvalidParameterValueException is thrown
+ * @param vm vm
+ * @param template template
+ * @throws InvalidParameterValueException if restore is not possible
+ */
+private void checkRestoreVmFromTemplate(UserVmVO vm, VMTemplateVO
template) {
+TemplateDataStoreVO tmplStore;
+if (!template.isDirectDownload()) {
+tmplStore =
_templateStoreDao.findByTemplateZoneReady(template.getId(),
vm.getDataCenterId());
+if (tmplStore == null) {
+throw new InvalidParameterValueException("Cannot restore the
vm as the template " + template.getUuid() + " isn't available in the zone");
+}
+} else {
+tmplStore = _templateStoreDao.findByTemplate(template.getId(),
DataStoreRole.Image);
+if (tmplStore == null || (tmplStore != null &&
!tmplStore.getDownloadState().equals(VMTemplateStorageResourceAssoc.Status.BYPASSED)))
{
+throw new InvalidParameterValueException("Cannot restore the
vm as the bypassed template " + template.getUuid() + " isn't available in the
zone");
+}
+}
+}
+
private void handleManagedStorage(UserVmVO vm, VolumeVO root) {
if (Volume.State.Allocated.equals(root.getState())) {
return;
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Reinstall VM from bypassed registered template
> --
>
> Key: CLOUDSTACK-10250
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> This fix allows users to restore a VM from a previously registered template
> using the Direct Download option (only for KVM currently)
> NOTE: As Reinstall VM button prompts only featured templates, to be able to
> restore a vm to a Direct Download template, it should be registered as
> Featured
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361368#comment-16361368 ] ASF GitHub Bot commented on CLOUDSTACK-10250: - nvazquez opened a new pull request #2423: CLOUDSTACK-10250: Reinstall VM from bypassed registered template URL: https://github.com/apache/cloudstack/pull/2423 JIRA Ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 This fix allows users to restore a VM from a previously registered template using the Direct Download option (only for KVM currently) NOTE: As Reinstall VM button prompts only featured templates, to be able to restore a vm to a Direct Download template, it should be registered as Featured This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Reinstall VM from bypassed registered template > -- > > Key: CLOUDSTACK-10250 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > This fix allows users to restore a VM from a previously registered template > using the Direct Download option (only for KVM currently) > NOTE: As Reinstall VM button prompts only featured templates, to be able to > restore a vm to a Direct Download template, it should be registered as > Featured -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10271) detect vulnerabilities in depndencies
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361362#comment-16361362 ] ASF GitHub Bot commented on CLOUDSTACK-10271: - DaanHoogland commented on issue #2446: CLOUDSTACK-10271 maven plugin for owasp dependency check added URL: https://github.com/apache/cloudstack/pull/2446#issuecomment-365042857 @marcaurele are you -1 on this chance as is? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > detect vulnerabilities in depndencies > - > > Key: CLOUDSTACK-10271 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10271 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Daan Hoogland >Assignee: Daan Hoogland >Priority: Major > > As a developer I want to know whether and what dependencies I am using that > might harm my users. For this we need to add the owasp dependency checker to > the maven build. It will require more then just this but it is a good first > step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10147) Disabled Xenserver cluster can still deploy VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361310#comment-16361310 ] ASF GitHub Bot commented on CLOUDSTACK-10147: - blueorangutan commented on issue #2442: CLOUDSTACK-10147 Disabled Xenserver Cluster can still deploy VM's URL: https://github.com/apache/cloudstack/pull/2442#issuecomment-365032026 Trillian test result (tid-2252) Environment: xenserver-65sp1 (x2), Advanced Networking with Mgmt server 7 Total time taken: 36354 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2442-t2252-xenserver-65sp1.zip Intermitten failure detected: /marvin/tests/smoke/test_vm_snapshots.py Smoke tests completed. 67 look OK, 0 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Disabled Xenserver cluster can still deploy VMs > > > Key: CLOUDSTACK-10147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.10.0.0, 4.9.2.0 > Environment: Xenserver 6.2, 7 >Reporter: Glenn Wagner >Assignee: Henko Holtzhausen >Priority: Major > > ENVIRONMENT > = > XenServer Version : 6.2 , 7 > ISSUE > == > Disabled Xenserver Cluster can still deploy VM's , hosts in the cluster are > still active > Repro. steps followed > == > Disabled Cluster from UI. > Deploy a new VM > Expected Behavior > === > After disabling the cluster , the hosts should be disabled. and no VM's can > be deployed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361131#comment-16361131 ] ASF GitHub Bot commented on CLOUDSTACK-10250: - blueorangutan commented on issue #2423: CLOUDSTACK-10250: Reinstall VM from bypassed registered template URL: https://github.com/apache/cloudstack/pull/2423#issuecomment-364999878 Trillian test result (tid-2253) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 30836 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2423-t2253-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py Smoke tests completed. 65 look OK, 2 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_02_cancel_host_maintenace_with_migration_jobs | `Error` | 3.55 | test_host_maintenance.py test_hostha_enable_ha_when_host_in_maintenance | `Error` | 1.85 | test_hostha_kvm.py This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Reinstall VM from bypassed registered template > -- > > Key: CLOUDSTACK-10250 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > This fix allows users to restore a VM from a previously registered template > using the Direct Download option (only for KVM currently) > NOTE: As Reinstall VM button prompts only featured templates, to be able to > restore a vm to a Direct Download template, it should be registered as > Featured -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10271) detect vulnerabilities in depndencies
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361113#comment-16361113 ] ASF GitHub Bot commented on CLOUDSTACK-10271: - blueorangutan commented on issue #2446: CLOUDSTACK-10271 maven plugin for owasp dependency check added URL: https://github.com/apache/cloudstack/pull/2446#issuecomment-364996703 Trillian test result (tid-2251) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 30372 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2446-t2251-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py Smoke tests completed. 66 look OK, 1 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_hostha_enable_ha_when_host_in_maintenance | `Error` | 0.83 | test_hostha_kvm.py This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > detect vulnerabilities in depndencies > - > > Key: CLOUDSTACK-10271 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10271 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Daan Hoogland >Assignee: Daan Hoogland >Priority: Major > > As a developer I want to know whether and what dependencies I am using that > might harm my users. For this we need to add the owasp dependency checker to > the maven build. It will require more then just this but it is a good first > step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360947#comment-16360947 ] ASF GitHub Bot commented on CLOUDSTACK-10025: - rhtyd commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC Console for KVM and XENSERVER URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-364967523 @syed great, happy to collaborate you've my support. Perhaps we can also get some help from @ustcweizhou and others who may have worked on novnc integration. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > To create a better VNC client for Cloudstack using noVNC > > > Key: CLOUDSTACK-10025 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10025 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Affects Versions: 4.11.0.0 >Reporter: Sachin >Priority: Minor > Labels: features > > I have implemented this feature as my GSoC'17 project. noVNC is written in > javascript and uses websockets to connect to VNC server. We have modified the > ConsoleProxy server to accept websocket request from noVNC client, which then > forwards the request request to VNC server. > Javascript cannot make plain tcp request, hence the websocket request have to > be forwarded to the VNC server via a proxy server that basically converts > websocket request from client to plain tcp request for VNC server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360892#comment-16360892 ] ASF GitHub Bot commented on CLOUDSTACK-10025: - syed commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC Console for KVM and XENSERVER URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-364958976 @rhtyd Sorry for dropping the ball on this. We will be looking at working on this in the coming months. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > To create a better VNC client for Cloudstack using noVNC > > > Key: CLOUDSTACK-10025 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10025 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Affects Versions: 4.11.0.0 >Reporter: Sachin >Priority: Minor > Labels: features > > I have implemented this feature as my GSoC'17 project. noVNC is written in > javascript and uses websockets to connect to VNC server. We have modified the > ConsoleProxy server to accept websocket request from noVNC client, which then > forwards the request request to VNC server. > Javascript cannot make plain tcp request, hence the websocket request have to > be forwarded to the VNC server via a proxy server that basically converts > websocket request from client to plain tcp request for VNC server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360867#comment-16360867 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364954377 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360865#comment-16360865 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364954204 @blueorangutan test This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360777#comment-16360777 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364930948 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1710 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360754#comment-16360754 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364907238 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1709 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360756#comment-16360756 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364923692 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360753#comment-16360753 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364901557 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360752#comment-16360752 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364923525 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360748#comment-16360748 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - rhtyd commented on a change in pull request #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167555229 ## File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql ## @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id BIGINT(20) DEFAULT 0; ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id; DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map; CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map (domain_id, account_id); + +CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` ( + `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id', + `uuid` varchar(255) UNIQUE, + `name` varchar(255) UNIQUE COMMENT 'name of the service package', + `description` varchar(255) COMMENT 'description of the service package', + PRIMARY KEY (`id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8; + +CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` ( + `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id', + `uuid` varchar(255) UNIQUE, + `username` varchar(255) COMMENT 'username of the NCC', + `password` varchar(255) COMMENT 'password of NCC', + `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager', + `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries in ncc for command failure', + PRIMARY KEY (`id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8; + +ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default NULL COMMENT 'Name of the Certificate'; Review comment: The assumption is it won't exist in before 4.11.0.0 release. Users of 4.9.3.0 or earlier will get this change when they upgrade to 4.11.0.0 but 4.10.0.0 users won't. See the dev/user ML for the discussion/proposal. But I see what you mean, the query is not idempotent which perhaps @ernjvr and @borisstoyanov may help improve. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CLOUDSTACK-9663) updateRole should return updated role as json
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dingane Hlaluku closed CLOUDSTACK-9663.
---
> updateRole should return updated role as json
> -
>
> Key: CLOUDSTACK-9663
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9663
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.9.0
>Reporter: René Moser
>Priority: Trivial
> Fix For: Future, 4.11.0.0
>
>
> updateRole does currently only return success but one would expect it returns
> the updated role as json like other update APIs
> Acutal results:
> {code}
> $ cs updateRole id=0d6f4eca-cf71-47ba-81d9-aa129b38911b name=test
> --region=simulator
> {
> "success": "true"
> }
> {code}
> expected resutls:
> {code}
> $ cs updateRole id=0d6f4eca-cf71-47ba-81d9-aa129b38911b name=test
> --region=simulator
> {
> "role": {
> "id": ...
> "description": ...
> "name": ...
> "type": ...
> }
> }
> {code}
> similar to other update api e.g.
> http://cloudstack.apache.org/api/apidocs-4.9/apis/updateUser.html.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360673#comment-16360673 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - ustcweizhou commented on a change in pull request #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167540175 ## File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql ## @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id BIGINT(20) DEFAULT 0; ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id; DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map; CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map (domain_id, account_id); + +CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` ( + `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id', + `uuid` varchar(255) UNIQUE, + `name` varchar(255) UNIQUE COMMENT 'name of the service package', + `description` varchar(255) COMMENT 'description of the service package', + PRIMARY KEY (`id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8; + +CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` ( + `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id', + `uuid` varchar(255) UNIQUE, + `username` varchar(255) COMMENT 'username of the NCC', + `password` varchar(255) COMMENT 'password of NCC', + `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager', + `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries in ncc for command failure', + PRIMARY KEY (`id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8; + +ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default NULL COMMENT 'Name of the Certificate'; Review comment: Is it possible that `name` field already exists in `sslcerts` table ? If yes, upgrade will fail here. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360668#comment-16360668 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364907238 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1709 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360644#comment-16360644 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364901557 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360643#comment-16360643 ] ASF GitHub Bot commented on CLOUDSTACK-10285: - rhtyd opened a new pull request #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users URL: https://github.com/apache/cloudstack/pull/2452 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due to some PRs that got merged without moving their sql changes to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those missing sql statements manually and then upgrade to 4.11.0.0, since a workaround like this is possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade path. Ideally we should not be doing this, but this will fix issues for a future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. The failure hit is missing column `service_package_id`. Issue was caused primarily due to `884606f77be7621944d2f315fd8eabe8884c45d9`. Pinging for review - @PaulAngus @borisstoyanov @DaanHoogland @wido @karuturi @sateesh-chodapuneedi and others. @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-10285: - Status: Reviewable (was: In Progress) > 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 > - > > Key: CLOUDSTACK-10285 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Critical > Fix For: 4.12.0.0, 4.11.1.0 > > > 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due > to some PRs that got merged without moving their sql changes to 4.10->4.11 > upgrade path. The 4.10.0.0 users can run those missing sql statements > manually and then upgrade to 4.11.0.0, since a workaround like this is > possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those > changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade > path. Ideally we should not be doing this, but this will fix issues for a > future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
Rohit Yadav created CLOUDSTACK-10285: Summary: 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 Key: CLOUDSTACK-10285 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285 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.12.0.0, 4.11.1.0 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due to some PRs that got merged without moving their sql changes to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those missing sql statements manually and then upgrade to 4.11.0.0, since a workaround like this is possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade path. Ideally we should not be doing this, but this will fix issues for a future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10261) Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one interface.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360596#comment-16360596 ] ASF subversion and git services commented on CLOUDSTACK-10261: -- Commit dee5bb527e7aca4e72e2249b348cca6d688fbe5f in cloudstack's branch refs/heads/4.11 from [~fmaximus] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=dee5bb5 ] CLOUDSTACK-10261: Libvirt metadata create only one nuage-extension xml tag (#2441) > Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one > interface. > --- > > Key: CLOUDSTACK-10261 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10261 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: cloudstack-agent >Affects Versions: 4.11.0.0 > Environment: Nuage VSP plugin on RHEL 7.4 >Reporter: Frank Maximus >Assignee: Frank Maximus >Priority: Critical > Fix For: 4.11.0.0 > > > When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there > is an issue with the metadata of the created VM in cloudstack. > It leads to password reset failure as the nuage vrs is not allowing passage > to DomainRouter. > After debugging , it was found that the nuage-extension in metadata was > missing. > When cloudstack-agent is preparing xml to be sent to openvswitch it contains > metadata with nuage-extension block as follows > > > > > > In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without > nuage-extension block in metadata as follows: > Jan 15 18:17:17 ovs-1 vm-monitor.log: > So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in > its metada, so the libvirt namespace needs to be adapted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10261) Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one interface.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360594#comment-16360594 ] ASF GitHub Bot commented on CLOUDSTACK-10261: - rhtyd commented on issue #2441: CLOUDSTACK-10261: Libvirt metadata: only create one nuage-extension tag URL: https://github.com/apache/cloudstack/pull/2441#issuecomment-364891629 LGTM, merging based on review and test results (ignoring intermittent failures). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one > interface. > --- > > Key: CLOUDSTACK-10261 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10261 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: cloudstack-agent >Affects Versions: 4.11.0.0 > Environment: Nuage VSP plugin on RHEL 7.4 >Reporter: Frank Maximus >Assignee: Frank Maximus >Priority: Critical > Fix For: 4.11.0.0 > > > When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there > is an issue with the metadata of the created VM in cloudstack. > It leads to password reset failure as the nuage vrs is not allowing passage > to DomainRouter. > After debugging , it was found that the nuage-extension in metadata was > missing. > When cloudstack-agent is preparing xml to be sent to openvswitch it contains > metadata with nuage-extension block as follows > > > > > > In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without > nuage-extension block in metadata as follows: > Jan 15 18:17:17 ovs-1 vm-monitor.log: > So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in > its metada, so the libvirt namespace needs to be adapted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10261) Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one interface.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360595#comment-16360595
]
ASF GitHub Bot commented on CLOUDSTACK-10261:
-
rhtyd closed pull request #2441: CLOUDSTACK-10261: Libvirt metadata: only
create one nuage-extension tag
URL: https://github.com/apache/cloudstack/pull/2441
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
index 385fe79ef2a..90674eb99a8 100644
---
a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
+++
b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
@@ -1543,16 +1543,15 @@ public void addNuageExtension(String macAddress, String
vrIp) {
@Override
public String toString() {
StringBuilder fsBuilder = new StringBuilder();
+fsBuilder.append("\n");
for (Map.Entry address : addresses.entrySet()) {
-fsBuilder.append("\n")
-.append(" \n")
-.append("\n");
+fsBuilder.append(" \n");
}
-return fsBuilder.toString();
+return fsBuilder.append("\n").toString();
}
}
diff --git
a/plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtVMDefTest.java
b/plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtVMDefTest.java
index 006562c213e..b391b94e740 100644
---
a/plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtVMDefTest.java
+++
b/plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtVMDefTest.java
@@ -209,4 +209,21 @@ public void testSCSIDef() {
assertEquals(str, expected);
}
+public void testMetadataDef() {
+LibvirtVMDef.MetadataDef metadataDef = new LibvirtVMDef.MetadataDef();
+
+
metadataDef.getMetadataNode(LibvirtVMDef.NuageExtensionDef.class).addNuageExtension("mac1",
"ip1");
+
metadataDef.getMetadataNode(LibvirtVMDef.NuageExtensionDef.class).addNuageExtension("mac2",
"ip2");
+
+String xmlDef = metadataDef.toString();
+String expectedXml = "\n" +
+"\n" +
+" \n" +
+" \n" +
+"\n" +
+"\n";
+
+assertEquals(xmlDef, expectedXml);
+}
+
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Nuage: Multinic: Libvirt nuage-extenstion metadata contains only one
> interface.
> ---
>
> Key: CLOUDSTACK-10261
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10261
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Frank Maximus
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there
> is an issue with the metadata of the created VM in cloudstack.
> It leads to password reset failure as the nuage vrs is not allowing passage
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains
> metadata with nuage-extension block as follows
>
>
>
>
>
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log:
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in
> its metada, so the libvirt namespace needs to be adapted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10282) SystemVM - filrewall rules incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360581#comment-16360581 ] ASF GitHub Bot commented on CLOUDSTACK-10282: - blueorangutan commented on issue #2450: CLOUDSTACK-10282: firewall rules operation should be done with ip6tab… URL: https://github.com/apache/cloudstack/pull/2450#issuecomment-364887772 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1708 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > SystemVM - filrewall rules incorrect > > > Key: CLOUDSTACK-10282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10282 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Reporter: Marc-Aurèle Brothier >Priority: Major > > The current state of the firewall on the systemVMs let all packets come in > due to the overwrite of the ipv6 rules on the ipv4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10282) SystemVM - filrewall rules incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360556#comment-16360556 ] ASF GitHub Bot commented on CLOUDSTACK-10282: - blueorangutan commented on issue #2450: CLOUDSTACK-10282: firewall rules operation should be done with ip6tab… URL: https://github.com/apache/cloudstack/pull/2450#issuecomment-364881789 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > SystemVM - filrewall rules incorrect > > > Key: CLOUDSTACK-10282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10282 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Reporter: Marc-Aurèle Brothier >Priority: Major > > The current state of the firewall on the systemVMs let all packets come in > due to the overwrite of the ipv6 rules on the ipv4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10282) SystemVM - filrewall rules incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360555#comment-16360555 ] ASF GitHub Bot commented on CLOUDSTACK-10282: - rhtyd commented on issue #2450: CLOUDSTACK-10282: firewall rules operation should be done with ip6tab… URL: https://github.com/apache/cloudstack/pull/2450#issuecomment-364881765 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > SystemVM - filrewall rules incorrect > > > Key: CLOUDSTACK-10282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10282 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Reporter: Marc-Aurèle Brothier >Priority: Major > > The current state of the firewall on the systemVMs let all packets come in > due to the overwrite of the ipv6 rules on the ipv4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10278) Adding a SQL table column is not Idempotent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360545#comment-16360545 ] ASF GitHub Bot commented on CLOUDSTACK-10278: - DaanHoogland commented on issue #2449: WIP CLOUDSTACK-10278 idempotent column addition URL: https://github.com/apache/cloudstack/pull/2449#issuecomment-364879178 @ustcweizhou I agree that something like that would be preferable but someone has to take the heat on implementing that. And nobody is taking the time for such a technical/non-functional improvement. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Adding a SQL table column is not Idempotent > --- > > Key: CLOUDSTACK-10278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10278 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.10.0.0, 4.11.0.0 >Reporter: Ernie Janse van Rensburg >Assignee: Ernie Janse van Rensburg >Priority: Major > Original Estimate: 4h > Remaining Estimate: 4h > > The SQL code to add a new column to a table in the > META-INF/db/schema-41000to41100.sql script is not written in an idempotent > way. When the upgrade is re-run, the code above causes a SQL error as > reported on the user mailing list: > ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc > INT(1) NOT NULL DEFAULT 0 > This is a more generic problem for every version due to to the fact that it > is not idempotent > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10274) L2 network refused to be designed on VXLAN physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360516#comment-16360516 ] ASF GitHub Bot commented on CLOUDSTACK-10274: - borisstoyanov commented on issue #2448: CLOUDSTACK-10274: L2 network refused to be designed on VXLAN physical network URL: https://github.com/apache/cloudstack/pull/2448#issuecomment-364874573 @NuxRo we'll be addressing this as well This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > L2 network refused to be designed on VXLAN physical network > > > Key: CLOUDSTACK-10274 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10274 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Priority: Major > Fix For: 4.11.1.1 > > > Issue reported by [~nuxro] while trying to add an L2 network on a VXLAN > physical network: > 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical > network id=201 based on requested tags mellanoxvxlan > 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical > network id=201 based on requested tags mellanoxvxlan > 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network, the physical isolation type is not BCF_SEGMENT > 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not > configured to be active > 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design network using network offering 19 on physical network 201 > 2018-02-06 11:20:27,770 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Releasing lock > for Acct[6af2875b-04fc-11e8-923e-002590474525-admin] > 2018-02-06 11:20:27,789 DEBUG [c.c.u.d.T.Transaction] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Rolling back > the transaction: Time = 38 Name = qtp788117692-390; called by > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-NetworkOrchestrator.createGuestNetwork:2315-NetworkServiceImpl$4.doInTransaction:1383-NetworkServiceImpl$4.doInTransaction:1331-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1331-NetworkServiceImpl.createGuestNetwork:1294-NativeMethodAccessorImpl.invoke0:-2 > 2018-02-06 11:20:27,798 ERROR [c.c.a.ApiServer] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) unhandled > exception executing api command: [Ljava.lang.String;@43b9df02 > com.cloud.utils.exception.CloudRuntimeException: Unable to convert network > offering with specified id to network profile > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:726) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2364) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2315) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50) > at com.cloud.utils.db.Transaction.execute(Transaction.java:40) > at com.cloud.utils.db.Transaction.execute(Transaction.java:47) --
[jira] [Commented] (CLOUDSTACK-10274) L2 network refused to be designed on VXLAN physical network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360508#comment-16360508 ] ASF GitHub Bot commented on CLOUDSTACK-10274: - NuxRo commented on issue #2448: CLOUDSTACK-10274: L2 network refused to be designed on VXLAN physical network URL: https://github.com/apache/cloudstack/pull/2448#issuecomment-364873501 A bit confused as to whether my previous complaint was noticed, so here goes again: - this is only HALF working, the VXLAN based L2 Network will fail to create if VXLAN id is over 4096, it seems to be applying VLAN limit numbers. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > L2 network refused to be designed on VXLAN physical network > > > Key: CLOUDSTACK-10274 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10274 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Priority: Major > Fix For: 4.11.1.1 > > > Issue reported by [~nuxro] while trying to add an L2 network on a VXLAN > physical network: > 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical > network id=201 based on requested tags mellanoxvxlan > 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical > network id=201 based on requested tags mellanoxvxlan > 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network, the physical isolation type is not BCF_SEGMENT > 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not > configured to be active > 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design this network > 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to > design network using network offering 19 on physical network 201 > 2018-02-06 11:20:27,770 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Releasing lock > for Acct[6af2875b-04fc-11e8-923e-002590474525-admin] > 2018-02-06 11:20:27,789 DEBUG [c.c.u.d.T.Transaction] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Rolling back > the transaction: Time = 38 Name = qtp788117692-390; called by > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-NetworkOrchestrator.createGuestNetwork:2315-NetworkServiceImpl$4.doInTransaction:1383-NetworkServiceImpl$4.doInTransaction:1331-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1331-NetworkServiceImpl.createGuestNetwork:1294-NativeMethodAccessorImpl.invoke0:-2 > 2018-02-06 11:20:27,798 ERROR [c.c.a.ApiServer] > (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) unhandled > exception executing api command: [Ljava.lang.String;@43b9df02 > com.cloud.utils.exception.CloudRuntimeException: Unable to convert network > offering with specified id to network profile > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:726) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2364) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2315) > at >
[jira] [Commented] (CLOUDSTACK-10282) SystemVM - filrewall rules incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360449#comment-16360449 ] ASF GitHub Bot commented on CLOUDSTACK-10282: - marcaurele commented on issue #2450: CLOUDSTACK-10282: firewall rules operation should be done with ip6tab… URL: https://github.com/apache/cloudstack/pull/2450#issuecomment-364857790 Rebased done @rhtyd This bug leaves the systemvm with all ports opened This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > SystemVM - filrewall rules incorrect > > > Key: CLOUDSTACK-10282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10282 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Reporter: Marc-Aurèle Brothier >Priority: Major > > The current state of the firewall on the systemVMs let all packets come in > due to the overwrite of the ipv6 rules on the ipv4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10282) SystemVM - filrewall rules incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360447#comment-16360447 ] ASF GitHub Bot commented on CLOUDSTACK-10282: - marcaurele commented on issue #2450: CLOUDSTACK-10282: firewall rules operation should be done with ip6tab… URL: https://github.com/apache/cloudstack/pull/2450#issuecomment-364857790 Rebased done @rhtyd This bug leaves the systemvm with all port opened This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > SystemVM - filrewall rules incorrect > > > Key: CLOUDSTACK-10282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10282 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Reporter: Marc-Aurèle Brothier >Priority: Major > > The current state of the firewall on the systemVMs let all packets come in > due to the overwrite of the ipv6 rules on the ipv4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10282) SystemVM - filrewall rules incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360441#comment-16360441 ] ASF GitHub Bot commented on CLOUDSTACK-10282: - marcaurele commented on issue #2450: CLOUDSTACK-10282: firewall rules operation should be done with ip6tab… URL: https://github.com/apache/cloudstack/pull/2450#issuecomment-364857790 Rebased done @rhtyd This bug leaves the systemvm with all port opens This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > SystemVM - filrewall rules incorrect > > > Key: CLOUDSTACK-10282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10282 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Reporter: Marc-Aurèle Brothier >Priority: Major > > The current state of the firewall on the systemVMs let all packets come in > due to the overwrite of the ipv6 rules on the ipv4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10147) Disabled Xenserver cluster can still deploy VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360429#comment-16360429 ] ASF GitHub Bot commented on CLOUDSTACK-10147: - blueorangutan commented on issue #2442: CLOUDSTACK-10147 Disabled Xenserver Cluster can still deploy VM's URL: https://github.com/apache/cloudstack/pull/2442#issuecomment-364855206 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + xenserver-65sp1) has been kicked to run smoke tests This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Disabled Xenserver cluster can still deploy VMs > > > Key: CLOUDSTACK-10147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.10.0.0, 4.9.2.0 > Environment: Xenserver 6.2, 7 >Reporter: Glenn Wagner >Assignee: Henko Holtzhausen >Priority: Major > > ENVIRONMENT > = > XenServer Version : 6.2 , 7 > ISSUE > == > Disabled Xenserver Cluster can still deploy VM's , hosts in the cluster are > still active > Repro. steps followed > == > Disabled Cluster from UI. > Deploy a new VM > Expected Behavior > === > After disabling the cluster , the hosts should be disabled. and no VM's can > be deployed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10147) Disabled Xenserver cluster can still deploy VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360428#comment-16360428 ] ASF GitHub Bot commented on CLOUDSTACK-10147: - borisstoyanov commented on issue #2442: CLOUDSTACK-10147 Disabled Xenserver Cluster can still deploy VM's URL: https://github.com/apache/cloudstack/pull/2442#issuecomment-364855183 @blueorangutan test centos7 xenserver-65sp1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Disabled Xenserver cluster can still deploy VMs > > > Key: CLOUDSTACK-10147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.10.0.0, 4.9.2.0 > Environment: Xenserver 6.2, 7 >Reporter: Glenn Wagner >Assignee: Henko Holtzhausen >Priority: Major > > ENVIRONMENT > = > XenServer Version : 6.2 , 7 > ISSUE > == > Disabled Xenserver Cluster can still deploy VM's , hosts in the cluster are > still active > Repro. steps followed > == > Disabled Cluster from UI. > Deploy a new VM > Expected Behavior > === > After disabling the cluster , the hosts should be disabled. and no VM's can > be deployed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360430#comment-16360430 ] ASF GitHub Bot commented on CLOUDSTACK-10250: - blueorangutan commented on issue #2423: CLOUDSTACK-10250: Reinstall VM from bypassed registered template URL: https://github.com/apache/cloudstack/pull/2423#issuecomment-364855209 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Reinstall VM from bypassed registered template > -- > > Key: CLOUDSTACK-10250 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > This fix allows users to restore a VM from a previously registered template > using the Direct Download option (only for KVM currently) > NOTE: As Reinstall VM button prompts only featured templates, to be able to > restore a vm to a Direct Download template, it should be registered as > Featured -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360427#comment-16360427 ] ASF GitHub Bot commented on CLOUDSTACK-10250: - borisstoyanov commented on issue #2423: CLOUDSTACK-10250: Reinstall VM from bypassed registered template URL: https://github.com/apache/cloudstack/pull/2423#issuecomment-364855042 @blueorangutan test This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Reinstall VM from bypassed registered template > -- > > Key: CLOUDSTACK-10250 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > This fix allows users to restore a VM from a previously registered template > using the Direct Download option (only for KVM currently) > NOTE: As Reinstall VM button prompts only featured templates, to be able to > restore a vm to a Direct Download template, it should be registered as > Featured -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10271) detect vulnerabilities in depndencies
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360426#comment-16360426 ] ASF GitHub Bot commented on CLOUDSTACK-10271: - blueorangutan commented on issue #2446: CLOUDSTACK-10271 maven plugin for owasp dependency check added URL: https://github.com/apache/cloudstack/pull/2446#issuecomment-364854977 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > detect vulnerabilities in depndencies > - > > Key: CLOUDSTACK-10271 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10271 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Daan Hoogland >Assignee: Daan Hoogland >Priority: Major > > As a developer I want to know whether and what dependencies I am using that > might harm my users. For this we need to add the owasp dependency checker to > the maven build. It will require more then just this but it is a good first > step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10271) detect vulnerabilities in depndencies
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360425#comment-16360425 ] ASF GitHub Bot commented on CLOUDSTACK-10271: - borisstoyanov commented on issue #2446: CLOUDSTACK-10271 maven plugin for owasp dependency check added URL: https://github.com/apache/cloudstack/pull/2446#issuecomment-364854961 @blueorangutan test This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > detect vulnerabilities in depndencies > - > > Key: CLOUDSTACK-10271 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10271 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Daan Hoogland >Assignee: Daan Hoogland >Priority: Major > > As a developer I want to know whether and what dependencies I am using that > might harm my users. For this we need to add the owasp dependency checker to > the maven build. It will require more then just this but it is a good first > step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10147) Disabled Xenserver cluster can still deploy VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360418#comment-16360418 ] ASF GitHub Bot commented on CLOUDSTACK-10147: - blueorangutan commented on issue #2442: CLOUDSTACK-10147 Disabled Xenserver Cluster can still deploy VM's URL: https://github.com/apache/cloudstack/pull/2442#issuecomment-364854142 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1706 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Disabled Xenserver cluster can still deploy VMs > > > Key: CLOUDSTACK-10147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.10.0.0, 4.9.2.0 > Environment: Xenserver 6.2, 7 >Reporter: Glenn Wagner >Assignee: Henko Holtzhausen >Priority: Major > > ENVIRONMENT > = > XenServer Version : 6.2 , 7 > ISSUE > == > Disabled Xenserver Cluster can still deploy VM's , hosts in the cluster are > still active > Repro. steps followed > == > Disabled Cluster from UI. > Deploy a new VM > Expected Behavior > === > After disabling the cluster , the hosts should be disabled. and no VM's can > be deployed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10250) Reinstall VM from bypassed registered template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360420#comment-16360420 ] ASF GitHub Bot commented on CLOUDSTACK-10250: - blueorangutan commented on issue #2423: CLOUDSTACK-10250: Reinstall VM from bypassed registered template URL: https://github.com/apache/cloudstack/pull/2423#issuecomment-364854140 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1707 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Reinstall VM from bypassed registered template > -- > > Key: CLOUDSTACK-10250 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10250 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.11.0.0 >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > This fix allows users to restore a VM from a previously registered template > using the Direct Download option (only for KVM currently) > NOTE: As Reinstall VM button prompts only featured templates, to be able to > restore a vm to a Direct Download template, it should be registered as > Featured -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10271) detect vulnerabilities in depndencies
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360419#comment-16360419 ] ASF GitHub Bot commented on CLOUDSTACK-10271: - blueorangutan commented on issue #2446: CLOUDSTACK-10271 maven plugin for owasp dependency check added URL: https://github.com/apache/cloudstack/pull/2446#issuecomment-364854141 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1705 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > detect vulnerabilities in depndencies > - > > Key: CLOUDSTACK-10271 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10271 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Daan Hoogland >Assignee: Daan Hoogland >Priority: Major > > As a developer I want to know whether and what dependencies I am using that > might harm my users. For this we need to add the owasp dependency checker to > the maven build. It will require more then just this but it is a good first > step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10284) Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360416#comment-16360416 ] ASF GitHub Bot commented on CLOUDSTACK-10284: - ustcweizhou commented on issue #2451: CLOUDSTACK-10284:Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM. URL: https://github.com/apache/cloudstack/pull/2451#issuecomment-364853929 @niteshsarda sorry I cannot merge it now. two issues (1) what if the instance is removed ? (2) what if we view the vm snapshots from Storage -> VM Snapshots -> select vm snapshot ? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM. > -- > > Key: CLOUDSTACK-10284 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10284 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitesh Sarda >Priority: Major > > ISSUE > Creating a snapshot from VM Snapshot generates error if hypervisor is not KVM. > STEPS TO REPRODUCE > * Create a cloudstack setup with hypervisor other than KVM. > * Create an instance. > * Take Snapshot of that VM. > * Try to take volume snapshot from newly created VM snapshot. > * It will throw an error as hypervisor is not KVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
