[atomic-wg] Issue #331: Issue Tracker for F27 release blockers
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
This ticket will be used throughout the f27 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on.
**Blocker Bugs**
- [BZ#1490505](https://bugzilla.redhat.com/show_bug.cgi?id=1490505) cloud-init fails when calling `xfs_growfs /dev/mapper/atomicos-root` on Fedora Atomic Host
**Important Bugs**
Over time only the description of this bug will be edited for updates. The comments of this bug will be used like a *changelog* for the description.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/331
5 years, 11 months
[atomic-wg] Issue #386: Provide updated examples for composing custom ostrees
by Micah Abbott
miabbott reported a new issue against the project: `atomic-wg` that you are following:
``
We've received requests/complaints from #atomic on Freenode about the lack of up to date documentation for composing custom ostrees.
```
I've been trying to build my own atomic repo using rpm-ostree for the past couple days.
I'm using a Fedora 27 workstation to build a repo for Atomic Fedora 27.
I've tried adapting multiple instructions found online (most of them very old).
Do working instructions exist anywhere for Fedora 27 Atomic?
```
It seems like we could benefit from an updated version of @jasonbrooks blog post for Fedora 27:
https://www.projectatomic.io/blog/2014/11/build-your-own-atomic-updates/
And perhaps another edition that covers composing your own F27 Workstation ostree?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/386
6 years
[atomic-wg] Issue #374: go-md2man deployed in osbs can't render tables
by Tomas Tomecek
ttomecek reported a new issue against the project: `atomic-wg` that you are following:
``
Hi, I just tried to build my container image and let osbs generate the `help.1` file. It worked!
The only problem I have is that the present version deployed inside infrastructure does not support rendering tables.
Which means that this help.md page
```
% tools (1) Container Image Pages
% Tomas Tomecek
% September 11th, 2017
# NAME
tools - container with all the management tools you miss in Atomic Host
# DESCRIPTION
You find plenty of well-known tools within this container. Here comes the full list:
| Package | Summary | Executables |
| --------------- | ------------------------------------------------------------------------------------------- | ---------------------------------- |
| bash-completion | Programmable completion for Bash | |
| bc | GNU's bc (a numeric processing language) and dc (a calculator) | /usr/bin/bc |
| | | /usr/bin/dc |
| bind-utils | Utilities for querying DNS name servers | /usr/bin/arpaname |
```
is translated to
```
tools (1) September 11th, 2017 tools (1)
NAME
tools - container with all the management tools you miss in Atomic Host
DESCRIPTION
You find plenty of well-known tools within this container. Here comes the full list:
USAGE
You should invoke this container using atomic command:
$ atomic run f26/tools
```
(yes, the table is missing)
when it should be translated to
```
tools (1) September 11th, 2017 tools (1)
NAME
tools - container with all the management tools you miss in Atomic Host
DESCRIPTION
You find plenty of well-known tools within this container. Here comes the full list:
┌────────────────┬────────────────────────────────────────────┬────────────────────────────────────┐
│Package │ Summary │ Executables │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│bash-completion │ Programmable completion for Bash │ │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│bc │ GNU's bc (a numeric processing language) │ /usr/bin/bc │
│ │ and dc (a calculator) │ │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│ │ │ /usr/bin/dc │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│bind-utils │ Utilities for querying DNS name servers │ /usr/bin/arpaname │
```
I used `golang-github-cpuguy83-go-md2man-1.0.7-1.fc28.x86_64` to do that. Would be awesome to have that version deployed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/374
6 years, 1 month
[atomic-wg] Issue #403: Minimal OSTree/ISO image initiative
by Josh Berkus
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Currently, the main user story for Fedora Atomic Host is as a container infrastructure web host. The OStree ref and ISOs we maintain work well for this user story, and it leads to certain decisions like keeping docker and atomic CLI in the base image (see https://pagure.io/atomic-wg/issue/360).
However, there is a user story we are not satisfying, which is the user who wants a truly minimal install, and is more interested in being able to compose her own ostrees and atomic updates than she is in container orchestration. This is an important user story because we already have demand for it, especially from the IoT sector.
The steps to pursue this would be:
1. work with users to refine and specify the requirements for a "minimal" edition
2. identify and recruit contributors to assist with building it
3. create and publicize new minimal ref and associated tools
Based on my conversations at conferences, the main requests are these:
* reduce the size of the base ostree by stripping things out, preferably to less than 300MB installed.
* auto-rollback on rpm-ostree upgrade reboot fail
* a complete, well-documented toolchain for building and redistributing custom ostrees, based on either the minimal ref or "from scratch".
* support for ARM32 (unlikely at best, but people have asked)
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/403
6 years, 1 month
[atomic-wg] Issue #388: Add Fedora AMIs to govcloud region.
by David Duncan
davdunc reported a new issue against the project: `atomic-wg` that you are following:
``
There are currently no Fedora images in the AWS govcloud region.
To publish images in the govcloud, we must follow the ITAR guidelines.
The AWS GovCloud (United States) region supports United States International Traffic in Arms Regulations (ITAR) compliance. International Traffic in Arms Regulations (ITAR) controls the export of defense-related articles and states that no non-US person can have physical or logical access to the articles stored in the ITAR environment.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/388
6 years, 2 months
[atomic-wg] Issue #351: atomic working group talks/sessions for devconf.cz
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Let's strategize on what sessions we want to submit for devconf this year. Please update the description with a bulleted list of sessions we'd like to submit as well as the status for each session. For example:
- Atomic Host 101 Hands On Lab - Not Yet Submitted - Dusty Mabe
Please add a comment anytime you update the description with a changelog of what you changed in the description.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/351
6 years, 2 months
[atomic-wg] Issue #382: growpart seems to fail on aarch64 atomic host cloud
image
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
I'm not sure why but would like others to confirm/deny that it happens for them with [the image from the first f27 release](https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomi....
```
[root@cloudhost ~]# rpm-ostree status
State: idle
Deployments:
● fedora-atomic:fedora/27/aarch64/atomic-host
Version: 27.1 (2017-11-10 12:02:44)
Commit: da1bd08012699a0aacaa11481d3ed617477858aab0f2ea7300168ce106202255
GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4
[root@cloudhost ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 40G 0 disk
├─sda1 8:1 0 200M 0 part /boot/efi
├─sda2 8:2 0 1G 0 part /boot
└─sda3 8:3 0 4.8G 0 part
└─atomicos-root 253:0 0 4.8G 0 lvm /sysroot
sdb 8:16 0 368K 0 disk
sdc 8:32 0 10G 0 disk
[root@cloudhost ~]# growpart /dev/sda 3
GPT PMBR size mismatch (12582911 != 83886079) will be corrected by w(rite).
attempt to resize /dev/sda failed. sfdisk output below:
| GPT PMBR size mismatch (12582911 != 83886079) will be corrected by w(rite).
| Backup files:
| PMBR (offset 0, size 512): /tmp/growpart.gpxB0y/backup-sda-0x00000000.bak
| GPT Header (offset 512, size 512): /tmp/growpart.gpxB0y/backup-sda-0x00000200.bak
| GPT Entries (offset 1024, size 16384): /tmp/growpart.gpxB0y/backup-sda-0x00000400.bak
|
| Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors
| Units: sectors of 1 * 512 = 512 bytes
| Sector size (logical/physical): 512 bytes / 512 bytes
| I/O size (minimum/optimal): 512 bytes / 512 bytes
| Disklabel type: gpt
| Disk identifier: 5B1DEB7C-8134-464C-8767-0883E53D8B64
|
| Old situation:
|
| Device Start End Sectors Size Type
| /dev/sda1 2048 411647 409600 200M EFI System
| /dev/sda2 411648 2508799 2097152 1G Linux filesystem
| /dev/sda3 2508800 12580863 10072064 4.8G Linux LVM
|
| >>> Script header accepted.
| >>> Script header accepted.
| >>> Script header accepted.
| >>> Script header accepted.
| >>> Script header accepted.
| >>> Script header accepted.
| >>> Created a new GPT disklabel (GUID: 5B1DEB7C-8134-464C-8767-0883E53D8B64).
| /dev/sda1: Created a new partition 1 of type 'EFI System' and of size 200 MiB.
| Partition #1 contains a vfat signature.
| /dev/sda2: Created a new partition 2 of type 'Linux filesystem' and of size 1 GiB.
| Partition #2 contains a ext4 signature.
| /dev/sda3: The last usable GPT sector is 12582878, but 83886079 is requested.
| Failed to add #3 partition: Invalid argument
| Leaving.
|
FAILED: failed to resize
***** WARNING: Resize failed, attempting to revert ******
512+0 records in
512+0 records out
512 bytes copied, 0.0930597 s, 5.5 kB/s
***** Appears to have gone OK ****
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/382
6 years, 2 months