add bugzilla component to OWNERS

[elmiko]

This change adds the bugzilla component name to the OWNERS file to
comply with the prodsec requirements for OpenShift builds through ART.

[elmiko]

/cherry-pick release-4.6
/cherry-pick release-4.5

[openshift-cherrypick-robot]

@elmiko: once the present PR merges, I will cherry-pick it on top of release-4.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.6
/cherry-pick release-4.5

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.

[elmiko]

/cherry-pick release-4.4

[openshift-cherrypick-robot]

@elmiko: once the present PR merges, I will cherry-pick it on top of release-4.4 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.4

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.

[elmiko]

/cherry-pick release-4.5

[openshift-cherrypick-robot]

@elmiko: once the present PR merges, I will cherry-pick it on top of release-4.5 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.5

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.

[JoelSpeed]

Should we also be including the subcomponent on this?

[elmiko]

for this one i think we should not include the subcomponent. subcomponent is optional and the cao could be related in bugzilla to other providers as well (eg ovirt, openstack).

[JoelSpeed]

Technically I think we should have a separate component for CAO, but I would expect any bug that is for the CAO (not the CA) to be related to the cluster-infrastructure team, not any provider team in particular

[elmiko]

i tend to agree about having a separate component, or maybe just a separate subcomponent. imo, considering that "subcomponent" in the OWNERS is optional, we should opt to not use it to ensure we aren't over-scoping.

[JoelSpeed]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 [JoelSpeed]

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

[michaelgugino]

/lgtm

[michaelgugino]

/lgtm cancel

[michaelgugino]

I don't think the subcomponent is actually optional. BZ usually complains when I try to create a bug without setting it.

[elmiko]

I don't think the subcomponent is actually optional. BZ usually complains when I try to create a bug without setting it.

in the docs for changing the OWNERS file it said that "component" is required, but "subcomponent" is optional. i can't link the doc here, but this is the relevant section:

# Bugillza fields at the same level. 

# Required. The repo's associated Bugillza component. e.g.:
component: "Networking"

# Optional. Specify only if the repo is associated with a subcomponent e.g.:
subcomponent: "multus"

# Unusual. Specify only if your Bugzilla product is not OCP
product: "..."

my thinking here is that since CAO could be associated with provider like bare metal or openstack, we should leave the subcomponent empty.

[michaelgugino]

/lgtm

[openshift-cherrypick-robot]

@elmiko: new pull request created: #173

In response to this:

/cherry-pick release-4.6
/cherry-pick release-4.5

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.

[openshift-cherrypick-robot]

@elmiko: new pull request created: #174

In response to this:

/cherry-pick release-4.4

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.

[openshift-cherrypick-robot]

@elmiko: new pull request created: #175

In response to this:

/cherry-pick release-4.5

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.