a-palchikov

Seems like tcp port `61009` is already reserved, can you check what it is reserved for? ``` $ semanage port -l | grep 61009 ```

Can you share the audit log for the specific failure? It is definitely distribution version-specific and the gravity's policy has not been updated in awhile.

It looks like the planet rootfs directory was not labeled properly as these transitions show. The planet binary needs to be labeled `gravity_container_runtime_exec_t` and not `container_file_t`. I'll have to repro...

If the whole `rootfs` directory is not labelled properly, then various binaries will fail at random places. I will try to reproduce this once I get a chance and will...

@Ahmadabed83 This can be achieved with [tls key pair resource](https://goteleport.com/gravity/docs/config/#tls-key-pair) - does this work for your use-case?

Do you set the [deadline](https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup) for your install hook? If not, it defaults to [20min](https://github.com/gravitational/gravity/blob/7.0.12/lib/defaults/defaults.go#L151) - has the job been running for that long?

It means the hook job ran longer than that. Can you check the `/var/log/gravity-install.log` for any hints about why the job took that longer (and possible would've run longer)? The...

Sorry - I should've looked at the original description. Yes, it looks like the install hook is not logging enough to see where it's stuck at times when this fails...

- [x] extended debug logging (incl. gRPC logs) - [x] add expiration to controller reconnect loop - [x] verify that `plan complete` command works for hung join operations from master...

Partially yes - once the changes are forward-ported to 6.2.x.