opened
ingvagabund
```
Error: packet_device.libvirt: "facilities": required field is not set

Error: packet_device.libvirt: "facility": [REMOVED] Use the "facilities" array instead, i.e. change
  facility = "ewr1"
to
  facilities = ["ewr1"]
```
facility field removed in favor of facilities
issue
created
zeenix
Seems like an obvious fix to me.
comment
created
ingvagabund
CI is rolling, hopefully it will take at most 15 minutes to run to completion.
comment
created
ingvagabund
`/usr/bin/docker-current: error pulling image configuration: Get https://registry.svc.ci.openshift.org/v2/openshift/origin-release/blobs/sha256:43a478d6a38d27af0e4473b9e258aad3d052f8702ce553a5a0918b2a2105f18c: dial tcp 35.196.103.194:443: i/o timeout.
See '/usr/bin/docker-current run --help'.`

/retest
comment
created
ingvagabund
/retest
comment
created
ingvagabund
/retest
comment
created
ingvagabund
`'events is forbidden: User "system:serviceaccount:namespace-dff96ea8-66a2-11e9-978f-0cc47ab21966:default" cannot create events in the namespace "namespace-dff96ea8-66a2-11e9-978f-0cc47ab21966"'`
comment
@ingvagabund: The following test **failed**, say `/retest` to rerun them all:

Test name | Commit | Details | Rerun command
--- | --- | --- | ---
ci/prow/actuator-pkg-staleness | 0232a81a5517f075a505dedcf3668c049057b904 | [link](https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-api-provider-libvirt/147/pull-ci-openshift-cluster-api-provider-libvirt-master-actuator-pkg-staleness/12) | `/test actuator-pkg-staleness`

[Full PR test history](https://openshift-gce-devel.appspot.com/pr/openshift_cluster-api-provider-libvirt/147). [Your PR dashboard](https://openshift-gce-devel.appspot.com/pr/ingvagabund). Please help us cut down on flakes by [linking to](https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/openshift/cluster-api-provider-libvirt/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
This message directly preceded comment from bot *openshift-ci-robot* by author *zeenix*:
Seems like an obvious fix to me.
[APPROVALNOTIFIER] This PR is **APPROVED**

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=openshift%2Fcluster-api-provider-libvirt).

The pull request process is described [here](https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process)

<details >
Needs approval from an approver in each of these files:

- **[OWNERS](https://github.com/openshift/cluster-api-provider-libvirt/blob/master/OWNERS)**

Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
</details>
<!-- META={"approvers":["ingvagabund"]} -->
This message directly preceded comment from bot *openshift-ci-robot* by author *ingvagabund*:
CI is rolling, hopefully it will take at most 15 minutes to run to completion.
@ingvagabund: The following tests **failed**, say `/retest` to rerun them all:

Test name | Commit | Details | Rerun command
--- | --- | --- | ---
ci/jenkins/e2e | 0232a81a5517f075a505dedcf3668c049057b904 | [link](https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-api-provider-libvirt/147/pull-ci-openshift-cluster-api-provider-libvirt-master-e2e/386/) | `/test e2e`
ci/prow/actuator-pkg-staleness | 0232a81a5517f075a505dedcf3668c049057b904 | [link](https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-api-provider-libvirt/147/pull-ci-openshift-cluster-api-provider-libvirt-master-actuator-pkg-staleness/15) | `/test actuator-pkg-staleness`

[Full PR test history](https://openshift-gce-devel.appspot.com/pr/openshift_cluster-api-provider-libvirt/147). [Your PR dashboard](https://openshift-gce-devel.appspot.com/pr/ingvagabund). Please help us cut down on flakes by [linking to](https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/openshift/cluster-api-provider-libvirt/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
This message directly preceded comment from bot *openshift-ci-robot* by author *ingvagabund*:
/retest
@ingvagabund: The following tests **failed**, say `/retest` to rerun them all:

Test name | Commit | Details | Rerun command
--- | --- | --- | ---
ci/jenkins/e2e | 0232a81a5517f075a505dedcf3668c049057b904 | [link](https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-api-provider-libvirt/147/pull-ci-openshift-cluster-api-provider-libvirt-master-e2e/388/) | `/test e2e`
ci/prow/actuator-pkg-staleness | 0232a81a5517f075a505dedcf3668c049057b904 | [link](https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-api-provider-libvirt/147/pull-ci-openshift-cluster-api-provider-libvirt-master-actuator-pkg-staleness/16) | `/test actuator-pkg-staleness`

[Full PR test history](https://openshift-gce-devel.appspot.com/pr/openshift_cluster-api-provider-libvirt/147). [Your PR dashboard](https://openshift-gce-devel.appspot.com/pr/ingvagabund). Please help us cut down on flakes by [linking to](https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/openshift/cluster-api-provider-libvirt/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
This message directly preceded comment from bot *openshift-ci-robot* by author *ingvagabund*:
/retest
This message directly preceded comment from bot *openshift-ci-robot* by author *zeenix*:
Seems like an obvious fix to me.
This message directly preceded comment from bot *openshift-ci-robot* by author *ingvagabund*:
CI is rolling, hopefully it will take at most 15 minutes to run to completion.
This message directly preceded comment from bot *openshift-ci-robot* by author *ingvagabund*:
/retest
This message directly preceded comment from bot *openshift-ci-robot* by author *ingvagabund*:
/retest