yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1366891@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.6~bzr1016-0ubuntu1

---------------
cloud-init (0.7.6~bzr1016-0ubuntu1) utopic; urgency=medium

  * New upstream snapshot.
    * upstart: block networking from coming up until after
      cloud-init-local has run. (LP: #1368861)
    * upstart: ensure /run mounted before cloud-init-local (LP: #1353008)
    * log failures in route info.
    * Openstack: do not search redundant urls for openstack datasource.
      do not load urls just to check if they're present when crawling.
    * ConfigDrive: fixes for better consumption of vendor-data
    * resizefs: make sure target is writable before attempting
      in order to avoid failures in containers. (LP: #1366891)
    * freebsd fixes.
    * ssh_authkey_fingerprints: correctly allow disabling (LP: #1340903)
    * CloudStack: work around bug in metadata service (LP: #1356855)
    * docs: fix doc about disk-setup 'table_type' (LP: #1313114)
    * resolv.conf: fix rendering if options not provided (LP: #1328953)
    * ensure keys exist before running ssh on systemd (LP: #1333920)
 -- Scott Moser <smoser@xxxxxxxxxx>   Fri, 12 Sep 2014 18:12:31 -0400

** Changed in: cloud-init (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1366891

Title:
  warning to console in container on failed resize

Status in Init scripts for use on cloud images:
  In Progress
Status in “cloud-init” package in Ubuntu:
  Fix Released

Bug description:
  inside a container, a device may exist, but even as root not be able to write to it.
  currently that results in warning to console.

  $ lsb_release -sc
  trusty

  $ awk '$5 == "/" { print $0 }' /proc/self/mountinfo 
  79 61 253:1 /var/lib/lxc/t1/rootfs / rw,relatime - ext4 /dev/disk/by-label/cloudimg-rootfs rw,data=ordered

  
  $ ls -l /dev/disk/by-label/cloudimg-rootfs
  lrwxrwxrwx 1 root root 11 Sep  4 12:49 /dev/disk/by-label/cloudimg-rootfs -> ../../loop0
  $ ls -l /dev/loop0
  brw-rw---- 1 root disk 7, 0 Sep  4 12:49 /dev/loop0

  $ sudo sh -c 'echo hi >/dev/loop0'
  sh: 1: cannot create /dev/loop0: Operation not permitted
  # outside this would give I/O error.

  $ sudo python -c 'import os; print(os.access("/dev/loop0", os.W_OK))'
  False

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cloud-init 0.7.5-0ubuntu1.1
  ProcVersionSignature: User Name 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Mon Sep  8 16:24:56 2014
  Ec2AMI: ami-00000064
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: aki-00000002
  Ec2Ramdisk: ari-00000002
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.cloud.init.local.conf: 2014-09-08T14:38:58.888631

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1366891/+subscriptions