openshift / openshift-ansible-contrib

Additional roles and playbooks for OpenShift installation and management
https://www.openshift.com
Apache License 2.0
283 stars 371 forks source link

Error from server (Forbidden): User "admin" cannot list egressnetworkpolicies.network.openshift.io in the namespace "sample-py": User "admin" cannot list egressnetworkpolicies.network.openshift.io in project "sample-py" (get egressnetworkpolicies.network.openshift.io) #1039

Closed brikeyes closed 4 years ago

brikeyes commented 6 years ago

bkeyes@AEM-9Q8N662 MINGW64 ~/exports/friday/contrib/openshift-ansible-contrib/reference-architecture/day2ops/scripts (master) $ ./project_export.sh sample-py ###########

WARNING

########### This script is distributed WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND Beware ImageStreams objects are not importables due to the way they work See https://github.com/openshift/openshift-ansible-contrib/issues/967 for more information Exporting namespace to sample-py/ns.json Exporting rolebindings to sample-py/rolebindings.json Exporting serviceaccounts to sample-py/serviceaccounts.json Exporting secrets to sample-py/secrets.json Exporting deploymentconfigs to sample-py/dc*.json Patching DC... Patching DC... Exporting buildconfigs to sample-py/bcs.json Exporting builds to sample-py/builds.json Exporting imagestreams to sample-py/iss.json Exporting imagestreamtags to sample-py/imagestreamtags.json Exporting replicationcontrollers to sample-py/rcs.json Exporting services to sample-py/svc*.json Exporting pods to sample-py/pods.json Exporting podpreset to sample-py/podpreset.json Exporting configmaps to sample-py/cms.json Exporting egressnetworkpolicies to sample-py/egressnetworkpolicies.json Error from server (Forbidden): User "admin" cannot list egressnetworkpolicies.network.openshift.io in the namespace "sample-py": User "admin" cannot list egressnetworkpolicies.network.openshift.io in project "sample-py" (get egressnetworkpolicies.network.openshift.io)

Is this a BUG REPORT or a FEATURE REQUEST ? (choose one):

BUG REPORT INFO

Environment

Copy of inventory files and custom variables used (please omit your secrets!):

Command used to invoke ansible:

Output of ansible run:

Anything else do we need to know:

FEATURE REQUEST INFO

An introduction paragraph with "[tl;dr]" info.

Problem Description

What problem is being solved by the proposed feature?

What are the use cases for End User vs Deployer?

Also describe the target cloud provider.

Proposed Change

Describe the change you would like to make.

Overview

Alternatives

Security Impact

Other End User Impact

Performance Impact

Other Deployer Impact

Developer Impact

Documentation Impact

Implementation

Describe your plan for implementation steps and potential assignees/contributors.

Acceptance criteria

Provide a definition of done and acceptance criteria.

Testing

Describe how to test this, including manual steps, if any.

Dependencies

References

openshift-bot commented 4 years ago

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 commented 4 years ago

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

openshift-bot commented 4 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 4 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-ansible-contrib/issues/1039#issuecomment-714843759): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close 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.