cannot upload custom image Cannot upload to a complete file

Bug #2039871 reported by Noam Angel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alexsander de Souza

Bug Description

$ maas $PROFILE boot-resources create name='rhel/9-custom' title='RHEL 9.2 Custom' architecture='amd64/generic' filetype='tgz' content@=rhel9.tar.gz
Cannot upload to a complete file.

Revision history for this message
Anton Troyanov (troyanov) wrote :

Can you please check if there are any errors in the logs?

journalctl -u snap.maas.pebble -t maas-regiond
journalctl -u snap.maas.pebble -t maas-rackd

Revision history for this message
Noam Angel (noama) wrote :

Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.04:s390x:hwe-22.04: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.04:s390x:hwe-22.04-edge: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:amd64:ga-22.10: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:amd64:ga-22.10-lowlatency: to_add=[] to_remove>
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:arm64:ga-22.10: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:arm64:xgene-uboot: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:arm64:xgene-uboot-mustang: to_add=[] to_remove>
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:armhf:ga-22.10: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:armhf:generic-lpae-generic-lpae: to_add=[] to_>
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:ppc64el:ga-22.10: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: sstreams: [info] com.ubuntu.maas:stable:v3:download/com.ubuntu.maas.stable:v3:boot:22.10:s390x:ga-22.10: to_add=[] to_remove=[]
Oct 19 19:50:51 maas-regiond[1669]: maasserver.clusterrpc.boot_images: [info] Rack controller (rh7hsx) has imported boot resources.
Oct 19 19:51:31 maas-regiond[1670]: regiond: [info] 127.0.0.1 PUT /MAAS/api/2.0/boot-resources/34/upload/89/ HTTP/1.1 --> 400 BAD_REQUEST (referrer: -; agent: Python-httpl>
Oct 19 19:51:32 maas-regiond[1671]: maasserver.rpc.leases: [info] Lease update: commit for 10.209.86.200 on 02:34:eb:aa:b0:68 at 2023-10-19 16:51:32 (lease time: 600s)

Revision history for this message
Noam Angel (noama) wrote :

was able to sync from ui other images, but when i try to upload custom when it failed shortly with

$ maas $PROFILE boot-resources create name='rhel/9-custom' title='RHEL 9.2 Custom' architecture='amd64/generic' filetype='tgz' content@=rhel9.tar.gz
Cannot upload to a complete file

what that means?

log files does not show anything related

Revision history for this message
Noam Angel (noama) wrote :

seems like if you upload custom image while there are ubuntu initial images on sync you get this message.

i have reinstalled maas, let maas sync ubuntu image, upload custom image, wait for sync. sync ok

Revision history for this message
Alexsander de Souza (alexsander-souza) wrote :

this should be fixed in master now.

is there any particular reason you are running `latest/edge`?

Changed in maas:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Alexsander de Souza (alexsander-souza)
milestone: none → 3.5.0
Revision history for this message
Noam Angel (noama) wrote :

No, I have move to 3.3 stable

I initially follow installation doc which implied to install latest edge, maybe you should correct the way user view this document as it was not clear it is not stable

Changed in maas:
milestone: 3.5.0 → 3.5.0-beta1
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.