blueorangutan commented on pull request #784:
URL:
https://github.com/apache/cloudstack-primate/pull/784#issuecomment-702558006
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/784 (JID-3
blueorangutan commented on pull request #784:
URL:
https://github.com/apache/cloudstack-primate/pull/784#issuecomment-702554922
@utchoang a Jenkins job has been kicked to build primate packages. I'll keep
you posted as I make progress.
utchoang commented on pull request #784:
URL:
https://github.com/apache/cloudstack-primate/pull/784#issuecomment-702554637
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the me
utchoang opened a new pull request #784:
URL: https://github.com/apache/cloudstack-primate/pull/784
Fixes #781
@rhtyd cc @svenvogel
Please review it. Thanks.
This is an automated message from the Apache Git Service.
T
jlk opened a new pull request #77:
URL: https://github.com/apache/cloudstack-www/pull/77
Updated the security page to reflect ACS no longer having separate security
team but instead working with ASF security team.
This is an
rhtyd opened a new issue #19:
URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/19
I see many scripts and go files don't have the Apache license header, we
need to fix that. cc @onitake
This is an automat
rhtyd commented on pull request #18:
URL:
https://github.com/apache/cloudstack-kubernetes-provider/pull/18#issuecomment-702097821
Thanks @onitake I'll reply on that as well
This is an automated message from the Apache Git Se
Hi Dirk,
My second problem is with git branches. My problem here is that I wanted to use
the cloudstack version 4.13.1 as base, for this reason I checkout the 4.13.1
branch, but the build process goes wrong with a couple of errors, after this I
checkout the master and revert it to the commit
shwstppr edited a comment on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-702089677
@nvazquez @rhtyd will this make Primate UI incompatible with older ACS
relases?
This is an au
shwstppr commented on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-702089677
@nvazquez @rhtyd will this make Primate UI backward incompatible?
This is an automated message from t
onitake commented on pull request #18:
URL:
https://github.com/apache/cloudstack-kubernetes-provider/pull/18#issuecomment-702073493
@rhtyd I created the INFRA ticket here:
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20921
I wasn't sure about all the options, please correc
shwstppr commented on issue #782:
URL:
https://github.com/apache/cloudstack-primate/issues/782#issuecomment-702071470
@DaanHoogland not yet. I think the 404 bug for destroy VM got introduced
with the custom componenent that has been added for `destroyVirtualMachine`
API. Otherwise the cod
blueorangutan commented on pull request #780:
URL:
https://github.com/apache/cloudstack-primate/pull/780#issuecomment-702053951
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/780 (JID-3
DaanHoogland commented on issue #782:
URL:
https://github.com/apache/cloudstack-primate/issues/782#issuecomment-702053742
there is an issue with 404 when destroying a VM as well (#753) , probably
related (by looking from the outside in) did you consider this as a generic
problem, yet @shw
blueorangutan commented on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-702053631
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/777 (JID-3
shwstppr edited a comment on issue #782:
URL:
https://github.com/apache/cloudstack-primate/issues/782#issuecomment-702051518
@rhtyd added a tentative fix which should resolve the issue. Will update
after more testing cc @vladimirpetrov
---
shwstppr commented on issue #782:
URL:
https://github.com/apache/cloudstack-primate/issues/782#issuecomment-702051518
@rhtyd added a tentative fix which should resolve the issue. Will update
after more testing
This is an au
shwstppr commented on pull request #783:
URL:
https://github.com/apache/cloudstack-primate/pull/783#issuecomment-702051197
@blueorganutan package
This is an automated message from the Apache Git Service.
To respond to the me
shwstppr opened a new pull request #783:
URL: https://github.com/apache/cloudstack-primate/pull/783
Route back on VM unmanage
Fixes #782
This is an automated message from the Apache Git Service.
To respond to the mess
rhtyd commented on pull request #780:
URL:
https://github.com/apache/cloudstack-primate/pull/780#issuecomment-702049310
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the messa
blueorangutan commented on pull request #780:
URL:
https://github.com/apache/cloudstack-primate/pull/780#issuecomment-702049682
@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep
you posted as I make progress.
---
blueorangutan commented on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-702049278
@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep
you posted as I make progress.
---
rhtyd commented on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-702048895
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the messa
rhtyd merged pull request #770:
URL: https://github.com/apache/cloudstack-primate/pull/770
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
rhtyd commented on issue #782:
URL:
https://github.com/apache/cloudstack-primate/issues/782#issuecomment-702034629
@shwstppr can you check and advise?
This is an automated message from the Apache Git Service.
To respond to t
vladimirpetrov opened a new issue #782:
URL: https://github.com/apache/cloudstack-primate/issues/782
**Describe the bug**
When you unmanage a VM, a 404 error (not found) page is shown.
**To Reproduce**
Steps to reproduce the behavior:
1. Log in as a User or an Admin
2.
onitake opened a new pull request #18:
URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/18
This PR adds a Travis-CI script, test cases, and applies `go fmt` to satisfy
the formatting check.
It should be merged after Travis is enabled on the Github repository, so we
rhtyd merged pull request #776:
URL: https://github.com/apache/cloudstack-primate/pull/776
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
davidjumani commented on pull request #761:
URL:
https://github.com/apache/cloudstack-primate/pull/761#issuecomment-701989277
I also think similar changes might be required. After an async job completes
the page refreshes. However, it shouldn't if the user is not on the same page.
Eg: Aft
borisstoyanov opened a new issue #781:
URL: https://github.com/apache/cloudstack-primate/issues/781
**Describe the bug**
Some usability from old ui can be implemented here as well. When ever we
have a confirmation screen we need to click with the mouse, instead as per the
old ui we can
rhtyd edited a comment on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-701969242
@andrijapanicsb can you review/test this and against expected behaviour for
upstream?
This is an
rhtyd commented on pull request #777:
URL:
https://github.com/apache/cloudstack-primate/pull/777#issuecomment-701969242
@andrijapanicsb can you review/test this and against expected feature for
upstream?
This is an automate
rhtyd commented on a change in pull request #775:
URL: https://github.com/apache/cloudstack-primate/pull/775#discussion_r498060019
##
File path: src/views/image/IsoZones.vue
##
@@ -32,15 +32,15 @@
33 matches
Mail list logo
