Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InfinispanOperatorProvisionerTest is failing CI checks when using named user accounts with different privileges #48

Closed
fabiobrz opened this issue May 18, 2023 · 1 comment
Labels
CI This issue affects or is related to the automation

Comments

@fabiobrz
Copy link
Member

For #46 a change has been made to the CI shell script in order to make the XTF configuration work with two different users (admin and master) with different privileges.
This is making the InfinispanOperatorProvisionerTest fail with the following traces:

...
[ERROR] org.jboss.intersmash.testsuite.provision.openshift.InfinispanOperatorProvisionerTest.basicProvisioningTest  Time elapsed: 19.192 s  <<< ERROR!
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://api.ci-ocp-4-12-amd64-aws-us-east-1-pzzzf.hive.aws.ci.openshift.org:6443/apis/infinispan.org/v1/namespaces/intersmash-test/infinispans. Message: Forbidden! User tadmin doesn't have permission. infinispans.infinispan.org is forbidden: User "tuser" cannot create resource "infinispans" in API group "infinispan.org" in the namespace "intersmash-test".
...

And this can only be solved by making tuser (i.e. the master account with regular privileges)a cluster-admin` as well.

We should investigate why this happens only on OpenShift CI infra and not locally or in internal runs/cluster.


  • Environment: testsuite
  • Steps to reproduce: ~/apache-maven-3.8.6/bin/mvn test -pl testsuite/ -Dtest=InfinispanOperatorProvisionerTest
@fabiobrz fabiobrz added the CI This issue affects or is related to the automation label May 18, 2023
@fabiobrz fabiobrz added the triage This issue needs investigation to better define its scope and context label Oct 27, 2023
@fabiobrz fabiobrz added this to the IM2 - WIP milestone Feb 2, 2024
@fabiobrz fabiobrz moved this to Todo in Intersmash library Feb 2, 2024
@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Sep 19, 2024
@fabiobrz fabiobrz removed the triage This issue needs investigation to better define its scope and context label Sep 20, 2024
@fabiobrz
Copy link
Member Author

This can be closed. CI checks are no longer run by OpenShift org Prow jobs, and the issue doesn't pop up in the latest internal CI checks runs.

@github-project-automation github-project-automation bot moved this from Todo to Done in Intersmash library Sep 20, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI This issue affects or is related to the automation
Projects
Development

No branches or pull requests

1 participant