Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare
Syed, AFAIK the standard behaviour that is baked in the password script as well as in the cloud-init Cloudstack meta source is to try whichever address provides the DHCP. Can't wait to see config drive implemented so we can get rid of all these head aches. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Syed Ahmed" > To: "dev" > Sent: Sunday, 2 April, 2017 03:50:50 > Subject: Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 > and VMWare > The SSH key doesn't work either. The default password for the centos > user is set at boot time to `password` which happens via the scripts > in the template itself. Coud-init is trying to fetch the metadata from > the default gateway instead of the VR (which which has a different IP > than the default GW) > > On Fri, Mar 31, 2017 at 4:08 PM, Nux! wrote: >> Hm, ok, so this is a corner case I'll need to cover then. >> But how did the password/sshkey feature work, if at all? >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> - Original Message - >>> From: "Syed Ahmed" >>> To: "dev" >>> Sent: Friday, 31 March, 2017 19:10:22 >>> Subject: Re: Need help in getting CentOS 7 templates to run on Cloudstack >>> 4.9 >>> and VMWare >> >>> I'm using a shared network so the VR is not the gateway. >>> >>> On Fri, Mar 31, 2017 at 12:49 PM, Nux! wrote: Syed, I just checked and centos user is added to sudoers, if it was not added to your instance, then cloud-init did not complete properly. I have seen this in the past when the data source is not reached properly. I would double check the cloud-init logs if I were you, make sure eth0 was up properly and the VR accessible. http://storage1.static.itmages.com/i/17/0331/h_1490978820_8688282_efdf2d86f5.png -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Nux!" > To: "dev" > Sent: Friday, 31 March, 2017 17:01:43 > Subject: Re: Need help in getting CentOS 7 templates to run on Cloudstack > 4.9 > and VMWare > Thanks, I'll check. > Cloud-init is supposed to add the user to sudo. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - >> From: "Syed Ahmed" >> To: "dev" >> Sent: Friday, 31 March, 2017 16:54:21 >> Subject: Re: Need help in getting CentOS 7 templates to run on >> Cloudstack 4.9 >> and VMWare > >> Hi Nux, >> >> One of the things that I've seen is that the user centos is not added >> to the sudoers. >> >> On Fri, Mar 31, 2017 at 8:06 AM, Nux! wrote: >>> Excellent, let me know if you hit any more issues. >>> >>> -- >>> Sent from the Delta quadrant using Borg technology! >>> >>> Nux! >>> www.nux.ro >>> >>> - Original Message - From: "Syed Ahmed" To: "dev" Sent: Friday, 31 March, 2017 12:58:21 Subject: Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare >>> Hey Nux, It worked! Thanks for fixing this. I am able to ping the VM now. On Fri, Mar 31, 2017 at 4:17 AM, Nux! wrote: > Syed, > > I am aware of the renaming issue and avoid it, if you check my > kickstart I > specifically add biosdevname=0 and net.ifnames=0 > http://jenkins.openvm.eu/cloudstack/config/centos/centos7-vmware.cfg > > However yesterday Rohit brought to my attention the ova generation > script > inserts a e1000 eth0 which apparently breaks things in certain > situations. > https://github.com/apache/cloudstack/pull/2022#issuecomment-290339928 > > I corrected the script and built a new image here, please give it a > try. > http://jenkins.openvm.eu/cloudstack/centos/x86_64/centos-7-vmware.ova > > If the problem persists, can you go in single user mode and check the > /proc/cmdline and share it here? > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - >> From: "Syed Ahmed" >> To: "Nux!" >> Cc: "dev" >> Sent: Thursday, 30 March, 2017 23:54:36 >> Subject: Re: Need help in getting CentOS 7 templates to run on >> Cloudstack 4.9 >> and VMWare > >> I tried the one you provided however, it still has the same problem >> ... DHCP doesn't seem to pick up. I also see that the interface is >> not >> named eth0 .. could this be the problem? I can try ch
Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare
On Mon, Apr 3, 2017 at 9:41 AM, Nux! wrote: > Syed, > > AFAIK the standard behaviour that is baked in the password script as well as > in the cloud-init Cloudstack meta source is to try whichever address provides > the DHCP. > > Can't wait to see config drive implemented so we can get rid of all these > head aches. Or the 169.254.169.254 address implemented :-) -- Erik
[GitHub] cloudstack issue #2023: BUG-ID: CLOUDSTACK-9808 Added system Vm upgrade path...
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/2023 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #2024: CLOUDSTACK-9857: With this change if agent di...
GitHub user abhinandanprateek opened a pull request: https://github.com/apache/cloudstack/pull/2024 CLOUDSTACK-9857: With this change if agent dies the systemd will catc⦠â¦h it properly and show process as exited You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack CLOUDSTACK-9857 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/2024.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2024 commit 3eb633a100a71193c4999172f494f6ce2175866d Author: Abhinandan Prateek Date: 2017-04-03T10:46:21Z CLOUDSTACK-9857: With this change if agent dies the systemd will catch it properly and show process as exited --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2024 @blueorangutan package --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2024 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #892: CLOUDSTACK-8910: The reserved_capacity field increase...
Github user jayantpatil1234 commented on the issue: https://github.com/apache/cloudstack/pull/892 I have tested this and LGTM for test. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2024 Packaging result: âcentos6 âcentos7 âdebian. JID-611 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #892: CLOUDSTACK-8910: The reserved_capacity field increase...
Github user SudharmaJain commented on the issue: https://github.com/apache/cloudstack/pull/892 tag:mergeready --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1734: CLOUDSTACK-9567 Difference in the api call outputs f...
Github user SudharmaJain commented on the issue: https://github.com/apache/cloudstack/pull/1734 tag:mergeready --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1246: CLOUDSTACK-9165 unable to use reserved IP range in a...
Github user SudharmaJain commented on the issue: https://github.com/apache/cloudstack/pull/1246 tag:mergeready --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #883: CLOUDSTACK-8906: /var/log/cloud/ doesn't get logrotat...
Github user SudharmaJain commented on the issue: https://github.com/apache/cloudstack/pull/883 tag:mergeready --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: :[VOTE] Apache Cloudstack 4.10.0.0
Look like we need a new systemvm named "systemvm-xenserver-4.10". t also seams that older VR ex: 4.7.x are still usable if the globalsetting "minreq.sysvmtemplate.version" is changed after the first boot of cloudstack-management that upgraded the database. I'll update the release note acordingly... So this 4.10 is looking promising! :-) On Apr 1, 2017 16:02, "Pierre-Luc Dion" wrote: I'm testing upgrade to 4.10 from latest master. I have the following error when upgrading from 4.7.2 in management-server.log: 2017-04-01 15:58:12,558 DEBUG [c.c.u.d.Upgrade4920to41000] (localhost-startStop-1:null) (logid:) Updating System Vm template IDs 2017-04-01 15:58:12,561 DEBUG [c.c.u.d.Upgrade4920to41000] (localhost-startStop-1:null) (logid:) Updating KVM System Vms 2017-04-01 15:58:12,561 WARN [c.c.u.d.Upgrade4920to41000] (localhost-startStop-1:null) (logid:) 4.10.0.0KVM SystemVm template not found. KVM hypervisor is not used, so not failing upgrade 2017-04-01 15:58:12,562 DEBUG [c.c.u.d.Upgrade4920to41000] (localhost-startStop-1:null) (logid:) Updating VMware System Vms 2017-04-01 15:58:12,563 WARN [c.c.u.d.Upgrade4920to41000] (localhost-startStop-1:null) (logid:) 4.10.0.0VMware SystemVm template not found. VMware hypervisor is not used, so not failing upgrade 2017-04-01 15:58:12,563 DEBUG [c.c.u.d.Upgrade4920to41000] (localhost-startStop-1:null) (logid:) Updating XenServer System Vms 2017-04-01 15:58:12,565 ERROR [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: 4.10.0.0XenServer SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade4920to41000.updateSystemVmTempl ates(Upgrade4920to41000.java:195) at com.cloud.upgrade.dao.Upgrade4920to41000.performDataMigratio n(Upgrade4920to41000.java:64) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpg radeChecker.java:426) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgra deChecker.java:507) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif eCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif eCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcesso r.doStart(DefaultLifecycleProcessor.java:173) at org.springframework.context.support.DefaultLifecycleProcesso r.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcesso r$LifecycleGroup.start(DefaultLifecycleProcessor.java:346) at org.springframework.context.support.DefaultLifecycleProcesso r.startBeans(DefaultLifecycleProcessor.java:149) at org.springframework.context.support.DefaultLifecycleProcesso r.onRefresh(DefaultLifecycleProcessor.java:112) at org.springframework.context.support.AbstractApplicationConte xt.finishRefresh(AbstractApplicationContext.java:879) at org.springframework.context.support.AbstractApplicationConte xt.refresh(AbstractApplicationContext.java:545) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet.withModule(DefaultModuleDefinitionSet.java:233) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117) at org.apache.cloudstack.spring.module.model.impl.DefaultModule DefinitionSet.load(DefaultModuleDefinitionSet.java:79) at org.apache.cloudstack.spring.module.factory.ModuleBasedConte xtFactory.loadModules(ModuleBasedContextFactory.java:37) at org.apache.cloudstack.spring.module.factory.CloudStackSpring Context.init(CloudStackSpringContext.java:71) at org.apache.cloudstack.spring.module.factory.CloudStackSpring Context.(CloudStackSpringContext.java:58) at org.apache.cloudstack.spring.module.factory.CloudStackSpring Context.(CloudStackSpringContext.java:62) at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener. contextInitialized(CloudStackContextLoaderListener.java:52) at org.apache.catalina.core.StandardContext.listenerStart(Stand ardContext.java:5068) at org.apache.catalina.core.StandardContext.startInternal(Stand ardContext.java:5584) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.ContainerBase.addChildInternal(Cont ainerBase.java:899) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) at org.apach
[GitHub] cloudstack issue #899: BUG-ID:CLOUDSTACK-8921 snapshot_store_ref table shoul...
Github user jayakarteek commented on the issue: https://github.com/apache/cloudstack/pull/899 @yvsubhash Tested the changes, tests LGTM. below are the results root@MgmtServerNitesh:/mnt/jayant/snapshots/2/120# ls -l total 1142048 -rw-r-+ 1 root root 1168306688 Apr 3 18:13 9c340447-5ff9-49f3-875e-1dbbcf63ccf9.vhd mysql> select * from snapshot_store_ref; ++--+-+-+--+++-+---++--+---+--+-+-+---+ | id | store_id | snapshot_id | created | last_updated | job_id | store_role | size| physical_size | parent_snapshot_id | install_path | state | update_count | ref_cnt | updated | volume_id | ++--+-+-+--+++-+---++--+---+--+-+-+---+ | 0 | 2017-04-03 12:53:16 | 120 | | 12 |6 | 6 | 2017-04-03 12:53:17 | NULL | NULL | Image | 5368709120 |1168306688 | 0 | snapshots/2/120/9c340447-5ff9-49f3-875e-1dbbcf63ccf9.vhd | Ready | 2 | 0 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
CloudStack Collaboration Conference Miami deadline fast approaching!
All, We're only weeks away from an extremely exciting CloudStack Collaboration Conference (CCC) colocated at ApacheCon NA, in beautiful Miami, FL. Don't miss out on great talks, exciting networking opportunities and the ability to see the latest and greatest on everything CloudStack. If you are a current Apache committer, or in the academic field, you qualify for a registration discount, so don't hesitate - register immediately! Standard registration discount ends on April 16th, so hurry and confirm your seat now, as space is limited. If you are a confirmed speaker, you should have received a special registration code, so don't forget that you still need to register in order to attend! http://events.linuxfoundation.org/events/apachecon-north-america/attend/register- - Si
Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare
I'd love to see the 169.254.169.254 implemented. Maybe something we can hack on at the CCC in Miami ;) On Mon, Apr 3, 2017 at 4:24 AM, Erik Weber wrote: > On Mon, Apr 3, 2017 at 9:41 AM, Nux! wrote: >> Syed, >> >> AFAIK the standard behaviour that is baked in the password script as well as >> in the cloud-init Cloudstack meta source is to try whichever address >> provides the DHCP. >> >> Can't wait to see config drive implemented so we can get rid of all these >> head aches. > > Or the 169.254.169.254 address implemented :-) > > -- > Erik
Re: [VOTE] Retirement of midonet plugin
Folks, I am now closing the voting for the retirement of the Midonet plugin. The final tally is: [+1] 12 [0] null [-1] null Based on this result I will move forward the retirement process. Thank you all for your valuable contributions to the discussion thread and then showing your opinion on the voting thread. On Wed, Mar 29, 2017 at 10:09 PM, Sateesh Chodapuneedi < sateesh.chodapune...@accelerite.com> wrote: > +1 > > Regards, > Sateesh > > From: Rafael Weingärtner > Sent: 29 March 2017 02:16:09 > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org > Subject: [VOTE] Retirement of midonet plugin > > Dear ACS fellows, > We have discussed the retirement of Midonet plugin [*]. After quite > some > talk, we converged in a retirement process and it seems that we all > agree > that the Midonet plugin should be retired. So, to formalize things, we > should vote Midonet retirement. > > All users and devs are welcome to vote here: > [+1] I *do want to retire *the Midonet plugin > [0] Whatever happens I am happy > [-1] I *do not want to retire* the Midonet plugin > > > [*] http://markmail.org/message/x6p3gnvqbbxcj6gs > > -- > Rafael Weingärtner > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > > > > > DISCLAIMER > == > This e-mail may contain privileged and confidential information which is > the property of Accelerite, a Persistent Systems business. It is intended > only for the use of the individual or entity to which it is addressed. If > you are not the intended recipient, you are not authorized to read, retain, > copy, print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Accelerite, a Persistent Systems business does not accept any > liability for virus infected mails. > -- Rafael Weingärtner
Register for CCC Miami
Hello Everyone, We are now into April and the CCC is starting to get closer. If you have not registered already, get on it before the pricing changes again. The prices go up again on April 16th [1], so make sure you get your tickets before then. This is going to be a great event with a lot of opportunities to meet other developers and users who successfully leverage Apache CloudStack in their organizations. There are still sponsorship opportunities [2], so please get in touch if you are interested in sponsoring. Looking forward to a lot of great conversations, ideas and collaboration. See you in Miami, ***Will Stevens* [1] http://us.cloudstackcollab.org/#attend [ 2] http://us.cloudstackcollab.org/#sponsors
Re: Register for CCC Miami
Will is right! Folks do not wait until the last minute to register. This ApacheCon is going to be a unique opportunity to meet our awesome community. Adding my two cents, I received this, and I think some of you that did not register may like it. > Register now and save 20% off your pass with code APCSP20 - bit.ly/2n0F5MO > . > I do not know if there is a limit of registration per discount code, but if there is. Please let us know. I think everyone that had a presentation accepted also received a discount code like this one. On Mon, Apr 3, 2017 at 10:55 AM, Will Stevens wrote: > Hello Everyone, > We are now into April and the CCC is starting to get closer. If you have > not registered already, get on it before the pricing changes again. > > The prices go up again on April 16th [1], so make sure you get your tickets > before then. > > This is going to be a great event with a lot of opportunities to meet other > developers and users who successfully leverage Apache CloudStack in their > organizations. > > There are still sponsorship opportunities [2], so please get in touch if > you are interested in sponsoring. > > Looking forward to a lot of great conversations, ideas and collaboration. > > See you in Miami, > > ***Will Stevens* > > [1] http://us.cloudstackcollab.org/#attend > [ > 2] > http://us.cloudstackcollab.org/#sponsors > > > -- Rafael Weingärtner
[GitHub] cloudstack pull request #2008: [CLOUDSTACK-9840] Fix datetime format of snap...
Github user olivierlemasle closed the pull request at: https://github.com/apache/cloudstack/pull/2008 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #2008: [CLOUDSTACK-9840] Fix datetime format of snap...
GitHub user olivierlemasle reopened a pull request: https://github.com/apache/cloudstack/pull/2008 [CLOUDSTACK-9840] Fix datetime format of snapshots events Include the timezone in datetime format of snapshot events, to be consistent with every other events. "eventDateTime" was added by @chipchilders in commit 14ee684ce3 and was updated the same day to add the timezone (commit bf967eb622f) except for Snapshots. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Amysta/cloudstack eventDateTimeTz Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/2008.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2008 commit b37ca77636feb22327d1b819657c6fd3913696fe Author: Olivier Lemasle Date: 2017-03-15T15:29:44Z Fix datetime format of snapshots events Include the timezone in datetime format of snapshot events, to be consistent with every other events. "eventDateTime" was added by @chipchilders in commit 14ee684ce3 and was updated the same day to add the timezone (commit bf967eb622f) except for Snapshots. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1725: CLOUDSTACK-9559 Why allow deleting zone without dele...
Github user yvsubhash commented on the issue: https://github.com/apache/cloudstack/pull/1725 tag:mergeready --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1996: CLOUDSTACK-9099: SecretKey is returned from the APIs
Github user jayapalu commented on the issue: https://github.com/apache/cloudstack/pull/1996 @rhtyd Once this PR got the LGTMs, I can rebase it on 4.9. Can you please review this PR --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
