Builds that reference invalid imagestreamtags should be noted.

[bparees]

osc describe and the web ui should give an indication if a BuildConfig uses a From reference to an imagestreamtag that cannot be resolved.

This could be because the imagestream doesn't exist, or because the tag doesn't exist within the imagestream.

Both are technically valid (you could be planning to create the imagestream or tag later) but it'd be good to be warned of it.

@smarterclayton fyi.

[liggitt]

That would require the web UI to fetch every ImageStreamTag individually. Also, since those can reference things in other namespaces, it would require the viewing user to have permissions in those namespaces. For cross-namespace build sources, it is likely permission will only have been given to the current namespace's service accounts (or even more narrowly, the builder service account), and the viewing user won't have permission to see if it exists.

[smarterclayton]

We probably have to do this to be a good product. It's just not easy.

----- Original Message -----

That would require the web UI to fetch every ImageStreamTag individually.
Also, since those can reference things in other namespaces, it would require
the viewing user to have permissions in those namespaces. For
cross-namespace build sources, it is likely permission will only have been
given to the current namespace's service accounts (or even more narrowly,
the builder service account), and the viewing user won't have permission to
see if it exists.

---

Reply to this email directly or view it on GitHub:
#2957 (comment)

[jwforres]

@bparees is this being done at all today as part of the API or CLI?

[bparees]

@jwforres if it's done anywhere, it might be done in oc status, @gabemontero would know, but it's not done in oc describe and it's definitely not part of the api.

[gabemontero]

This is what oc status provides.

At first blush I believe it covers what is in this issue's description. But as alluded to, not part of the api.

[openshift-bot]

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

[openshift-bot]

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

[bparees]

/remove-lifecycle rotten
/lifecycle frozen