This bug was fixed in the package curtin - 0.1.0~bzr425-0ubuntu1~16.04.1

curtin (0.1.0~bzr425-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  [ Scott Moser ]
  * debian/new-upstream-snapshot: add writing of debian changelog entries.

  [ Ryan Harper ]
  * New upstream snapshot.
    - unittest,tox.ini: catch and fix issue with trusty-level mock of open
    - block/mdadm: add option to ignore mdadm_assemble errors  (LP: #1618429)
    - curtin/doc: overhaul curtin documentation for
      (LP: #1351085)
    - curtin.util: re-add support for RunInChroot  (LP: #1617375)
    - curtin/net: overhaul of eni rendering to handle mixed ipv4/ipv6 configs
    - curtin.block: refactor clear_holders logic into block.clear_holders and
      cli cmd
    - curtin.apply_net should exit non-zero upon exception.  (LP: #1615780)
    - apt: fix bug in disable_suites if sources.list line is blank.
    - vmtests: disable Wily in vmtests
    - Fix the unittests for test_apt_source.
    - get CURTIN_VMTEST_PARALLEL shown correctly in jenkins-runner output
    - fix vmtest check_file_strippedline to strip lines before comparing
    - fix whitespace damage in tests/vmtests/
    - fix dpkg-reconfigure when debconf_selections was provided.
      (LP: #1609614)
    - fix apt tests on non-intel arch
    - Add apt features to curtin.  (LP: #1574113)
    - vmtest: easier use of parallel and controlling timeouts
    - mkfs.vfat: add force flag for formating whole disks  (LP: #1597923)
    - block.mkfs: fix sectorsize flag  (LP: #1597522)
    - block_meta: cleanup use of sys_block_path and handle cciss knames
      (LP: #1562249)
    - block.get_blockdev_sector_size: handle _lsblock multi result return
      (LP: #1598310)
    - util: add target (chroot) support to subp, add target_path helper.
    - block_meta: fallback to parted if blkid does not produce output
      (LP: #1524031)
    - commands.block_wipe:  correct default wipe mode to 'superblock'
    - tox.ini: run coverage normally rather than separately
    - move uefi boot knowledge from launch and vmtest to xkvm

 -- Ryan Harper <>  Mon, 03 Oct 2016 13:43:54

** Changed in: curtin (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  Confusing 'success' message when apply_net fails.

Status in curtin:
  Fix Committed
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:

   * Curtin produced a configusing 'success' message when failying to apply
     a provided network configuration.

     Curtin has been updated to ensure that if 'apply_net' commands fail
     the return code is propagated up to the invocation and no longer 
     prints both a success and failure message when a failure occurs.
  [Test Case]

   * Install proposed curtin package and run the command
     - # curtin apply_net -t target -c bad.yaml

    PASS: Curtin does not emit successful message:
          'Applied network configuration successfully'

    FAIL: Curtin emits both
          'Applied network configuration successfully' and
          'failed to apply network config'

  [Regression Potential]

   * Users of apply_net cli command may have examined the output of the
     command which is now modified, as well as the return code.

  [Original Description]

  When apply_net fails, the user both a fail message and a success
  message.. a bit confusing.

  root@x1:~# curtin apply_net -t target -c bad.yaml
  Applying network configuration
  failed to apply network config
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/curtin/commands/", line 
78, in apply_net_main
    File "/usr/lib/python3/dist-packages/curtin/commands/", line 
44, in apply_net
      ns = net.parse_net_config(network_config)
    File "/usr/lib/python3/dist-packages/curtin/net/", line 283, in 
      net_config = config.load_config(path)
    File "/usr/lib/python3/dist-packages/curtin/", line 117, in 
      return yaml.safe_load(content)
    File "/usr/lib/python3/dist-packages/yaml/", line 94, in 
      return load(stream, SafeLoader)
    File "/usr/lib/python3/dist-packages/yaml/", line 72, in load
      return loader.get_single_data()
    File "/usr/lib/python3/dist-packages/yaml/", line 35, in 
      node = self.get_single_node()
    File "/usr/lib/python3/dist-packages/yaml/", line 36, in 
      document = self.compose_document()
    File "/usr/lib/python3/dist-packages/yaml/", line 55, in 
      node = self.compose_node(None, None)
    File "/usr/lib/python3/dist-packages/yaml/", line 84, in 
      node = self.compose_mapping_node(anchor)
    File "/usr/lib/python3/dist-packages/yaml/", line 133, in 
      item_value = self.compose_node(node, item_key)
    File "/usr/lib/python3/dist-packages/yaml/", line 84, in 
      node = self.compose_mapping_node(anchor)
    File "/usr/lib/python3/dist-packages/yaml/", line 127, in 
      while not self.check_event(MappingEndEvent):
    File "/usr/lib/python3/dist-packages/yaml/", line 98, in 
      self.current_event = self.state()
    File "/usr/lib/python3/dist-packages/yaml/", line 428, in 
      if self.check_token(KeyToken):
    File "/usr/lib/python3/dist-packages/yaml/", line 116, in 
    File "/usr/lib/python3/dist-packages/yaml/", line 257, in 
  yaml.scanner.ScannerError: while scanning for the next token
  found character '\t' that cannot start any token
    in "<unicode string>", line 4, column 5:
  Applied network configuration successfully

  Note the emitting of messages

  "failed to apply network config"
  "Applied network configuration successfully"

  Really a minor issue.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to