Bug 705876 - luci chokes on working cluster.conf line
Summary: luci chokes on working cluster.conf line
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: luci
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ryan McCabe
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 18:44 UTC by joshua
Modified: 2012-08-16 15:21 UTC (History)
4 users (show)

Fixed In Version:
Clone Of: 705884
Environment:
Last Closed: 2012-08-16 15:21:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
luci error log (10.93 KB, text/plain)
2011-05-18 18:44 UTC, joshua
no flags Details

Description joshua 2011-05-18 18:44:39 UTC
Created attachment 499664 [details]
luci error log

Description of problem:

I have a cluster that works perfectly fine, then I add this line which also works per the cluster, but on which luci chokes

vm autostart="1" exclusive="1" migrate="pause" name="Tally-On-Premise_2011.1" path="/data/cluster-storage/tally" recovery="relocate" snapshot="/data/cluster-storage/rally" use_virsh="1"/>

I get on another machine, install luci, import the cluster, and luci in my web browser still shows the same error:

Error 500

We're sorry but we weren't able to process this request.



Per the /var/log/luci/luci.log, luci is very unhappy (see attached log).


Version-Release number of selected component (if applicable):

luci-0.24.0-2.fc14.x86_64


Expected Results:

Shouldn't luci be able to parse this line?  If not, surely it could have a more intelligent response than the error above.

Comment 1 Jan Pokorný [poki] 2012-03-12 16:20:47 UTC
This is duplicate of bug 705884:  entities, namely services, matching
the "name + '.' + known extension" pattern would cause issues when
entity specific page is requested -- the framework would strip this
extension (".1" in this particular case) resulting in query for
non-existent entity unless taught not to do so.

Fix will be in upcoming release.

Comment 2 Fedora End Of Life 2012-08-16 15:21:16 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.