-
Bug
-
Resolution: Done
-
Minor
-
7.8.0.GA
-
None
-
Release Notes
-
-
-
-
-
-
CR1
-
When using Githooks in Business Central, both known_hosts and id_rsa files must be provided. Otherwise, Business Central pod won't start.
-
-
2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9)
When the known_hosts file is missing from the githook secret, the Business Central pod remains stuck at "Container Creating" status and we can't easily see why (no errors or events).
The expected behaviour would be to let users know why the pod can't start (via errors or events) or set the pod at Error because the known_hosts file is missing.
This is working fine whether the known_host file is provided:
oc create secret generic githook-ssh-key-secret --from-file=id_rsa=test_manual/.ssh/id_rsa --from-file=known_hosts=test_manual/.ssh/known_hosts
- is caused by
-
RHPAM-2996 Operator and Operator Console do not provide a way to configure SSH private key for Git hooks
- Closed