Avoid monitoring provisoning issue when a service doesn't exist
ClosedPublic
Actions

Authored by dereckson on Mar 20 2022, 23:47.

Tags

None

Referenced Files

	F24256493: D2617.id6603.diff
	Wed, Feb 11, 22:18

	F24236743: D2617.id6603.diff
	Wed, Feb 11, 14:19

	Unknown Object (File)
	Fri, Feb 6, 21:03

	Unknown Object (File)
	Thu, Feb 5, 15:06

	Unknown Object (File)
	Wed, Feb 4, 15:20

	Unknown Object (File)
	Wed, Feb 4, 15:20

	Unknown Object (File)
	Wed, Feb 4, 13:30

	Unknown Object (File)
	Sun, Feb 1, 01:29

View All Files

Subscribers

None

Details

Reviewers

dereckson

Maniphest Tasks

T1704: Monitor HTTP back-end from Docker containers

Commits

rOPS1817b70f630e: Avoid monitoring provisoning issue when a service doesn't exist

Summary

This is a follow-up for 49771b70088d.

Ref T1704.

Test Plan

Run on Dwellers

Diff Detail

Repository

rOPS Nasqueron Operations

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

dereckson requested review of this revision.Mar 20 2022, 23:47

dereckson created this revision.

Harbormaster completed remote builds in B4101: Diff 6603.Mar 20 2022, 23:47

dereckson accepted this revision.Mar 20 2022, 23:47

This revision is now accepted and ready to land.Mar 20 2022, 23:47

Closed by commit rOPS1817b70f630e: Avoid monitoring provisoning issue when a service doesn't exist (authored by dereckson). · Explain WhyMar 20 2022, 23:47

This revision was automatically updated to reflect the committed changes.

dereckson added a commit: rOPS1817b70f630e: Avoid monitoring provisoning issue when a service doesn't exist.

Revision Contents
Changeset List

Path

Size

_modules/

paas_docker.py

2 lines

Diff 6604

View Options

Avoid monitoring provisoning issue when a service doesn't existClosedPublicActions