[jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357711#comment-16357711 ] ASF GitHub Bot commented on CLOUDSTACK-10269: - blueorangutan commented on issue #2444: CLOUDSTACK-10269: On deletion of role set name to null URL: https://github.com/apache/cloudstack/pull/2444#issuecomment-364285841 Trillian test result (tid-2240) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 27361 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2444-t2240-kvm-centos7.zip 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 > Allow deletion of roles without causing concurrent exception > > > Key: CLOUDSTACK-10269 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10269 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Major > Fix For: Future, 4.11.1.1, 4.12.0.0 > > > Deletion of a role renames the role with a timestamp, when roles are > created/deleted aggresively it may cause concurrent exceptions. The fix is to > follow how other cloudstack entities are removed where name uniqueness need > to be honoured, i.e. by setting the field to null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10132) Multiple Management Servers Support for agents
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357466#comment-16357466 ] ASF GitHub Bot commented on CLOUDSTACK-10132: - blueorangutan commented on issue #2309: CLOUDSTACK-10132: Multiple Management Servers Support for agents URL: https://github.com/apache/cloudstack/pull/2309#issuecomment-364224932 Trillian test result (tid-2239) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 29590 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2309-t2239-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Smoke tests completed. 66 look OK, 1 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_network_garbage_collector_nics | `Failure` | 293.89 | test_vpc_redundant.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 > Multiple Management Servers Support for agents > -- > > Key: CLOUDSTACK-10132 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10132 > Project: CloudStack > Issue Type: Improvement > 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 > > Multiple Management Servers Support for agents -- 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=16357271#comment-16357271 ] 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-364188866 It works for the most part, but it doesn't seem to like VNI ids higher than those for VLANs which is 4096, however VXLAN's max id is about 16 millions, so this is a problem that needs a fix. Here are some logs: 2018-02-08 15:50:00,738 WARN [resource.wrapper.LibvirtStartCommandWrapper] (agentRequest-Handler-4:null) (logid:bd9fbea5) InternalErrorException com.cloud.exception.InternalErrorException: Failed to create vnet 3: RTNETLINK answers: Numerical result out of rangeCannot find device "bond0.3"Failed to create vlan 3 on pif: bond0. 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 >
[jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357066#comment-16357066 ] ASF GitHub Bot commented on CLOUDSTACK-10269: - blueorangutan commented on issue #2444: CLOUDSTACK-10269: On deletion of role set name to null URL: https://github.com/apache/cloudstack/pull/2444#issuecomment-364148442 @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 > Allow deletion of roles without causing concurrent exception > > > Key: CLOUDSTACK-10269 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10269 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Major > Fix For: Future, 4.11.1.1, 4.12.0.0 > > > Deletion of a role renames the role with a timestamp, when roles are > created/deleted aggresively it may cause concurrent exceptions. The fix is to > follow how other cloudstack entities are removed where name uniqueness need > to be honoured, i.e. by setting the field to null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357062#comment-16357062 ] ASF GitHub Bot commented on CLOUDSTACK-10269: - blueorangutan commented on issue #2444: CLOUDSTACK-10269: On deletion of role set name to null URL: https://github.com/apache/cloudstack/pull/2444#issuecomment-363818026 Trillian test result (tid-2232) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 17201 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2444-t2232-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_accounts.py Intermitten failure detected: /marvin/tests/smoke/test_affinity_groups_projects.py Intermitten failure detected: /marvin/tests/smoke/test_affinity_groups.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_virtio_scsi_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_iso.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vms_with_varied_deploymentplanners.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_with_userdata.py Intermitten failure detected: /marvin/tests/smoke/test_internal_lb.py Intermitten failure detected: /marvin/tests/smoke/test_iso.py Intermitten failure detected: /marvin/tests/smoke/test_list_ids_parameter.py Intermitten failure detected: /marvin/tests/smoke/test_loadbalance.py Intermitten failure detected: /marvin/tests/smoke/test_metrics_api.py Intermitten failure detected: /marvin/tests/smoke/test_migration.py Intermitten failure detected: /marvin/tests/smoke/test_multipleips_per_nic.py Intermitten failure detected: /marvin/tests/smoke/test_nested_virtualization.py Intermitten failure detected: /marvin/tests/smoke/test_network_acl.py Intermitten failure detected: /marvin/tests/smoke/test_network.py Intermitten failure detected: /marvin/tests/smoke/test_nic.py Intermitten failure detected: /marvin/tests/smoke/test_over_provisioning.py Intermitten failure detected: /marvin/tests/smoke/test_password_server.py Intermitten failure detected: /marvin/tests/smoke/test_portforwardingrules.py Intermitten failure detected: /marvin/tests/smoke/test_primary_storage.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_projects.py Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py Intermitten failure detected: /marvin/tests/smoke/test_reset_vm_on_reboot.py Intermitten failure detected: /marvin/tests/smoke/test_router_dhcphosts.py Intermitten failure detected: /marvin/tests/smoke/test_router_dns.py Intermitten failure detected: /marvin/tests/smoke/test_router_dnsservice.py Intermitten failure detected: /marvin/tests/smoke/test_routers_iptables_default_policy.py Intermitten failure detected: /marvin/tests/smoke/test_routers_network_ops.py Intermitten failure detected: /marvin/tests/smoke/test_routers.py Intermitten failure detected: /marvin/tests/smoke/test_secondary_storage.py Intermitten failure detected: /marvin/tests/smoke/test_service_offerings.py Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py Intermitten failure detected: /marvin/tests/smoke/test_templates.py Intermitten failure detected: /marvin/tests/smoke/test_usage.py Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py Intermitten failure detected: /marvin/tests/smoke/test_vm_snapshots.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_router_nics.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py Smoke tests completed. 22 look OK, 45 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_01_create_iso_with_checksum_sha1 | `Error` | 65.34 | test_iso.py test_02_create_iso_with_checksum_sha256 | `Error` | 65.32 | test_iso.py test_03_create_iso_with_checksum_md5 | `Error` | 65.33 | test_iso.py test_04_create_iso_with_no_checksum | `Error` | 65.33 | test_iso.py test_01_create_iso | `Failure` | 1511.54 | test_iso.py ContextSuite context=TestISO>:setup | `Error` | 3024.31 | test_iso.py ContextSuite context=TestAccounts>:setup | `Error` | 0.00 | test_accounts.py ContextSuite context=TestAddVmToSubDomain>:setup | `Error` | 0.00 | test_accounts.py test_DeleteDomain | `Error` |
[jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357065#comment-16357065 ] ASF GitHub Bot commented on CLOUDSTACK-10269: - rhtyd commented on issue #2444: CLOUDSTACK-10269: On deletion of role set name to null URL: https://github.com/apache/cloudstack/pull/2444#issuecomment-364148204 @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 > Allow deletion of roles without causing concurrent exception > > > Key: CLOUDSTACK-10269 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10269 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Major > Fix For: Future, 4.11.1.1, 4.12.0.0 > > > Deletion of a role renames the role with a timestamp, when roles are > created/deleted aggresively it may cause concurrent exceptions. The fix is to > follow how other cloudstack entities are removed where name uniqueness need > to be honoured, i.e. by setting the field to null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357063#comment-16357063 ] ASF GitHub Bot commented on CLOUDSTACK-10269: - blueorangutan commented on issue #2444: CLOUDSTACK-10269: On deletion of role set name to null URL: https://github.com/apache/cloudstack/pull/2444#issuecomment-363731713 @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 > Allow deletion of roles without causing concurrent exception > > > Key: CLOUDSTACK-10269 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10269 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Major > Fix For: Future, 4.11.1.1, 4.12.0.0 > > > Deletion of a role renames the role with a timestamp, when roles are > created/deleted aggresively it may cause concurrent exceptions. The fix is to > follow how other cloudstack entities are removed where name uniqueness need > to be honoured, i.e. by setting the field to null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10269) Allow deletion of roles without causing concurrent exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357064#comment-16357064 ] ASF GitHub Bot commented on CLOUDSTACK-10269: - borisstoyanov commented on issue #2444: CLOUDSTACK-10269: On deletion of role set name to null URL: https://github.com/apache/cloudstack/pull/2444#issuecomment-363731571 @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 > Allow deletion of roles without causing concurrent exception > > > Key: CLOUDSTACK-10269 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10269 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav >Priority: Major > Fix For: Future, 4.11.1.1, 4.12.0.0 > > > Deletion of a role renames the role with a timestamp, when roles are > created/deleted aggresively it may cause concurrent exceptions. The fix is to > follow how other cloudstack entities are removed where name uniqueness need > to be honoured, i.e. by setting the field to null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CLOUDSTACK-10277) Console Proxy and SSVM blocked in starting state
Thomas ZAEPFFEL created CLOUDSTACK-10277: Summary: Console Proxy and SSVM blocked in starting state Key: CLOUDSTACK-10277 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10277 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.9.0.1 Environment: Cloudstack 4.9 xenserver 7.3 Reporter: Thomas ZAEPFFEL Hi all, I've installed cloudstack management 4.9 on Ubuntu 14.04.05 192.168.117.128 Dedicated NFS server for primary and secondary storage on ubuntu 14.04.05 192.168.117.129 Xenserver 7.3 as hypervisor 192.168.117.130 I'm facing an issue at the last configuration step, console proxy and secondary storage VMs are still in starting state in the cloudstack management WebUI. VMs are created, and started I can see them in the xencenter. In management-server.log I have the following messages, connections to v-2-M and v-1-M on 169.254.x.x adresses, that are failing : 2018-02-08 14:24:53,663 DEBUG [c.c.h.x.r.w.x.CitrixStartCommandWrapper] (DirectAgent-11:ctx-7637ba0a) (logid:7510a60e) 2. The VM v-2-VM is in Running state. 2018-02-08 14:24:53,669 DEBUG [c.c.h.x.r.w.x.CitrixCheckSshCommandWrapper] (DirectAgent-11:ctx-7637ba0a) (logid:7510a60e) Ping command port, 169.254.3.194:3922 2018-02-08 14:24:53,672 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-11:ctx-7637ba0a) (logid:7510a60e) Trying to connect to 169.254.3.194 attempt 0 of 100 Did I miss something during configuration? Thank you, Thomas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CLOUDSTACK-10276) View volumes from primary storage not working when storage UUID is not a UUID
Rafael Weingärtner created CLOUDSTACK-10276: --- Summary: View volumes from primary storage not working when storage UUID is not a UUID Key: CLOUDSTACK-10276 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10276 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Rafael Weingärtner Assignee: Rafael Weingärtner When configuration a pre-setup primary storage we can enter the name-label of the storage that is going to be used by ACS and is already set up in the host. The problem is that we can use any String of characters there, and this String does not need to be a UUID one. When listing volumes from a primary storage that has such conditions, the list will return all of the volumes in the cloud because the ad-hoc “API framework” will ignore that value as it is not a UUID type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-9677) Swift Storage Policy support for Secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356808#comment-16356808 ] ASF GitHub Bot commented on CLOUDSTACK-9677: blueorangutan commented on issue #2412: CLOUDSTACK-9677: Adding storage policy support for swift as secondary… URL: https://github.com/apache/cloudstack/pull/2412#issuecomment-364078295 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1695 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 > Swift Storage Policy support for Secondary Storage > -- > > Key: CLOUDSTACK-9677 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9677 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Patrick D. >Assignee: Patrick D. >Priority: Major > -- 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=16356807#comment-16356807 ] 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-364078111 I think it would be best to have a apache jenkins job that reports to sec@ that doesn't exclude your idea btw, @rafaelweingartner 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=16356792#comment-16356792 ] ASF GitHub Bot commented on CLOUDSTACK-10271: - rafaelweingartner commented on issue #2446: CLOUDSTACK-10271 maven plugin for owasp dependency check added URL: https://github.com/apache/cloudstack/pull/2446#issuecomment-364075710 So, what we need is a jenkins job to report the "sanity/quality" of a PR's dependencies as a status in the Github's PR page. 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=16356788#comment-16356788 ] 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-364074852 Let me add to that: I think a PR should be stopped on a dependency CVE but a build should not fail. Builds must be reproducible even (or especially) when there are vulnerabilities in it. 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=16356780#comment-16356780 ] 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-364072274 No @marcaurele, we need to go there I agree, but it is a bridge to far 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 > 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-9677) Swift Storage Policy support for Secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356779#comment-16356779 ] ASF GitHub Bot commented on CLOUDSTACK-9677: blueorangutan commented on issue #2412: CLOUDSTACK-9677: Adding storage policy support for swift as secondary… URL: https://github.com/apache/cloudstack/pull/2412#issuecomment-364072006 @DaanHoogland 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 > Swift Storage Policy support for Secondary Storage > -- > > Key: CLOUDSTACK-9677 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9677 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Patrick D. >Assignee: Patrick D. >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-9677) Swift Storage Policy support for Secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356777#comment-16356777 ] ASF GitHub Bot commented on CLOUDSTACK-9677: DaanHoogland commented on issue #2412: CLOUDSTACK-9677: Adding storage policy support for swift as secondary… URL: https://github.com/apache/cloudstack/pull/2412#issuecomment-364071766 @khos2ow no, it seems to never have started, retrying @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 > Swift Storage Policy support for Secondary Storage > -- > > Key: CLOUDSTACK-9677 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9677 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Patrick D. >Assignee: Patrick D. >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
