This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
averharen
Level 3

Re: Creating volumes in vscale slows down with the increase of volumes in that account/tenant

by in Cloud Management Platform Forum
‎Jul 14, 2020 12:16 AM
‎Jul 14, 2020 12:16 AM
About a year ago, there weren't any concrete plans to resolve this.  We're now approaching  5k volumes in our largest account and we're worried this will shut us down soon...    Are you guys at Flexera just waiting for us to call support when it stops working?   Or, was it a foregone conclusion that we would evacuate Flexera solutions before we hit the danger threshold?   If there's anything Flexera can do, today, or sometime sooner than later would be good.     ... View more

Re: EPEL mirror errors for Collectd agent (repomd.xml does not match metalink for epel)

by in Cloud Management Platform Forum
‎Jun 16, 2020 12:26 PM
‎Jun 16, 2020 12:26 PM
I found another discussion on this topic and I am trying to figure out how I can use those if it should happen in the future. In this case, the issue persisted for many days: https://stackoverflow.com/questions/62359639/unable-to-install-packages-via-yum-in-aws-errno-1-repomd-xml-does-not-match ... View more

Re: EPEL mirror errors for Collectd agent (repomd.xml does not match metalink for epel)

by in Cloud Management Platform Forum
‎Jun 14, 2020 07:25 PM
1 Kudo
‎Jun 14, 2020 07:25 PM
1 Kudo
It appears there was an update on June 11, 2020 at fedora - possibly it took mirrors several days to catch up? ... View more

EPEL mirror errors for Collectd agent (repomd.xml does not match metalink for epel)

by in Cloud Management Platform Forum
‎Jun 13, 2020 12:14 PM
‎Jun 13, 2020 12:14 PM
Since yesterday, I am seeing intermittent issues where the deployments end up stranded, citing "repomd.xml does not match metalink for epel".  Is there a recommended way to handle this? RightScript: 'RL10 Linux Collectd v2 [rev 1]' Started at: 2020-06-13 00:55:13 PDT     (Details 970 lines) ******************************************************************************** *RS> RightScript: 'RL10 Linux Collectd v2 [rev 1]' *** *RS> COLLECTD_SERVER = 'tss3.rightscale.com' *RS> RS_INSTANCE_UUID = '03-0IL62MK23AD6E' *RS> Starting at 2020-06-13 00:55:13 PDT Loaded plugins: fastestmirror STDERR> Error: No matching Packages to list Installing EPEL repository STDERR> warning: /var/tmp/rpm-tmp.7dXlGw: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY Retrieving https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm Preparing... ######################################## Updating / installing... epel-release-7-12 ######################################## Loaded plugins: fastestmirror STDERR> http://mirror.siena.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.nodesdirect.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.atl.genesisadaptive.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.oss.ou.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.pit.teraswitch.com/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.grid.uchicago.edu/pub/linux/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.twinlakes.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirrors.sonic.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.mrjester.net/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://sjc.edge.kernel.org/fedora-buffet/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://epel.mirror.constant.com/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://dl.iad2.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: dl.iad2.fedoraproject.org; Name or service not known" STDERR> Trying other mirror. STDERR> https://ewr.edge.kernel.org/fedora-buffet/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.steadfastnet.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://fedora.mirrors.pair.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.compevo.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://fedora-epel.mirrors.tds.net/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://linux-mirrors.fnal.gov/linux/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.csis.ysu.edu/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirrors.mit.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://packages.oit.ncsu.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://download-cc-rdu01.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.vcu.edu/pub/gnu%2Blinux/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.team-cymru.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirrors.kernel.org/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.us-midwest-1.nexcess.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.coastal.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://reflector.westga.edu/repos/Fedora-EPEL/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.prgmr.com/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirrors.upr.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://fedora.westmancom.com/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.dst.ca/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel STDERR> Trying other mirror. STDERR> STDERR> STDERR> One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64), STDERR> and yum doesn't have enough cached data to continue. At this point the only STDERR> safe thing yum can do is fail. There are a few ways to work "fix" this: STDERR> STDERR> 1. Contact the upstream for the repository and get them to fix the problem. STDERR> STDERR> 2. Reconfigure the baseurl/etc. for the repository, to point to a working STDERR> upstream. This is most often useful if you are using a newer STDERR> distribution release than is supported by the repository (and the STDERR> packages for the previous distribution release still work). STDERR> STDERR> 3. Run the command with the repository temporarily disabled STDERR> yum --disablerepo=epel ... STDERR> STDERR> 4. Disable the repository permanently, so yum won't use it by default. Yum STDERR> will then just ignore the repository until you permanently enable it STDERR> again or use --enablerepo for temporary usage: STDERR> STDERR> yum-config-manager --disable epel STDERR> or STDERR> subscription-manager repos --disable=epel STDERR> STDERR> 5. Configure the failing repository to be skipped, if it is unavailable. STDERR> Note that yum will try to contact the repo. when it runs most commands, STDERR> so will have to try and fail each time (and thus. yum will be be much STDERR> slower). If it is a very temporary problem though, this is often a nice STDERR> compromise: STDERR> STDERR> yum-config-manager --save --setopt=epel.skip_if_unavailable=true STDERR> ... View more

Re: Self-Service - How to avoid CloudApps reaching a failed state if the operation that failed does ...

by in Cloud Management Platform Forum
‎Mar 03, 2020 07:59 PM
1 Kudo
‎Mar 03, 2020 07:59 PM
1 Kudo
Hi @spomeroy , I really don't have a solution for this issue. What I described doesn't even work, because the action fails due to the CloudApp being in a failed state. 1. The user needs to get a notice that something went wrong, and a failed cloudApp does that. I've made sure to include relevant messaging. Sure, I can ignore the error, but that's not what I want - the owner(s) need to understand there was a problem.  2. The user doesn't have the ability to address it, because the app is in a FAILED state. It now requires an admin.  People launching CloudApps should have the ability to put it back in Running state, but they don't have that privilege. What's the privilege needed for the user to be able to put it back into a Running state? If I make the user admin, they can see everyone's CloudApps, I don't want that. Thanks if you have any better suggestions! ... View more

Re: August 2019 CMP and Policy Release Summary

by in Cloud Management Platform Release Blog
‎Nov 04, 2019 04:07 PM
1 Kudo
‎Nov 04, 2019 04:07 PM
1 Kudo
Here's an idea for future policy development -- include a policy ownership framework: 1. Administrators having the ability to destroy or access resources may not fit everyone's security model. (Ask the NSA, "re: PRIVAC and Ed S."). 2. Current policies do not take the end-user or owner into consideration.  3. Current policies do not leverage roles (only at the level of access management) -- A lot of parts to the policy implementation now exist, but I think what's needed also is policy ownership framework. I'm thinking that each account in Cloud Management should have some settings defined, such as; Per Account Per type of policy (cost/security/etc) policy-owner-role policy-type-delegation-method (policy-owner-role, resource-owner, both) Then, every policy will always inform the person with the correct role, regardless of how it is setup in governance, as well as - if necessary, the individual resource owner.   In one case, we worked with Professional Services to build a policy that will identify owners as setup in rightscale tags and email them directly. That seems a great method to involve the owners of resources. We should move away from selecting individual email addresses for policy notification. ... View more

Self-Service - How to avoid CloudApps reaching a failed state if the operation that failed does not ...

by in Cloud Management Platform Forum
‎Nov 04, 2019 10:28 AM
4 Kudos
‎Nov 04, 2019 10:28 AM
4 Kudos
In Self-Service, using CAT code to run workflow during operations like stop, start, but also creating custom workflows for backups, etc., has been a real nice feature.  In my case, we execute specific tasks, such as shutting down a stack of applications, clean-up cache and/or take a backup. If any task or API call fails, it puts the CloudApp in a failed state, where an end-user is lacking privileges to see the "force to stopped/running".  Depending on what task failed, considering a lot of our users are responsible for their own application stack, (developers, technical support, etc.), we want them to be able to continue to operate the CloudApp without intervention.  I had been looking for a way to, in stead of failing (raise "condition") the CloudApp, to just put it back into a running state - while providing the user with the appropriate warning information. Although Self-Service does not have a method to abort an operation, it does offer a method to just run the start operation again. In my specific case, the start operation will check to see if the instance(s) are already operational - it will be a no-op at that point. ... else # prior step during shutdown operations failed $time = now() + 30 rs_ss.scheduled_actions.create( execution_id: @@execution.id, action: "start", first_occurrence: $time ) Besides the putting the app back in Running, based on the information returned from the prior steps, I assign a message to an output variable that is displayed in the Info tab for the CloudApp. I hope sharing this tidbit helps other people! ... View more

Re: How to View All Cases from Your Company

by in Using the Case Portal
‎Aug 16, 2019 03:04 PM
‎Aug 16, 2019 03:04 PM
I guess the article provides the answer, but from a support application, not the best usability. Who'd suspect that "My Cases" would include a filter for tickets entered by others. Better call it "All Cases".  ... View more

Re: Creating volumes in vscale slows down with the increase of volumes in that account/tenant

by in Cloud Management Platform Forum
‎Aug 14, 2019 01:11 PM
‎Aug 14, 2019 01:11 PM
Hi egonzales, Thanks for confirming this limitation. We are currently at 4.7k volumes in one account and we're experiencing daily deployment failures due to timeouts related to creation of new volumes. We're currently paying for PS to work around the issue, which is not really working, nor is it addressing the root cause.  Our business is not stagnant - we're expecting significant growth year over year. We'll be at 6k within a few months and at 8k in 24 months. The deployment architecture for RCA-V is one instance per data center. How are we supposed to scale this up? ... View more

Creating volumes in vscale slows down with the increase of volumes in that account/tenant

by in Cloud Management Platform Forum
‎Jul 26, 2019 11:52 AM
‎Jul 26, 2019 11:52 AM
Hi,  We're having problems with an account that has on average 4000-6000 disk volumes and we realize that creating new volumes is quite slow, timing out frequently, requiring a lot of orchestration to work around 240s API timeouts and wait limits. It appears that the API is not performing at scale. Are there any updates coming to resolve this? ... View more
Latest posts by averharen
View All ≫
Activity Feed
Contact Me
Online Status
Offline
Date Last Visited
‎Dec 03, 2021 04:54 PM
Kudos given to
View All ≫