GOsa bug report: Empty boot kernel dropdown when no supported options for current release

[mbenkmann]

From matthias...@gmail.com on March 16, 2013 17:54:43

If go-susi reports no supported boot kernels for the release currently selected, then the kernel dropdown is empty in GOsa. Instead GOsa should always included the current option and if that is not part of the supported list it should print a text next to it like "(not on this server)". This is similar to how FAI classes are handled that are currently listed in a system's faiclass attribute even though the si-server says they are not part of the release.

Original issue: http://code.google.com/p/go-susi/issues/detail?id=89

[mbenkmann]

From matthias...@gmail.com on March 17, 2013 03:25:11

The bug is more general and does not require go-susi to trigger. To reproduce:

1. Set up server A so that it has ONLY release "plophos" in its repository
2. Set up server B so that it has ONLY release "tramp" in its repository
3. In GOsa on server A edit a client object on server A and select any boot kernel OTHER THAN "default"
4. Save the client object and then open it in the GOsa on server B. The boot kernel information has been lost. It has changed to "default". Saving the object destroys the boot kernel information without telling the user.

[mbenkmann]

From matthias...@gmail.com on March 17, 2013 03:36:37

While fixing this bug, change GOsa to always add a "default" option if there is none.

[mbenkmann]

From matthias...@gmail.com on March 17, 2013 04:17:47

The attached patch fixes the issue. It's a bit ugly because the text "[not available in current setup]" is written into the dropdown. It would be nicer if it were printed in red next to the dropdown. But that's just a cosmetic issue.

Attachment: gosa-fix-gotoBootKernel-lost-if-server-does-not-have-that-kernel.patch

[mbenkmann]

From mux2...@gmail.com on March 19, 2013 09:23:18

TRAC ticket #10294

Status: Done