1. 14 Feb, 2018 5 commits
  2. 13 Feb, 2018 7 commits
    • Harald Sitter's avatar
      once the restart button is up upload the dist-upgrade log · c412951d
      Harald Sitter authored
      this way we'll not lose out on it in case the upgrade went wrong and
      we won't start after the restart
      c412951d
    • Harald Sitter's avatar
      lax restart needle a bit · 70a27fc8
      Harald Sitter authored
      had problem matching with a 0.96 match
      
      I continue to not understand why 0.96 isn't enough for two 0.95 areas
      though (this is not the first needle that had this problem)
      70a27fc8
    • Harald Sitter's avatar
      fix metadata import · a98f6781
      Harald Sitter authored
      - should run in the osautoinst if not the raid if
      - resolve relative to osautoinst root not raid root
      a98f6781
    • Harald Sitter's avatar
      make sure the symlink is gone before creating it · b38d4f26
      Harald Sitter authored
      we have a new feature to keep a build dir after failure, this implodes
      if we want to overwrite the previously existing raid dir, so make sure to
      drop it before linking again
      b38d4f26
    • Harald Sitter's avatar
      ignore++ · fc0880e8
      Harald Sitter authored
      fc0880e8
    • Harald Sitter's avatar
      archive the wok relative · e6ae0008
      Harald Sitter authored
      previously we'd have to dig into wok to get to the wok's artifacts, since
      they are the primary artifacts that is fairly daft though. by diring
      into the wok first we can archive them into the root of the artifacts dir
      e6ae0008
    • Harald Sitter's avatar
      add a new metadata system to get high level access to global metadata · 4d94c67d
      Harald Sitter authored
      this is primarily useful to get metadata out of the ISO so we know
      what was installed initially.
      
      this data is uploaded by the install core as soon as possible and later
      (on success) moved to a metdata dir for archival.
      so, for installs the metadata is in ulogs on error and metadata on success
      
      for !install tests they pick up the metadata from the image storage to
      seed their initial metadata dir (they may still added more info if
      applicable).
      they always have metadata (from the install), so even on errors we know
      what the image contained
      
      archival of this happens relative, so the metadata is in the main dir
      4d94c67d
  3. 12 Feb, 2018 18 commits
  4. 09 Feb, 2018 9 commits
  5. 08 Feb, 2018 1 commit