Bug 1425349 - can't resize disk when running Fedora25 Cloud image in OpenStack
Summary: can't resize disk when running Fedora25 Cloud image in OpenStack
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cloud-init
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Garrett Holmstrom
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-21 09:26 UTC by Kevin Zhao
Modified: 2017-12-12 10:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1440859 (view as bug list)
Environment:
Last Closed: 2017-12-12 10:13:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Zhao 2017-02-21 09:26:01 UTC
Description of problem:

In openstack, upload a image from Fedora25 cloud image. After boot, I see that cloud init can't resize the disk.
Hardware: Aarch64
Openstack Newton

Version-Release number of selected component (if applicable):


How reproducible:
1.glance image-create --name fedora25 --disk-format qcow2 --container-format bare --visibility public --file Fedora-Cloud-Base-25-1.3.aarch64.qcow2 --progress
2.IMAGE_UUID=$(glance image-list | grep fedora25 | awk '{ print $2 }')
glance image-update --property hw_firmware_type=uefi --property os_command_line='console=tty0 console=ttyAMA0' ${IMAGE_UUID}

3.nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0
test -f ~/.ssh/id_rsa.pub || ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa
nova keypair-add --pub-key ~/.ssh/id_rsa.pub testkey

4.IMAGE_UUID=$(glance image-list | grep fedora25 | awk '{ print $2 }')
NET_UUID=$(neutron net-list | grep private | awk '{ print $2 }')
nova boot --image ${IMAGE_UUID} --flavor m1.medium --nic net-id=${NET_UUID} --security-group default --key-name testkey fedora25-instance

5. ssh into the instance and use journalctl




Steps to Reproduce:
1.
2.
3.

Actual results:

Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] cc_resizefs.py[DEBUG]: Resizing / (ext4) using resize2fs /dev/vda3
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Running command ('resize2fs', '/dev/vda3') with allowed return codes [0] (shell=False, capture=True)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Resizing took 0.022 seconds
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] cc_resizefs.py[DEBUG]: Resized root filesystem (type=ext4, val=True)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] handlers.py[DEBUG]: finish: init-network/config-resizefs: SUCCESS: config-resizefs ran successfully
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] stages.py[DEBUG]: Running module disk_setup (<module 'cloudinit.config.cc_disk_setup' from '/usr/lib/python3.5/site-packages/cloudinit/config/cc_disk_set
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] handlers.py[DEBUG]: start: init-network/config-disk_setup: running config-disk_setup with frequency once-per-instance
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_disk_setup - wb: [420] 24 bytes
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_disk_setup (recursive=False)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_disk_setup (recursive=False)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] helpers.py[DEBUG]: Running config-disk_setup using lock (<FileLock using file '/var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_d
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] handlers.py[DEBUG]: finish: init-network/config-disk_setup: SUCCESS: config-disk_setup ran successfully
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] stages.py[DEBUG]: Running module mounts (<module 'cloudinit.config.cc_mounts' from '/usr/lib/python3.5/site-packages/cloudinit/config/cc_mounts.py'>) wit
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] handlers.py[DEBUG]: start: init-network/config-mounts: running config-mounts with frequency once-per-instance
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_mounts - wb: [420] 23 bytes
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_mounts (recursive=False)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_mounts (recursive=False)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] helpers.py[DEBUG]: Running config-mounts using lock (<FileLock using file '/var/lib/cloud/instances/01501eda-7d6c-41bf-848f-003ad37ee033/sem/config_mount
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] cc_mounts.py[DEBUG]: Attempting to determine the real name of ephemeral0
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] openstack.py[DEBUG]: Using ec2 style lookup to find device ['ephemeral0']
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] openstack.py[DEBUG]: Using openstack style lookup to find device ['ephemeral0']
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: Running command ['blkid', '-tLABEL=ephemeral0', '-odevice'] with allowed return codes [0, 2] (shell=False, capture=True)
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] cc_mounts.py[DEBUG]: Ignoring nonexistant default named mount ephemeral0
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] cc_mounts.py[DEBUG]: Attempting to determine the real name of swap
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] openstack.py[DEBUG]: Using ec2 style lookup to find device ['swap']
                                                   util.subp(["growpart", diskdev, partnum])
                                                 File "/usr/lib/python3.5/site-packages/cloudinit/util.py", line 1832, in subp
                                                   cmd=args)
                                               cloudinit.util.ProcessExecutionError: Unexpected error while running command.
                                               Command: ['growpart', '/dev/vda', '3']
                                               Exit code: 2
                                               Reason: -
                                               Stdout: 'FAILED: failed to resize\n'
                                               Stderr: "GPT PMBR size mismatch (6291455 != 83886079) will be corrected by w(rite).\nattempt to resize /dev/vda failed. sfdisk output below:\n| GPT PMBR size mismatc
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] util.py[DEBUG]: resize_devices took 0.300 seconds
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] cc_growpart.py[DEBUG]: '/' FAILED: failed to resize: disk=/dev/vda, ptnum=3: Unexpected error while running command.
                                               Command: ['growpart', '/dev/vda', '3']
                                               Exit code: 2
                                               Reason: -
                                               Stdout: 'FAILED: failed to resize\n'
                                               Stderr: "GPT PMBR size mismatch (6291455 != 83886079) will be corrected by w(rite).\nattempt to resize /dev/vda failed. sfdisk output below:\n| GPT PMBR size mismatc
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] handlers.py[DEBUG]: finish: init-network/config-growpart: SUCCESS: config-growpart ran successfully
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] stages.py[DEBUG]: Running module resizefs (<module 'cloudinit.config.cc_resizefs' from '/usr/lib/python3.5/site-packages/cloudinit/config/cc_resizefs.py'
Feb 21 09:13:45 host-10-0-0-4 cloud-init[695]: [CLOUDINIT] handlers.py[DEBUG]: start: init-network/config-resizefs: running config-resizefs with frequency always


Expected results:

resize successfully
Additional info:

Comment 1 Garrett Holmstrom 2017-04-13 03:46:13 UTC
Which version of cloud-init are you using?  If it is older than cloud-init-0.7.9-4.fc25 then would you please see if the newer package works?  It should have several OpenStack compatibility fixes that were not present in the original version that Fedora 25 shipped with.

Barring that, I am afraid I have neither an OpenStack installation nor any Aarch64 hardware to test with, so the more details you can provide about the image you are trying to boot, the easier it should be to figure out what is broken.

Comment 2 Fedora End Of Life 2017-11-16 18:53:04 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:13:21 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.