Actions
Bug #4075
closedThe rudder vhost changes make some rudder-upgrade steps unnecessary
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The rudder vhost changes make some rudder-upgrade steps unnecessary/broken. (vhost migration)
Updated by Matthieu CERDA about 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/160
PR available
Updated by Matthieu CERDA about 11 years ago
The changes introduced in #3878 broke rudder-upgrade by replacing completely the existing vhost by a brand new one.
Updated by Matthieu CERDA about 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset packages:commit:e1bf75b6b06912805449e0daf9846fae826db5ff.
Updated by Matthieu CERDA about 11 years ago
Applied in changeset packages:commit:1d74e956c07f365259b81eba5de84559f1c6934a.
Updated by Vincent MEMBRÉ about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~beta1, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-October/000056.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: http://www.rudder-project.org/foswiki/Download/
Actions