-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.403+
-
-
2.435. 2.426.3
Regression identified during testing of the ec2-plugin on Jenkins 2.403+.
When the clouds management page was reworked, submitting a config change to the cloud node does not return the top of the cloud page. Instead it returns to the cloud node page. This is not a problem if the name has not been changed. However, once the name has been changed, the cloud node page is now invalid and user is greeted with a 404.
Reproduction steps:
- Go to manage jenkins -> clouds
- Create a new cloud node and save
- Select config for the new cloud node
- update the name and click save
- is duplicated by
-
JENKINS-72214 Renaming a cloud leads to a 404
-
- Closed
-
- links to
[JENKINS-71737] Bad redirect when cloud node name is changed
Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/8310 (Web Link)" [ 28875 ] |
Assignee | New: Carroll Chiou [ carroll ] |
Link |
New:
This issue is duplicated by |
Released As | New: 2.435 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Remote Link | New: This issue links to "jenkinsci/jenkins#8505 (Web Link)" [ 29203 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Labels | Original: lts-candidate | New: 2.426.3-fixed lts-candidate |
Labels | Original: 2.426.3-fixed lts-candidate | New: 2.426.3-fixed |
Released As | Original: 2.435 | New: 2.435. 2.426.3 |