Closed droslean closed 3 years ago
All those variables are normally validated via the installer, it's surprising that you were able to skip the validation.
Could you describe how you ran the installer? Can you reproduce this consistently?
Could you describe how you ran the installer? Can you reproduce this consistently?
I run the normal create cluster command. I can reproduce that consistently. I think that this should be a permission error related. I noticed that my user doesn't have permissions to add an image in that OpenStack project. However, those errors are misleading.
I run the normal create cluster command. I can reproduce that consistently.
Great, this will be easier to debug.
I think that this should be a permission error related. I noticed that my user doesn't have permissions to add an image in that OpenStack project. However, those errors are misleading.
Agreed - it's poor UI experience. Let's find out what causes this error and catch it in the validations.
Is the installer logging anything useful before spitting this terraform error? We'll try to reproduce on our side.
We'll be tracking at https://bugzilla.redhat.com/show_bug.cgi?id=1835838
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
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
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-bot: Closing this issue.
Hi @droslean
Could you describe how you ran the installer? Can you reproduce this consistently?
I run the normal create cluster command. I can reproduce that consistently. I think that this should be a permission error related. I noticed that my user doesn't have permissions to add an image in that OpenStack project. However, those errors are misleading.
it's definitely not a permission issue to add_image. You would see something like:
DEBUG Creating a Glance image for your bootstrap ignition config...
FATAL failed to fetch Terraform Variables: failed to generate asset "Terraform Variables": failed to get openstack Terraform variables: Request forbidden: [POST http://x.y.z.z:9292/v2/images], error message: {"message": "You are not authorized to complete add_image action.<br /><br />\n\n\n", "code": "403 Forbidden", "title": "Forbidden"}
I built the installer from the same commit you have used:
./openshift-install unreleased-master-2633-gfb65b95076665c794e7c1cc148f56722761d0d31-dirty
built from commit fb65b95076665c794e7c1cc148f56722761d0d31
release image registry.svc.ci.openshift.org/origin/release:4.3
If you would like to help me figure this out and still have the environment, please can you share output of:
./openshift-install create cluster --dir=<install-dir> --log-level=debug
Version
built from branch
release-4.4
Platform:
What happened?