QA » openQA Project » openQA Tests

Motivation¶

See https://trello.com/c/wATMQ3Mo/917-5-import-export-nfs-shares-with-new-profile-format

Scope limited to SLE 15 only.

NFS drives are specified in the AutoYaST profile by an "undocumented" option. That is, by defining a drive with a "/dev/nfs" device, and then, each partition defines a NFS share, e.g.:

<drive>
  <device>/dev/nfs</device>
  <partitions>
    <partition>
      <mount>/</mount>
      <device>server:path</device>
    </partition>
  </partitions>
</drive>

The section contains a attribute. This is quite unexpected, because a section cannot contain a . In fact, the AutoYaST profile does not validate.

The support for importing this kind of drives was implemented in this card https://trello.com/c/x4LYDnwe/865-3-l3-important-bug-1130256-autoyast-for-a-nfs-root-fails-at-partitioning. But now we have to find a better way for defining NFS drives and be able to import/export this new format.

Note: currently, old format cannot be exported at all because we don't want to continue supporting this format for new products (from SLE-15 on).

The new format must be available for SP0 (GA), SP1 and master.

Review¶

• Added support for importing/exporting new format for NFS drives.
• PR (SLE-15-SP0): https://github.com/yast/yast-storage-ng/pull/900
• PR (SLE-15-SP1): https://github.com/yast/yast-storage-ng/pull/896
• PR (master): https://github.com/yast/yast-storage-ng/pull/899
• PR (SLE doc): https://github.com/SUSE/doc-sle/pull/418 (pending review)
• SR (SLE-15-SP0): https://build.suse.de/request/show/190666
• SR (SLE-15-SP1): https://build.suse.de/request/show/190650
• Added NFS section to AutoYaST documentation: https://github.com/SUSE/doc-sle/pull/418
  
• Not only NFS drives are missing in AutoYaST UI, so a follow-up card has been created:
  • Follow-up card to improve AutoYaST UI: https://trello.com/c/6GuKcKUs/3042-autoyast-ui-improve-drives-edition ```

Acceptance criteria¶

1. Functionality is tested manually to install with NFS share using autoyast profile
2. Autoyast profile generation is tested and verified that mount is correct
3. Documentation is validated and cross-checked with implementation
4. Ticket for the automated test is created in case scenario is worth automating