[Spacewalk-list] Spacewalk-hostname-rename behavior

[Sander Kuusemets]

Hello!

Running spacewalk-hostname-rename on my spacewalk instance, I stumbled 
into a bizarre .. bug?

I'm using the internal postgres you get by installing the 
spacewalk-postgresql package before installing spacewalk itself, and 
upon running the command, the output is:

> [root at localhost ~]# spacewalk-hostname-rename ip
> Validating IP ... OK
> =============================================
> hostname: localhost
> ip: ip
> =============================================
> Stopping rhn-satellite services ... OK
> Testing DB connection ... FAILED
> Your database isn't running.
> Fix the problem and run /usr/bin/spacewalk-hostname-rename again

Which means that for some reason, this rename command first shuts down 
postgresql, and then tries to connect to it. I got around this by 
starting the postgres service just after it completed "Stopping 
rhn-satellite services", but I am wondering:

Is this the desired behavior?

Best regards,

-- 
Sander Kuusemets
University of Tartu, High Performance Computing, IT Specialist
Skype: sander.kuusemets1
+372 737 5694