Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

Error when uploading Ubuntu 18.04 qcow2 image via horizon #86

Open
davecore82 opened this issue Oct 19, 2020 · 3 comments
Open

Error when uploading Ubuntu 18.04 qcow2 image via horizon #86

davecore82 opened this issue Oct 19, 2020 · 3 comments

Comments

@davecore82
Copy link

I downloaded https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img on my laptop and tried to upload it with the microstack dashboard. I select the QCOW2 format and click Create image but get the following error:

<html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.19.0</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
@davecore82
Copy link
Author

$ snap list microstack
Name Version Rev Tracking Publisher Notes
microstack ussuri 216 latest/beta canonical✓ devmode

@davecore82 davecore82 changed the title Error when uploading Uubntu 18.04 qcow2 image via horizon Error when uploading Ubuntu 18.04 qcow2 image via horizon Oct 19, 2020
@davecore82
Copy link
Author

Using the CLI works:

microstack.openstack --os-username=admin --os-password= image create --file ./Downloads/bionic-server-cloudimg-amd64.img --public --container-format bare --disk-format qcow2 bionic

@pengale
Copy link
Contributor

pengale commented Oct 23, 2020

MicroStack should be setting the upload size that the web interface accepts to something much larger than the default. I thought there was a launchpad bug open about this, but I couldn't find it. (https://bugs.launchpad.net/microstack)

You can fix this yourself by finding and tweaking the Django settings in /var/microstack/common/etc/ It would definitely be nice if MicroStack came configured appropriately for this out of the box, though!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pengale @davecore82