I think your commit 85081d50ccd26aec9b43357515ae11826a72fb9f causes this problem, in this commit, you added the description for "consoleservice", however, the line is ended with a comma(should be a period), caused the lines after this line are considered as a new hash entry and ignored.
I understand that why this check was not in 2.10, with the current situation, I think we will use the conserver as the default console service in 2.10 also, do you think we need to put these changes into 2.10 also?
[ligc@ligc-1xCAT]$gitshow85081d50ccd26aec9b43357515ae11826a72fb9fcommit85081d50ccd26aec9b43357515ae11826a72fb9fAuthor:VictorHu<vhu@us.ibm.com>Date:WedFeb415:36:302015-0500Addnewservicerelatedkeywordintositetable:consoleservice[DevopsTask10075]Thebehaviorchangesbetween2.9.1and2.10.Thekeywordisprovidedforthoseuserswhowanttotryoutconfluentinthe2.9.1timeframe.Confluentisplannedtobepackagedbetterandthedefaultconsolefor2.10.conserverwillstillbeshippedtoprovideconsoleforthesystemsnotsupportedbyconfluent.diff--gita/perl-xCAT/xCAT/Schema.pmb/perl-xCAT/xCAT/Schema.pmindexa41d427..84e3c31100755---a/perl-xCAT/xCAT/Schema.pm+++b/perl-xCAT/xCAT/Schema.pm@@-1129,6+1129,7@@site=>{" consoleondemand: When set to 'yes', conserver connects and creates the console\n"." output only when the user opens the console. Default is no on\n"." Linux, yes on AIX.\n\n".+" consoleservice: The console service to be used by xCAT. Default is conserver\n\n"," httpport: The port number that the booting/installing nodes should contact the\n"." http server on the MN/SN on. It is your responsibility to configure\n"." the http server to listen on that port - xCAT will not do that.\n\n".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
HI Victor,
I think your commit 85081d50ccd26aec9b43357515ae11826a72fb9f causes this problem, in this commit, you added the description for "consoleservice", however, the line is ended with a comma(should be a period), caused the lines after this line are considered as a new hash entry and ignored.
I understand that why this check was not in 2.10, with the current situation, I think we will use the conserver as the default console service in 2.10 also, do you think we need to put these changes into 2.10 also?
sorry about that. I will fix it.
If we commit this to 2.10 also, on the upgrade path, how do we change the default value if configured to conserver?
070e5a9..1fd513d 2.9 -> 2.9