Last modified: 2014-07-11 22:20:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67379, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 65379 - "The specified resource does not exist" when you try to configure an instance and are not a projectadmin
"The specified resource does not exist" when you try to configure an instance...
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-05-15 23:23 UTC by Matthew Flaschen
Modified: 2014-07-11 22:20 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Matthew Flaschen 2014-05-15 23:23:00 UTC 
I already had permissions to see the instance existed, so this doesn't do anything to increase security.  However, it also doesn't give the real reason I couldn't configure the instance, which is confusing.
Comment 1 Matthew Flaschen 2014-07-11 17:50:34 UTC 
Testing with bastion (since I'm not a projectadmin, and it has instances), I can't see the list at https://wikitech.wikimedia.org/wiki/Special:NovaInstance (it appears blank).

However, I can at https://wikitech.wikimedia.org/wiki/Nova_Resource:Bastion under "Instances for this project".

The list is SemanticMediaWiki-generated, I think, since it's not in the wikitext.
Comment 2 Andrew Bogott 2014-07-11 22:20:01 UTC 
I've investigated this some -- it turns out that with the default nova policy, if you aren't a project admin you're not allowed to query an instance at all.  So, when it tries to look up what project the instance is in, it can't find the instance, hence, no such resource.

I'm going to see if its possible to adjust the nova policy so that we can see but not change instances.  It's not entirely obvious how to do this though.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links