[00:07:59] !log admin rebooting cloudcontrol1006 to recover from full disk error [00:08:04] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [09:17:50] hello everyone, I'm trying to login to bastion after a while; I uploaded my new public ssh key and tried to login with command ssh epantaleo@bastion-eqiad1-03.etytree.wikimedia.cloud (after creating a config file) where I set my instance equal to  bastion-eqiad1-03 because I think this is my new instance (it used to be etytree-a or etytree-b. [09:18:28] after entering my passphrase I get: "channel 0: open failed: connect failed: Name or service not known [09:18:28] stdio forwarding failed [09:18:29] kex_exchange_identification: Connection closed by remote host [09:18:29] Connection closed by UNKNOWN port 65535" [09:19:11] anyone can help me login into the instances in my etytree project? [09:36:20] !help [09:36:20] If you don't get a response in 15-30 minutes, please create a phabricator task -- https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=wmcs-kanban [09:40:44] Epantaleo: there's only one instance in the project etytree, named etytree-a (https://openstack-browser.toolforge.org/project/etytree), did you try sshing to it? (`ssh etytree-a.etytree.eqiad1.wikimedia.cloud`) (looking myself in parallel) [09:41:02] I see [09:41:04] will try now [09:42:09] it's turned off though [09:42:41] Epantaleo: https://sal.toolforge.org/log/li9AvIYBxE1_1c7svpUy [09:44:29] I see but I had a mail exchange with Aklapper: I didnt flag my project as in use because I couldnt login (change my computer and my phone) [09:44:35] and with fixed it together [09:44:46] I flagged it correctly [09:45:03] what should I do? [09:46:20] nice, okok, so you can now login into horizon.wikimedia.org? [09:46:31] https://phabricator.wikimedia.org/T151762 [09:46:33] yes [09:46:46] awesome, so all that's needed should be to turn on the VM from there [09:47:02] (I can do it myself, but better if you make sure you have access) [09:47:09] ok [09:47:17] can you remind me what I should do? [09:47:23] sure [09:47:27] thanks! [09:47:30] go to https://horizon.wikimedia.org/project/instances/ [09:47:52] make sure that on the upper left selector you choose etytree project [09:48:10] https://usercontent.irccloud-cdn.com/file/7EyMjgGZ/image.png [09:48:52] you should see then the list of instances (only one there), and a 'Start instance' button on the right side [09:49:27] I think I have done it, thanks [09:49:35] I have another question now [09:49:36] ... [09:49:46] awesome [09:54:24] My tool is based on Virtuoso and since the OS was updated to buster I couldn't install it on the VM. I just figured out maybe I can use Virtuoso's docker. But I am not an engineer, so I am not sure this will work. So my first question is: should I use Buster or there is a more recent OS? and my second question is: do you think I can build [09:54:25] Virtuoso's docker with docker pull openlink/virtuoso-opensource-7:7.2.11 and then the build? I would also need to install maven [09:55:04] (the reason why the tool is off is the OS upgrade and software incompatibilities and I just found some time to try and fix it= [09:55:06] ) [09:57:23] "should I use Buster or there is a more recent OS?" There's now a newer version yes, you can create a new VM, and get the latest image available (I think it's debian 12) [09:59:04] I'm not familiar with virtuoso, but you should be able to use the docker image yes, you might have to mount volumes and such for it to access your code [09:59:27] if you are able to use the docker image locally, you should be able to use it in the VM also [10:00:29] ok thanks you will try [10:02:22] feel free to ask for help :), I know docker, but not virtuoso, but can try helping (create a task if there's nobody around, most of us are in a 'team offsite') [10:04:45] great. however I can see now that the tool is up and working on buster [10:04:55] maybe i don't need to figure that out... [10:11:45] I recommend starting to look it up though, debian buster will go end support sooner than later (in 6 months), having it in a docker container will help migrating too to newer versions. No rush though, but better doing it bit by bit than in a rush when the support is over [10:13:03] makes sense [10:13:04] thanks [10:25:37] !log tf-infra-test added tf-infra-test VM to the default security group so we stop getting alerts for instance down (and get prometheus metrics out of it) [10:25:40] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tf-infra-test/SAL [10:48:14] !log wikiwho `samtar@wikiwho01:~$ sudo systemctl restart ww_celery.service` T351172 [10:48:18] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikiwho/SAL [10:48:19] T351172: WikiWho is down - https://phabricator.wikimedia.org/T351172 [15:16:03] !log quarry re-enable puppet that has been too long disabled (T348748) [15:16:08] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Quarry/SAL [15:16:08] T348748: Remove gerrit git from quarry puppet - https://phabricator.wikimedia.org/T348748