Use new podinfo command to gather pod data

[jlojosnegros]

From v0.1.7 debug-tools has a new podinfo command to help us to gather
info from pods to complement PodResourcesAPI info.
The information gathered is the same that was gotten with the current
oc command.

[coveralls]

Pull Request Test Coverage Report for Build 2516

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 60.508%

---

Totals
Change from base Build 2490:	0.0%
Covered Lines:	1644
Relevant Lines:	2717

---

💛 - Coveralls

[openshift-ci]

@jlojosnegros: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-operator-upgrade	54b1a3e	link	false	/test e2e-gcp-operator-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[ffromani]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fromanirh, jlojosnegros

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fromanirh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jlojosnegros]

I think there are two Ci lanes that still need to be overridden:

/override ci/prow/e2e-gcp-operator-upgrade
/override ci/prow/e2e-gcp

[openshift-ci]

@jlojosnegros: jlojosnegros unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:.

In response to this:

I think there are two Ci lanes that still need to be overridden:

/override ci/prow/e2e-gcp-operator-upgrade
/override ci/prow/e2e-gcp

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jlojosnegros]

/cherry-pick release-4.10

[openshift-cherrypick-robot]

@jlojosnegros: new pull request created: #908

In response to this:

/cherry-pick release-4.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jlojosnegros]

/cherry-pick release-4.9

[openshift-cherrypick-robot]

@jlojosnegros: #907 failed to apply on top of branch "release-4.9":

Applying: Use new `podinfo` command to gather pod data
.git/rebase-apply/patch:123: trailing whitespace.
		"namespace":"{{.ObjectMeta.Namespace}}", 
.git/rebase-apply/patch:124: trailing whitespace.
		"name":"{{.ObjectMeta.Name}}", 
.git/rebase-apply/patch:125: trailing whitespace.
		"nodeName":"{{.Spec.NodeName}}", 
.git/rebase-apply/patch:126: trailing whitespace.
		"qosClass": "{{.Status.QOSClass}}", 
.git/rebase-apply/patch:130: trailing whitespace.
			{{- if (ne $cdx 0) }},{{ end }} 
warning: squelched 6 whitespace errors
warning: 11 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	must-gather/collection-scripts/gather_nodes
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging must-gather/collection-scripts/gather_nodes
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use new `podinfo` command to gather pod data
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jlojosnegros]

/cherry-pick release-4.8

[openshift-cherrypick-robot]

@jlojosnegros: #907 failed to apply on top of branch "release-4.8":

Applying: Use new `podinfo` command to gather pod data
.git/rebase-apply/patch:123: trailing whitespace.
		"namespace":"{{.ObjectMeta.Namespace}}", 
.git/rebase-apply/patch:124: trailing whitespace.
		"name":"{{.ObjectMeta.Name}}", 
.git/rebase-apply/patch:125: trailing whitespace.
		"nodeName":"{{.Spec.NodeName}}", 
.git/rebase-apply/patch:126: trailing whitespace.
		"qosClass": "{{.Status.QOSClass}}", 
.git/rebase-apply/patch:130: trailing whitespace.
			{{- if (ne $cdx 0) }},{{ end }} 
warning: squelched 6 whitespace errors
warning: 11 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	must-gather/collection-scripts/gather_nodes
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging must-gather/collection-scripts/gather_nodes
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use new `podinfo` command to gather pod data
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.