-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding sonar major version 4.16 #424
base: dev
Are you sure you want to change the base?
Conversation
Hi Linda, 5 Checks failed above and I see following error: Please share the access instructions for a live system so that I can pass on to respective team to look into this error. |
Hi Jagdeep, the ssh keys of the environment are added to the github action as "Artifact", you can see then if you scroll down the action main page. By default, when an action runs, whether successful or failed, the resources are destroyed. To keep the resources for an investigation, you can use the "delay destroy" feature when you run the action manually. |
Hi Linda - I was able to find the SSH key from Sonar machine from "Artifacts" section on Github actions page. and I successfully manually triggered the github actions with "delay destroy" option. But, I am facing issue while finding the public ip of host servers. I think I need to go through jumphost. Please share the jumphost information so that we can ssh to those servers. |
Hi Jagdeep, you are right, when the machine is not publicly accessible, you have to go via a jump server. Usually, depending on the terraform example/recipe, the Hub is accessible directly and the gateways are accessible via a jump server which is the Hub. Now, you don't need to build the ssh command yourself, we generate it and we take into account whether there is a jump server or not. You can see in the terraform output, for each machine, what is the ssh command to reach it. You can find the terraform output in one of the steps in the github action output. |
HI Linda. thanks for the information. I checked terraform output and i think i found the ssh command. I will try sshing with it. |
Sure |
Hi Team.. while pushing changes for adding major 4.16 version, github actions is failing. to debug, i re-ran the workflow manually with delay destroy. now i need to ssh to the created DR machine. i have the ssh key and ssh command. but i am getting following error: ➜ ~ ssh -i ssh_keys/dsf_ssh_key-dsf_cli-sonar-132-1- [email protected] manual run link: https://github.com/imperva/dsfkit/actions/runs/9811668509 what might be the issue here? |
HI Linda, workflow run: https://github.com/imperva/dsfkit/actions/runs/10376028524 i tried within the 30 min window. but still getting operation timeout for hub_dr and hub_main. my branch has the latest ssh_cidr code as well to allow vancouver traffic: can we get on a call to sort this out? or can you try manually running and then sshing into hub_dr machine? need to know if i am missing something. |
Hi Jagdeep, I just started a manual run with a destroy delay. I will let you know. We can have a call if needed. |
HI Linda, my ip doesn't fall under above mentioned 2 ranges. Correct CIDRs for our location are mentioned below: Please add these to the ALLOWED_SSH_CIDRS secret in Github. |
aac0cbc
to
5d8154a
Compare
Hi Jagdeep, I have added CIDRs of GP-Canada-West and GP-US-North-West to ALLOWED_SSH_CIDRS secret. |
HI Linda, |
shared replication.log with David. |
Any updates with that? |
4.16.0.10.0 has issues with replication. we are waiting for 4.16.0.20.0 which has fixes. it is currently in QA testing. |
No description provided.