davdunc reported a new issue against the project: `atomic-wg` that you are following:
``
I have made arrangements with Mattdm to host Marketplace AMIs of F27 in the AWS Marketplace. These will be hosted by me as a member of the Fedora community. This allows us to get around certain legal issues that have heretofore prevented the images hosting.
* Need Fedora Marketing to assist with writeup for the listing.
* TODO F27 submission prior to release date (there is a security audit)
Account number for Marketplace deployment is 662243699625. This is legally separate from the FAS managed account.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/339
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
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Since we moved to a new model where we are only using overlay2 on top of the root filesystem (default), we need to automatically extend the root filesystem to fill up the root VG by default, unless the user modifies docker-storage-setup config file and tells us to do otherwise.
I opened a [PR](https://github.com/projectatomic/container-storage-setup/pull/258) for this functionality to be added to container-storage-setup. The new version of that rpm is in updates-testing. We'll update the kickstarts to properly take advantage of this soon.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/343
dimtheo reported a new issue against the project: `atomic-wg` that you are following:
``
hello
using this image Fedora-Atomic-26-20170821.0.x86_64.qcow2 with magnum to deploy a kube cluster , i found out some issues with networking and im not sure if there is something wrong with the image or not.
first of all if i just create a single instance using the above image and i ssh into it , networking is fine and fast as it should be. The problems begin when i use that image with magnum to deploy a cluster then the networking become so slow to the point where its useless. It takes 25 min to docker pull even the smallest images from docker hub , it will take 10 seconds to let you ssh from one minion to another etc .
I can verify there are no networking problems in the openstack cloud and all other instances outside of kubernetes have no such problems .
there is plenty of ram and disk space available as well in the master and 2 minions as well
so i would like to ask if someone else has experienced a similar issue ?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/335
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
These were removed as part of the [remove of kube](https://pagure.io/fedora-atomic/c/7d50906d91097f6eef4af91a6f693b98c57a9b91?branch=master). They were originally added [here](https://pagure.io/fedora-atomic/c/a1f7373f66d10150349aa7e1869c22ad9ebb78c8?branch=master) as a result of [this BZ](https://bugzilla.redhat.com/show_bug.cgi?id=1303546)
We need to determine if tools like openshift-ansible depend on them being in the host for gluster storage to work or if it all works inside containers for them.
A longer term approach would be to get package layering support in an ansible module so that we could worry about stuff like this less.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/333
walters reported a new issue against the project: `atomic-wg` that you are following:
``
In https://github.com/projectatomic/rpm-ostree/pull/1003 I discovered that `/etc/selinux/config` starts out modified; this is actually a sort of anaconda/selinux-policy interaction bug. It looks like we can work around it by simply removing `selinux --enforcing` from our kickstart which will use the defaults.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/341
mattdm reported a new issue against the project: `atomic-wg` that you are following:
``
Knock on wood, the beta is getting signed-off on tomorrow. I'll need to get a press release and the Fedora announcement ready. What do we want to say about Atomic Host?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/342
goern added a new comment to an issue you are following:
``
any updates?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/217
dustymabe added a new comment to an issue you are following:
``
> This has been applied, and should now be fixed.
thanks patrick. will leave open until our next atomic host release email goes out and makes it to the list.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/325