Bug #20340
closedUpdating puppet environment which is not associated with organization creates internal server error
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1471702
Description of problem: We were trying to update the puppet environment in particular organization. But when we attempt to update environment which is not associated with organization, it redirects to error page and shows error as
"something went wrong Validation failed: Name has already been taken"
and /var/log/foreman/production.log shows
"500 Internal Server Error"
Version-Release number of selected component (if applicable): sat 6.3 / Foreman nightly
How reproducible: always
Steps to Reproduce:
1. Create an organization
2. Navigate to Configure -> Environments
3. Click on import environment
4. Try to update environment which is not associated with particular organization
Actual results:
It will redirect to error page showing
"something went wrong Validation failed: Name has already been taken"
and produces
"500 Internal Server Error"
in log file.
Expected results:
Error should be handled without navigating to error page and without 500 internal server error.
Additional info:
I suppose we should handle errors more gracefully or maybe even not allowing to display envs that are out of scope for current user.
Updated by Marek Hulán over 7 years ago
- Subject changed from Updating puppet environment which is not associated with organization creates internal server error to Updating puppet environment which is not associated with organization creates internal server error
- Category changed from PuppetCA to Puppet integration
- Target version set to 115
Updated by Marek Hulán over 7 years ago
- Related to Bug #17463: Importing classes for a new org fails when the environment already exist in a different org added
Updated by Marek Hulán over 7 years ago
It seems that #17463 tried to fix it but I was able to reproduce with nigthly.
Updated by Ondřej Pražák almost 7 years ago
Updated by Tomer Brisker over 6 years ago
- Status changed from New to Resolved
marking as resolved per comment #4