Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails Initializing Rally when performed more than once in an application #152

Open
jonvadney opened this issue Jul 7, 2019 · 4 comments

Comments

@jonvadney
Copy link

python 3.6
pyral 1.4.2

In a flask application I'm connecting to Rally on every user connection, on the second request I'm always getting the following error.

"pyral.context.RallyRESTAPIError: The current Workspace does not contain an accessible Project with the name of None"

I tracked down the cause to pyral/entity.py::getEntityName(candidate).

The function is returning PortfolioItem/Project instead of Project on the second invocation of that method which is resulting in portfolio items being returned instead of projects.

@klehman-rally
Copy link
Member

In your subscription, do you have any custom PortfolioItem sub-types in any workspace?

Do you have any code you would be comfortable sharing that would allow me to reproduce the error you observed?

@jonvadney
Copy link
Author

It's possible there are custom portfolio, the team tried them out a couple years ago, but stopped using them and didn't clean anything up. The types are set to Project, Feature, and Stage.

I'll try to get a sample, representative project, I can share soon.

@klehman-rally
Copy link
Member

It is currently problematic in pyral to have a custom PortfolioItem sub-type named the same as a standard Rally WSAPI model entity, ie., a Project is a standard Rally entity, a custom PortfolioItem sub-type named 'Project' will have conflicts that are currently unresolved.
If you can provide some sample code, I'd like to determine if this is the root of the problem you've observed.

@jonvadney
Copy link
Author

rally_sample.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants