resizefs: first check if device is writable before attempting

In a container the device nodes may exist but not be writable.
I'm seeing this on trusty host with trusty containers, the root
device ends up looking like it is to /dev/loop0.

LP: #1366891

1 files changed, 1 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index dbd0715a..01ecb53c 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -31,6 +31,7 @@
  - Datasource: fix broken logic to provide hostname if datasource does not
    provide one
  - Improved and less verbose logging.
+ - resizefs: first check that device is writable.
 0.7.5:
  - open 0.7.5
  - Add a debug log message around import failures