Sure, i will give further infomation tomorrow or on Monday. (No testsetup at home)<br><br><div class="gmail_quote">2009/7/30 Iustin Pop <span dir="ltr"><<a href="mailto:iusty@k1024.org">iusty@k1024.org</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Thu, Jul 30, 2009 at 04:27:14PM +0200, Maximilian Mill wrote:<br>
> Package: ganeti2<br>
> Version: 2.0.1-2<br>
> Severity: grave<br>
> Justification: renders package unusable<br>
><br>
> Hello,<br>
<br>
Hi and thanks for the report.<br>
<br>
> it looks like 'gnt-cluster init --vg-name=vg0 <a href="http://cluster.xyz.com" target="_blank">cluster.xyz.com</a>' doesn't create<br>
> all needed files for the cluster to work. ll /var/lib/ganeti:<br>
> insgesamt 20<br>
> -rw------- 1 root root 2422 30. Jul 13:29 config.data<br>
> -rw------- 1 root root 416 30. Jul 13:29 known_hosts<br>
> drwx------ 3 root root 4096 30. Jul 13:30 queue/<br>
> -r-------- 1 root root 1880 30. Jul 13:29 rapi.pem<br>
> -r-------- 1 root root 1880 30. Jul 13:29 server.pem<br>
> -rwxr-xr-x 1 root root 0 30. Jul 13:30 watcher.data*<br>
<br>
This means that the initial part of the init worked, but ganeti-masterd<br>
didn't start correctly.<br>
<br>
> I found this problem when i was trying to add a node. This error message comes:<br>
> gnt-node add anc<br>
> Corrupt configuration file: Can't read from the ssconf file: '[Errno 2] No<br>
> such file or directory: '/var/lib/ganeti/ssconf_master_node''<br>
> Aborting.<br>
><br>
> I have this bug with 2.0.1-2 from unstable on a lenny maschine(bpo'ed).<br>
><br>
> I did a repack with the new upstream 2.0.2-1 and everything works like it<br>
> should.<br>
> Now gnt-cluster init created these files in /var/lib/ganeti and everything works:<br>
> insgesamt 56<br>
> -rw------- 1 root root 2422 30. Jul 13:32 config.data<br>
> -rw------- 1 root root 416 30. Jul 13:32 known_hosts<br>
> drwx------ 3 root root 4096 30. Jul 13:32 queue/<br>
> -r-------- 1 root root 1880 30. Jul 13:32 rapi.pem<br>
> -r-------- 1 root root 1880 30. Jul 13:32 server.pem<br>
> -r--r--r-- 1 root root 35 30. Jul 13:32 ssconf_cluster_name<br>
> -r--r--r-- 1 root root 0 30. Jul 13:32 ssconf_cluster_tags<br>
> -r--r--r-- 1 root root 25 30. Jul 13:32 ssconf_file_storage_dir<br>
> -r--r--r-- 1 root root 0 30. Jul 13:32 ssconf_instance_list<br>
> -r--r--r-- 1 root root 40 30. Jul 13:32 ssconf_master_candidates<br>
> -r--r--r-- 1 root root 15 30. Jul 13:32 ssconf_master_ip<br>
> -r--r--r-- 1 root root 8 30. Jul 13:32 ssconf_master_netdev<br>
> -r--r--r-- 1 root root 40 30. Jul 13:32 ssconf_master_node<br>
> -r--r--r-- 1 root root 40 30. Jul 13:32 ssconf_node_list<br>
> -r--r--r-- 1 root root 0 30. Jul 13:32 ssconf_offline_nodes<br>
> -r--r--r-- 1 root root 40 30. Jul 13:32 ssconf_online_nodes<br>
> -r--r--r-- 1 root root 6 30. Jul 13:32 ssconf_release_version<br>
<br>
It is strange that 2.0.1 is broken and 2.0.2 works, since there have<br>
been no fixes between 2.0.1 and 2.0.2 in regard to cluster init.<br>
<br>
Are you sure this is not a problem of the backport somehow? The failed<br>
cluster init should have left some error detals in the logs<br>
(/var/log/ganeti/*), can you check that out and give the errors details?<br>
<br>
thanks!<br>
<font color="#888888">iustin<br>
</font></blockquote></div><br>