Bug #32026: Saving invalid cloned role ends up with Internal server error - Foreman

Actions

Copy link

Bug #32026

closed

Saving invalid cloned role ends up with Internal server error

Added by Ondřej Ezr about 4 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ondřej Ezr

Category:

Users, Roles and Permissions

Target version:

Difficulty:

Triaged:

Yes

Bugzilla link:

1934427

Pull request:

https://github.com/theforeman/foreman/pull/8369

Fixed in Releases:

2.4.0

Found in Releases:

2.3.3

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1934427

Description of problem:

Error message displayed when cloning a role without supplying name:
Oops, we're sorry but something went wrong undefined method `id' for nil:NilClass

How reproducible:
always

Steps to Reproduce:
1. In Foreman UI: Administer > Roles
2. Pick a role, select Clone from the dropdown
3. Don't input any information in the form and click Submit

Actual results:
Red box with the aforementioned error

Expected results:
Information about the required field

Additional info:

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Ondřej Ezr about 4 years ago

Subject changed from Saving invalid cloned role ends up with 500. to Saving invalid cloned role ends up with Internal server error
Category set to Users, Roles and Permissions
Target version set to 2.4.1
Triaged changed from No to Yes