[katello-devel] Common FQDN problem with Signo

[Petr Chalupa]

Good to know, thanks.

I would disallow running katello-configure without FQDN if it does not 
work. It would be also useful to detect problems like these on 
signp/katello startup and log/show some warning notifications.

Logic behind this is that 5 days from now I'll forget about this and 
I'll will be looking for solution. If the problem is detected by 
application and it tells me what to fix than it'll save me possible 
hours of investigation.

This may be not applicable for this particular problem, but it's 
something to think about if a problem can be fixed in this way.

Petr

On 13.06.13 13:07, Marek Hulan wrote:
> Hello everyone
>
> Some of you already noticed, that having correctly set hostname on a machine
> is required before running katello-configure, otherwise Signo (and some other
> parts) won't work because of certificate issues. Certificates are generated
> during katello-configure so make sure your hostname is set correctly before.
>
> If you already have an installation where your FQDN was set to internal
> address or your FQDN was not configured properly you can use the script I put
> in katello-misc/scripts/regenerate-certificate.sh to generate new certificate.
> It will also restart all services.
>