cc_resizefs for zfs/zpool

Bug #1721243 reported by do3meli
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Medium
do3meli

Bug Description

the resizefs module is not able to handle zfs/zpool resizing for the root filesystem. if tried so we get the error message: "Could not determine filesystem type of /".

version: cloud_init-17.1-py2.7.egg

Tags: freebsd zfs

Related branches

Revision history for this message
Joshua Powers (powersj) wrote :

Hi! Thanks for taking the time to file a bug report.

Would it be possible to at least get both cloud-init logs from /var/log/cloud-init*?

I will move this to incomplete and when you attach them, please move the bug back to new. Thanks!

Changed in cloud-init:
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
do3meli (d-info-e) wrote :
Revision history for this message
do3meli (d-info-e) wrote :
Changed in cloud-init:
status: Incomplete → New
Revision history for this message
do3meli (d-info-e) wrote :

i have created a patch that works for me so far. please have a look at it. any feedback is welcome. i hope this is a good base for a merge.

also note that this bug may be related to https://bugs.launchpad.net/cloud-init/+bug/1645947

Revision history for this message
Scott Moser (smoser) wrote :

Hello do3meli,

Thank you for your contribution to cloud-init. Contributions to
cloud-init require the developer to have signed the Canonical Contributors
Agreement [1]. Your launchpad id is not currently listed as a member of
the contributor-agreement-canonical group [2].

Membership in that group is currently managed by a manual process, so it
is possible that you have followed the process but were not added to the
group. If you have already signed the contributor agreement, please
simply say so here.

For more information on contribution see the hacking documentation in
cloud-init [3].

If you have any questions, feel free to reach out in IRC (#cloud-init or private message) or via email.

Thanks again,
--
[1] https://www.ubuntu.com/legal/contributors
[2] https://launchpad.net/~contributor-agreement-canonical/+members
[3] http://cloudinit.readthedocs.io/en/latest/topics/hacking.html

Revision history for this message
do3meli (d-info-e) wrote :

Hi Scott,
I have just now signed the contributor agreement. may you have a look at it and grant me membership so we can go ahead and start looking at a possible merge?
thanks & regards
dom

Revision history for this message
Scott Moser (smoser) wrote :

do3meli,
Hi.
Thanks for following up.
Take a look at the hacking.html doc link listed above, and submit a merge proposal and we'll get it.

A quick look, my first comment is that unit tests on your added code would be great.

But please submit a merge proposal and we'll have the C-I bot run on your branch.

Let me know if you have any questions.
Thanks,
Scott

do3meli (d-info-e)
Changed in cloud-init:
status: New → In Progress
do3meli (d-info-e)
Changed in cloud-init:
assignee: nobody → do3meli (d-info-e)
do3meli (d-info-e)
tags: added: zfs
tags: added: freebsd
Revision history for this message
Scott Moser (smoser) wrote :

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=20e3ddab

Changed in cloud-init:
status: In Progress → Fix Committed
Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in Cloud-init 18.2

This bug is believed to be fixed in cloud-init in 18.2. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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