adding sonar major version 4.16

[jagdeep-sonar]

No description provided.

[jagdeep-sonar]

Hi Linda,

5 Checks failed above and I see following error:
module.hub_hadr[0].null_resource.exec_replication_cycle_on_dr (remote-exec): The exception was: "Replication script exited with code 1, full error: {'ok': 0.0, 'errmsg': 'Replication script exited with code 1', 'code': 151}"

Please share the access instructions for a live system so that I can pass on to respective team to look into this error.

[lindanasredin]

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.

[jagdeep-sonar]

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.

[lindanasredin]

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.

[jagdeep-sonar]

HI Linda. thanks for the information. I checked terraform output and i think i found the ssh command. I will try sshing with it.

[lindanasredin]

Sure

[jagdeep-sonar]

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]
ssh: connect to host ec2-13-41-252-225.eu-west-2.compute.amazonaws.com port 22: Operation timed out

manual run link: https://github.com/imperva/dsfkit/actions/runs/9811668509

what might be the issue here?

[lindanasredin]

Hi Jagdeep, I have added CIDRs of GP-Canada-West and GP-US-North-West to ALLOWED_SSH_CIDRS secret.

[jagdeep-sonar]

HI Linda,
Thanks for adding the new CIDRs. it works. i am able to SSH into machines.
Shared audit.log with David. will also fetch replication.log and share.

[jagdeep-sonar]

shared replication.log with David.

[eytannnaim]

shared replication.log with David.

Any updates with that?

[jagdeep-sonar]

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.

[jagdeep-sonar]

4.16.0.10.0 had issues with replication. so it is not be used anymore. Replacing 4.16 major version with 4.16.0.20.0.
PR for dsfkit_backend: https://github.com/imperva/dsfkit_backend/pull/43

[jsonar-cpapke]

@eytannnaim are we able to get approval on this PR?