Bug #15535
closed
"rudder server trigger-policy-generation/reload-groups" output a curl error if apache is stopped
Added by Nicolas CHARLES over 5 years ago.
Updated almost 5 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
# systemctl stop apache2
# rudder server trigger-policy-generation
curl: (7) Failed to connect to 127.0.0.1 port 443: Connection refused
Web interface is down - requested a policy generation at its restart
this is clearly suboptimal
- Target version changed from 5.0.13 to 5.0.14
- Target version changed from 5.0.14 to 5.0.15
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Small
- Priority changed from 0 to 47
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/270
- Status changed from Pending technical review to Pending release
- Subject changed from rudder server trigger-policy-generation/reload-groups, etc outputs curl error if apache2 is stopped to "rudder server trigger-policy-generation/reload-groups" output a curl error if apache is stopped
- Name check changed from To do to Reviewed
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
- Priority changed from 47 to 46
This bug has been fixed in Rudder 5.0.15 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by