[atomic-wg] Issue #252 `Fix rawhide ISO`
by Colin Walters
walters reported a new issue against the project: `atomic-wg` that you are following:
``
https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/...
```
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/pylorax/ltmpl.py", line 56, in parse
textbuf = template.render(**variables)
File "/usr/lib/python3.6/site-packages/mako/template.py", line 462, in render
return runtime._render(self, self.callable_, args, data)
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 838, in _render
**_kwargs_for_callable(callable_, data))
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 873, in _render_context
_exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 899, in _exec_template
callable_(context, *args, **kwargs)
TypeError: render_body() missing 1 required positional argument: 'root'
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/252
6 years, 10 months
Requesting freeze exception for atomic in F26 to drop rpm-build
deps
by Jonathan Lebon
Hi,
If I understand correctly, in its current state, F26 AH will
be shipping with the atomic package which added the
rpm-build deps. The update that removes it again is blocked
in testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-ac1919a04b
Double-checking the current state:
$ ostree remote add fedora-26 --no-gpg-verify https://kojipkgs.fedoraproject.org/atomic/26/
$ ostree pull fedora-26 --subpath=/usr/share/rpm --depth=0 fedora/26/x86_64/atomic-host
$ ostree checkout -U --subpath=/usr/share/rpm fedora-26:fedora/26/x86_64/atomic-host tmp/rpmdb-26
$ rpm -qa --dbpath $PWD/tmp/rpmdb-26 | grep -E '(rpm-build|gdb)'
gdb-headless-7.12.50.20170226-4.fc26.x86_64
rpm-build-libs-4.13.0.1-4.fc26.x86_64
rpm-build-4.13.0.1-4.fc26.x86_64
gdbm-1.13-1.fc26.x86_64
If this is what the F26 AH deliverables will be based on,
then would it be possible to justify a freeze exception out
of this? It's a pretty big wart on a new AH release, esp.
since the motto is that we're a streamlined OS, though it's
obviously not a critical release blocker.
6 years, 10 months
Atomic WG Meeting Minutes 2017-05-24
by Jerry Zhang
Summary:
https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg...
Full logs:
https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg...
Meeting started by yzhang at 17:02:46 UTC (full logs
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>
).
Meeting summary
1. Roll Call (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:02:53)
2. Action items from last meeting (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:05:27)
1. ACTION: jberkus to ask mattdm about how to get PRD approved (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:07:10)
2. jbrooks opened a PR for a blog post about support policy in the
future for atomic
https://github.com/projectatomic/atomic-site/pull/434 (dustymabe
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:07:36)
3. https://pagure.io/cloud-sig/issue/138 (dustymabe
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:08:32)
4. dustymabe migrated all remaining cloud-base tickets to the
cloud-sig repo: https://pagure.io/cloud-sig/issue/138 (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:08:44)
5. https://pagure.io/atomic-wg/issue/275 (dustymabe
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:09:00)
6. https://pagure.io/atomic-wg/issue/275 (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:10:06)
3. Enforce ENV usage as a requirement for release label (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:11:13)
1. https://pagure.io/atomic-wg/issue/277 (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:11:24)
2. ACTION: maxamillion to update container guidelines to enforce ENV
and label maintainer usage https://pagure.io/atomic-wg/issue/277 (
yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:17:11)
4. fedimg: don't use 'builder' instance for uploading AMIs (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:17:45)
1. https://pagure.io/atomic-wg/issue/269 (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:17:59)
5. clarify policy on atomic host support for older Fedora "number"
releases (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:19:59)
1. https://pagure.io/atomic-wg/issue/228 (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:20:03)
2. please review jbrook's blog post on this topic:
https://github.com/projectatomic/atomic-site/pull/434 (dustymabe
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:20:34)
3. https://fedoraproject.org/wiki/Atomic/PRD#Updates (jbrooks
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:23:05)
4. https://fedoraproject.org/wiki/Atomic (jbrooks
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:29:29)
5. ACTION: dustymabe to propose a VFAD for wiki and docs discussion (
yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:40:12)
6. open floor (yzhang
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:41:22)
1. ACTION: dusty and roshi to plan test day for coming weeks (
dustymabe
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:45:18)
2. https://www.flocktofedora.org/ (jberkus
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:46:34)
3. ACTION: everyone to discuss flock proposals next week (jberkus
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:48:57)
4. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f4ccc7cb91 this
runc needs a bit more karma (jbrooks
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:52:25)
5. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f4ccc7cb91 karma
please (jbrooks
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>,
17:54:17)
Meeting ended at 17:57:43 UTC (full logs
<https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomi...>
).
Action items
1. jberkus to ask mattdm about how to get PRD approved
2. maxamillion to update container guidelines to enforce ENV and label
maintainer usage https://pagure.io/atomic-wg/issue/277
3. dustymabe to propose a VFAD for wiki and docs discussion
4. dusty and roshi to plan test day for coming weeks
5. everyone to discuss flock proposals next week
Action items, by person
1. dustymabe
1. dustymabe to propose a VFAD for wiki and docs discussion
2. jberkus
1. jberkus to ask mattdm about how to get PRD approved
3. maxamillion
1. maxamillion to update container guidelines to enforce ENV and
label maintainer usage https://pagure.io/atomic-wg/issue/277
4. roshi
1. dusty and roshi to plan test day for coming weeks
People present (lines said)
1. yzhang (113)
2. dustymabe (85)
3. roshi (66)
4. jberkus (42)
5. jbrooks (34)
6. maxamillion (28)
7. zodbot (15)
8. miabbott (10)
9. nzwulfin (3)
6 years, 10 months
[atomic-wg] Issue #181 `Vagrant cannot create synced folder`
by Pagure
jorti reported a new issue against the project: `atomic-wg` that you are following:
``
I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir.
```
$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: mail-server_default
==> default: -- Domain type: kvm
==> default: -- Cpus: 1
==> default: -- Memory: 512M
==> default: -- Management MAC:
==> default: -- Loader:
==> default: -- Base box: fedora/25-atomic-host
==> default: -- Storage pool: default
==> default: -- Image:
/var/lib/libvirt/images/mail-server_default.img (41G)
==> default: -- Volume Cache: default
==> default: -- Kernel:
==> default: -- Initrd:
==> default: -- Graphics Type: vnc
==> default: -- Graphics Port: 5900
==> default: -- Graphics IP: 127.0.0.1
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: cirrus
==> default: -- Video VRAM: 9216
==> default: -- Keymap: en-us
==> default: -- TPM Path:
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- Command line :
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for SSH to become available...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Configuring and enabling network interfaces...
==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
mkdir: cannot create directory ‘/vagrant’: Operation not permitted
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/181
6 years, 10 months
