'Environment' did not survive a reboot for a gateway on which I applied a JHF - is this expected?

[eth4_]

Recently applied a JHF to the stand by member of a cluster (R81.20).  I was startled I didn't see telemetry coming in after enough time had passed for the reboot so I check the environment drop down and found 'Default' there - along with the missing gateway.  Is there a way to make the setting survive a reboot?

[Chris_Atkinson]

Could you please share additional specifics of the JHF used before & after etc?

Possibly this is one of those things more readily worked through with TAC via a remote session...

[Ruan_Kotze · Accepted solution]

Have experienced the same issue accross a couple of environments, but it seem random.  Fix is always the same (do the below on the appliances not checking in):

1. Recreate payload-no-tls.json
2. Run "/opt/CPotelcol/REST.py --set_open_telemetry "$(cat payload-no-tls.json)"

Thanks,
Ruan

[the_rock]

I can confirm 100% what @Ruan_Kotze said is indeed true. I had CP esc. guy send the same via case last year for this issue.

Best,

Andy