Issues for projects hosted in Cloud-VPS (not: Toolforge which is toolforge.org).
Please check first if there is a sub-project, talkpage, or another dedicated place to file bug reports, so you will get the attention of their developers.
Note: Issues with the Cloud-VPS infrastructure itself should be filed under Cloud-VPS.
Closing this out since things have been ok with the new instances.
Change #1108428 had a related patch set uploaded (by Muehlenhoff; author: Muehlenhoff):
[operations/puppet@production] Remove obsolete puppetmaster::standalone role
Tested the full restore process on crm-dev-02. Adjusted the web proxy from community-crm to crm-dev-01 and tested basic functionality successfully. Powered off community-crm and puppetserver instances.
The new puppet 7 puppetserver is up and running. I have built and am testing crm-dev-02 with the new puppetserver and things appear to all be working as desired. Any issues we run across will be fixed forward and I hope to transition the current cloudvps crm test instance to crm-dev-02 in the next few hours assuming the data copies and restores go as planned. Once those are complete and verified, I'll power off the two older instances.
@MoritzMuehlenhoff At this point, the puppet5 puppet master is out of service or at least isn't doing any new updates. It will hopefully be powered down today.
What's the status, is the old puppet 5 puppet master already out of service?
I have now freed some disk space and the images work again. I think Susanna will be happy if there are instructions on how to receive email notifications when disk space is running out.
@TuukaH was recently active and created the only instance in that project
@Susannaanas try seeing if you can login to that portal and if you can grant me access to the project and ill see if i can help. I also asked in the telegram group if someone has access.
Cloud project is https://horizon.wikimedia.org/identity/wikidocumentaries/detail/
This was on the https://wikidocumentaries.wmcloud.org/wiki/Special:ListFiles page. I have not done anything myself, not flooded with media nor upgraded.
The HTML contains: Error creating thumbnail: Unable to save thumbnail to destination
@Andrew Thanks so much for that. I'm sure some of that was my doing or due to how my workflow was. I'll work through the changes and fix forward from here.
tofuinfratest is again failing to create Trove instances because of this. But this time there were also some Trove instances stuck in ERROR state.
Hello @Dwisehaupt -- I don't know how things got into this state but I have tried to sort things out a bit. I believe the puppetserver is now running.
The wikistream Cloud VPS project was deleted after migrating wikistream to Toolforge. See also T251555: wikistream.toolforge.org needs new maintainers.
Ok. I think I'm going to need some help at this point. I have gone back to the puppetserver (puppetserver-01.civicrm-prototype) I created a few months ago and am trying to do the full migration. I have verified the steps up to 6 above and all was going well.
The reservations table looks consistent:
The "reserved" column is inconsistent again, but this time it's ram and volumes that were not reset, instead of instances and volumes:
A few days after, the quotas were like this:
This is still happening on the new project tofuinfratest. I did reset the database quotas last week, following the instructions at Portal:Cloud_VPS/Admin/Trove#Reserved_quota_does_not_go_down.
Hi, sorry about this. I did make progress and then promptly got placed on a jury where I have been for the last month. I'll plan to look at this next week after I recover from triaging the rest of my backlog.
Ping.
Going to decline this as the owner of this VPS project. I use it to test schema changes for CheckUser. Because CheckUser stores private data, it means that access to the project allows access to this data. Therefore, I do not want to allow others to access this data unless I see them as trusted to hold it.
These cloudvirts were decom'd recently.
After some testing (and much distraction by other projects) we're going to upgrade to puppetserver 7 instead of trying to run off the stock puppetserver. I have created the volume, copied the data, and created the new VPS. Will wrap up the work tomorrow.