Skip to content

Conversation

@jayaragini-hcl
Copy link

@jayaragini-hcl jayaragini-hcl commented Jul 30, 2025

This PR introduces the backend support for gNOI Healthz. However, since the necessary consumer logic for receiving and executing debug requests is currently absent within the upstream SONiC component containers, the current backend implementation only supports Host-level artifact collection. This involves running common debug commands directly on the host and generating the resulting *.tar.gz file, excluding component-specific debug data.

NOTE: All the Functionality testing has been done on SONiC Virtual Switch.

Below is the placeholder for Artifact tar file and the list of files

admin@sonic:/tmp/dump$ ls
sonic_20251106_082724534264  sonic_20251106_082724534264.tar.gz
admin@sonic:/tmp/dump/sonic_20251106_082724534264$ ls
host
admin@sonic:/tmp/dump/sonic_20251106_082724534264/host$ ls
core  log   pre_counter_20251106_082724  version.txt
db    post_counter_20251106_082954  routing.txt
admin@sonic:/tmp/dump/sonic_20251104_132111395021/host/log$ ls
audit	  cron.log	  frr	      lastlog	  swss		 user.log
auth.log     debug_info.log gnmi.log    lost+found  syslog	 user.log.1
btmp	  dpkg.log	  kern.log    private	  sysstat	 wtmp
chrony	  dump		  kern.log.1  README	  telemetry.log
admin@sonic:/tmp/dump/sonic_20251106_082724534264/host$ ls pre_counter_20251106_082724/
counter_db.json  top.txt
admin@sonic:/tmp/dump/sonic_20251106_082724534264/host$ ls post_counter_20251106_082954/
counter_db.json  top.txt
admin@sonic:/tmp/dump/sonic_20251106_082724534264/host$ ls db/
appl_db.json  asic_db.json  config_db.json  vidtorid.txt

Dependent FE PRs

sonic-net/sonic-gnmi#485
sonic-net/sonic-gnmi#486
sonic-net/sonic-gnmi#507
sonic-net/sonic-gnmi#487
sonic-net/sonic-gnmi#488
sonic-net/sonic-gnmi#489
sonic-net/sonic-gnmi#509

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@jayaragini-hcl jayaragini-hcl marked this pull request as draft July 30, 2025 05:06
@jayaragini-hcl
Copy link
Author

@rkavitha-hcl , @kanchanavelusamy could you please review the PR

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jayaragini-hcl
Copy link
Author

@kishanps , @magnusgao-google All the review comments have been addressed. Could you please review the updated PR and share your feedback?
cc: @ndas7

gnoi_reset
)

from host_modules import config_engine, debug_info, docker_service, file_service, gcu, host_service, image_service, reboot, showtech, systemd_service

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this changed and I see gnoi_reset missing.

'file_stat': file_service.FileService('file'),
'debug_service': debug_service.DebugExecutor('DebugExecutor'),
'gnoi_reset': gnoi_reset.GnoiReset('gnoi_reset')
'debug_info': debug_info.DebugInfo('debug_info')

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't debug_service different than debug_info ? Why are we removing debug_service ?

gnoi_reset is missing here too.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants