Pulp

First off, I'm delighted you filed this. It's not often a non-core member points out a pre-beta issue in the code!

In this case (unfortunately) the note is correct. Currently, Pulp is not able to check if pulp_streamer or httpd are running. I can understand wanting to have those check also, but that would be a new feature since we would need those components to "heartbeat" like pulp_celerybeat, pulp_resource_manager, and pulp_workers do today.

So given ^ do you want to file two new stories requesting that functionality? One for pulp_streamer and one for httpd? Since the docs are correct, I think this should be closed as NOTABUG.

@tcarlin, what do you think?

I believe there are separate issues:

• There should be some type of warning to administrators since the result may be Pulp database corruption. This was my original intent in filing this issue
• I agree with you that determining if pulp_streamer or httpd would indeed be separate issues. I will file them so the work is properly segregated.

Thank you for your thoughtful response.

I touched up the language some on the stories you filed, #2529 and #2530.

In order to do that, we need those components to heartbeat so I've created tasks for each of those as #2534 and #2535. Those would have to be done first, so I added a blocking relationship between the issues.

This request seems to be well captured in #2529 and #2530, so I think closing this as duplicate of #2529 and #2530 would be productive.

@tcarlin, how does ^ sound?

Sounds like a plan. If we do have downstream cases relating, we can link to these 3 issues at that time.