Replies: 4 comments
-
Hello, I am working on reproducing the issue, created a ticket, CFE-4469, and if I can reproduce it look into a fix. Also saw your other issue and will look into that after this one. Thanks for the report! |
Beta Was this translation helpful? Give feedback.
-
I am not able to reproduce this initially. I set the hostname with
oddly, if I try a similar command after successful install I get your error and I agree that your error is "valid" and that if the hostname is longer than the limit of 64 characters we need to do something different during the install. Leaving out the key that is no longer there:
And after much ascii art during generation I get the error:
|
Beta Was this translation helpful? Give feedback.
-
Can I assume that if you run
I will try this and can likely provide a test package for you to check. |
Beta Was this translation helpful? Give feedback.
-
I didn't have a chance to test this build/package yet, but maybe you can try: https://github.com/cfengine/buildscripts/actions/runs/12244892565/artifacts/2296556865 |
Beta Was this translation helpful? Give feedback.
-
Initially the issue was noticed during latest LTS installation in Azure.
How to reproduce: create a VM in Azure with name
poc-cfengine-test
and try to install hub using cf-remote as the followingLogs:
Workaround: rename the host to
hub
(hostnamectl hostname hub
or, initially, name the VM like this)Beta Was this translation helpful? Give feedback.
All reactions