Bug #3063: Apache 2 HTTP Server: No reporting on whether Apache 2 was started or not - Rudder - Issue Tracker

Actions

Copy link

Bug #3063

closed

Apache 2 HTTP Server: No reporting on whether Apache 2 was started or not

Added by Nicolas CHARLES over 11 years ago. Updated almost 8 years ago.

Status:

Rejected

Priority:

Assignee:

Nicolas CHARLES

Category:

Techniques

Target version:

2.11.21

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

There is currently no reports on the Apache technique to know if Apache2 was started as expected or not, and if it was restarted or not

We need a new component to resolve that

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES over 11 years ago

Status changed from In progress to Pending technical review
Assignee changed from Nicolas CHARLES to Jonathan CLARKE

The pull request is here
https://github.com/Normation/rudder-techniques/pull/10

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

Status changed from Pending technical review to Discussion
Assignee changed from Jonathan CLARKE to Nicolas CHARLES

Nicolas CHARLES wrote:

The pull request is here
https://github.com/Normation/rudder-techniques/pull/10

I'm bothered by this pull request because it introduces another change, which isn't just reporting: it changes the conditions for what "autostart" means. Do we start Apache immediately, or do we configure it to be started at boot? These are two separate settings.

If reporting needs fixing, please go ahead and make a pull request just for that, I will happily validate it.

However, this behaviour should not be changed without a clear warning, a Technique version change, and a clarification in the Technique's metadata. Maybe it is wrong in the first place? In this case, a bug should be filed against this problem - but it is clearly not a reporting bug as stated here.

Actions

Copy link

Updated by Nicolas CHARLES over 11 years ago

I can't fix the reporting without clarification on what should be done (or not done) if the service is started (or not), otherwise there are corner case when action are done without reporting, or not actin, but no reporting either

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

Nicolas CHARLES wrote:

I can't fix the reporting without clarification on what should be done (or not done) if the service is started (or not), otherwise there are corner case when action are done without reporting, or not actin, but no reporting either

What should be done:

If the settings in a Directive request to set Apache to start on boot, it should be set to start on boot only, not necessarily started immediately.
If the settings in a Directive request to start/restart Apache after changing it's configuration, then this should be done immediately, regardless of the "start on boot" setting

Does anything else need clarifying?

Actions

Copy link

Updated by Nicolas CHARLES over 11 years ago

Assignee changed from Nicolas CHARLES to Jonathan CLARKE

Jonathan CLARKE wrote:

Nicolas CHARLES wrote:

I can't fix the reporting without clarification on what should be done (or not done) if the service is started (or not), otherwise there are corner case when action are done without reporting, or not actin, but no reporting either

What should be done:

If the settings in a Directive request to set Apache to start on boot, it should be set to start on boot only, not necessarily started immediately.

If the settings in a Directive request to start/restart Apache after changing it's configuration, then this should be done immediately, regardless of the "start on boot" setting

Does anything else need clarifying?

There is no setting in the PT/Technique to start/restart Apache after changing it's configuration; so I'm not sure I understand your explanation

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

Nicolas CHARLES wrote:

Jonathan CLARKE wrote:

Nicolas CHARLES wrote:

I can't fix the reporting without clarification on what should be done (or not done) if the service is started (or not), otherwise there are corner case when action are done without reporting, or not actin, but no reporting either

What should be done:

If the settings in a Directive request to set Apache to start on boot, it should be set to start on boot only, not necessarily started immediately.

If the settings in a Directive request to start/restart Apache after changing it's configuration, then this should be done immediately, regardless of the "start on boot" setting

Does anything else need clarifying?

There is no setting in the PT/Technique to start/restart Apache after changing it's configuration; so I'm not sure I understand your explanation

I guess we should add one then.

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

Assignee changed from Jonathan CLARKE to Nicolas CHARLES

Actions

Copy link

Updated by Matthieu CERDA about 11 years ago

Target version changed from 2.3.10 to 2.3.11

Actions

Copy link

Updated by Jonathan CLARKE about 11 years ago

Project changed from Rudder to 24
Category deleted (~~Techniques~~)

Actions

Copy link

#10

Updated by Nicolas CHARLES about 11 years ago

Jonathan CLARKE wrote:

Nicolas CHARLES wrote:

Jonathan CLARKE wrote:

Nicolas CHARLES wrote:

I can't fix the reporting without clarification on what should be done (or not done) if the service is started (or not), otherwise there are corner case when action are done without reporting, or not actin, but no reporting either

What should be done:

If the settings in a Directive request to set Apache to start on boot, it should be set to start on boot only, not necessarily started immediately.

If the settings in a Directive request to start/restart Apache after changing it's configuration, then this should be done immediately, regardless of the "start on boot" setting

Does anything else need clarifying?

There is no setting in the PT/Technique to start/restart Apache after changing it's configuration; so I'm not sure I understand your explanation

I guess we should add one then.

So, it would be a new revision of the technique.
What about this one ?

Actions

Copy link

#11

Updated by Nicolas CHARLES about 11 years ago

Assignee changed from Nicolas CHARLES to Jonathan CLARKE

Actions

Copy link

#12

Updated by Matthieu CERDA about 11 years ago

Target version changed from 2.3.11 to 2.3.12

Actions

Copy link

#13

Updated by Matthieu CERDA almost 11 years ago

Target version changed from 2.3.12 to 2.3.13

Actions

Copy link

#14

Updated by Nicolas PERRON almost 11 years ago

Target version changed from 2.3.13 to 84

Actions

Copy link

#15

Updated by Nicolas PERRON almost 11 years ago

Target version changed from 84 to 2.4.7

Actions

Copy link

#16

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.7 to 2.4.8

Actions

Copy link

#17

Updated by Jonathan CLARKE over 10 years ago

Assignee changed from Jonathan CLARKE to Nicolas CHARLES

Nicolas CHARLES wrote:

Jonathan CLARKE wrote:

Nicolas CHARLES wrote:

Jonathan CLARKE wrote:

Nicolas CHARLES wrote:

I can't fix the reporting without clarification on what should be done (or not done) if the service is started (or not), otherwise there are corner case when action are done without reporting, or not actin, but no reporting either

What should be done:

If the settings in a Directive request to set Apache to start on boot, it should be set to start on boot only, not necessarily started immediately.

If the settings in a Directive request to start/restart Apache after changing it's configuration, then this should be done immediately, regardless of the "start on boot" setting

Does anything else need clarifying?

There is no setting in the PT/Technique to start/restart Apache after changing it's configuration; so I'm not sure I understand your explanation

I guess we should add one then.

So, it would be a new revision of the technique.
What about this one ?

Sounds like the best approach, yes.

Actions

Copy link

#18

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.8 to 2.4.9

Actions

Copy link

#19

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.9 to 2.4.10

Actions

Copy link

#20

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.10 to 2.4.11

Actions

Copy link

#21

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.11 to 2.4.12

Actions

Copy link

#22

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.4.12 to 2.4.13

Actions

Copy link

#23

Updated by Vincent MEMBRÉ about 10 years ago

Target version changed from 2.4.13 to 2.6.11

Since Support for 2.4 branch is over, retargeting this issue to 2.6

Actions

Copy link

#24

Updated by Vincent MEMBRÉ about 10 years ago

Target version changed from 2.6.11 to 2.6.12

Actions

Copy link

#25

Updated by Vincent MEMBRÉ about 10 years ago

Target version changed from 2.6.12 to 2.6.13

Actions

Copy link

#26

Updated by Vincent MEMBRÉ almost 10 years ago

Target version changed from 2.6.13 to 2.6.14

Actions

Copy link

#27

Updated by Jonathan CLARKE almost 10 years ago

Target version changed from 2.6.14 to 2.6.16

Actions

Copy link

#28

Updated by Jonathan CLARKE almost 10 years ago

Target version changed from 2.6.16 to 2.6.17

Actions

Copy link

#29

Updated by Nicolas PERRON over 9 years ago

Target version changed from 2.6.17 to 2.6.18

Actions

Copy link

#30

Updated by Matthieu CERDA over 9 years ago

Target version changed from 2.6.18 to 2.6.19

Actions

Copy link

#31

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.6.19 to 2.6.20

Actions

Copy link

#32

Updated by François ARMAND about 9 years ago

Subject changed from (ex PT/ Technique)Apache 2 HTTP Server: No reporting on whether Apache 2 was started or not to Apache 2 HTTP Server: No reporting on whether Apache 2 was started or not
Target version changed from 2.6.20 to 2.10.10