OCPBUGS-90611: Bump origin

[winiciusallan]

The 4.16 release is out dated with regarding to the Origin package. This PR bumps the origin vendored version to the 4.16 branch HEAD commit (3a9e376)

Other changes were needed since some imported packages don't exist anymore.

• Added a standard_suite.go file to point out to our openshift/openstack suite

[openshift-ci-robot]

@winiciusallan: This pull request references Jira Issue OCPBUGS-90611, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-90611 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

The 4.16 release is out dated with regarding to the Origin package. This PR bumps the origin vendored version to the 4.16 branch HEAD commit (3a9e376)

Other changes were needed since some imported packages don't exist anymore.

• Added a standard_suite.go file to point out to our `openshift/openstack" suite

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @winiciusallan. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[mandre]

/ok-to-test

[openshift-ci]

@winiciusallan: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[mandre]

/lgtm
/approve
/verified bypass

Let's just wait for #270 to merge first. We'll do a /jira refresh once that's done, to get a valid associated bug.
/hold

[openshift-ci-robot]

@mandre: The verified label has been added.

Details

In response to this:

/lgtm
/approve
/verified bypass

Let's just wait for #270 to merge first. We'll do a /jira refresh once that's done, to get a valid associated bug.
/hold

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [mandre]

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

[winiciusallan]

/jira refresh

Since #270 is now merged, refreshing the jira label to get the associated bug.

[openshift-ci-robot]

@winiciusallan: This pull request references Jira Issue OCPBUGS-90611, which is invalid:

• expected Jira Issue OCPBUGS-90611 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Since #270 is now merged, refreshing the jira label to get the associated bug.

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 openshift-eng/jira-lifecycle-plugin repository.

[winiciusallan]

/jira refresh

[openshift-ci-robot]

@winiciusallan: This pull request references Jira Issue OCPBUGS-90611, which is invalid:

• expected dependent Jira Issue OCPBUGS-90609 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[winiciusallan]

/jira refresh

[openshift-ci-robot]

@winiciusallan: This pull request references Jira Issue OCPBUGS-90611, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.z) matches configured target version for branch (4.16.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-90609 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-90609 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
• bug has dependents

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[winiciusallan]

/unhold

Unholding since #270 is merged

[openshift-ci-robot]

@winiciusallan: Jira Issue Verification Checks: Jira Issue OCPBUGS-90611
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-90611 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

The 4.16 release is out dated with regarding to the Origin package. This PR bumps the origin vendored version to the 4.16 branch HEAD commit (3a9e376)

Other changes were needed since some imported packages don't exist anymore.

• Added a standard_suite.go file to point out to our openshift/openstack suite

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 openshift-eng/jira-lifecycle-plugin repository.