[RFE] Add the version of the branch to the version file about must-gather HOT 13 CLOSED

@palonsoro see #327 (comment)

from must-gather.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from must-gather.

#129 I think addresses this.
Other improvements are being made with #327

from must-gather.

/close

from must-gather.

@sferich888: Closing this issue.

from must-gather.

@sferich888 , #129 is not addressing this, as the version file in latest must-gather versions is still not showing information about the version.

The version file in a must-gather from an OCP 4.11 cluster only shows 4.0-art-dev:

$ oc version
Client Version: 4.11.9
Server Version: 4.11.9
Kubernetes Version: v1.24.0+dc5a2fd

$ cat version 
openshift/must-gather
4.0-art-dev

There is no info about the version of the must-gather image used to collect it.

from must-gather.

A version obtained at the must-gather image will never reflect the version used to run oc adm must-gather command but the version of oc inside the must-gather image.

Writing that version doesn't have greatest value, because it is imposed by the cluster version (the must-gather image is derived from cli image of the same release, so oc version is imposed by the release).

If the client version is desired, this should be proposed and implemented in oc repo

from must-gather.

This issue is not for the oc version used for running the command, but the version of the must-gather script used.
The current version script in the must-gather (https://github.com/openshift/must-gather/blob/release-4.11/collection-scripts/version) is not working properly and only shows 4.0-art-dev (and not the digest of the image, the PR of the script, or nothing else):

$ cat version 
openshift/must-gather
4.0-art-dev

/reopen

#327 could be the solution for this issue.

from must-gather.

@oarribas: Reopened this issue.

from must-gather.

@sanchezl if you think #327 fixes this issue; can you plean link and close upon merger?

from must-gather.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from must-gather.

/close

from must-gather.

@sferich888: Closing this issue.

from must-gather.