hhorak reported a new issue against the project: `atomic-wg` that you are following: `` I'm trying to build a container, but it always fails. I'm trying from more repos, e.g.: https://koji.fedoraproject.org/koji/taskinfo?taskID=26340825
Seeing: container_linux.go:247: starting container process caused "process_linux.go:364: container init caused "rootfs_linux.go:54: mounting \"/var/lib/origin/openshift.local.volumes/pods/e2e09f0d-3f04-11e8-aa8d-5254004f20fd/volumes/kubernetes.io~secret/builder-token-01lfv\" to rootfs \"/var/lib/docker/devicemapper/mnt/777d7851d75b3ecc837d1cb61b9fbc9dd5beb379e66d7552b1f2eb6da2fbff8e/rootfs\" at \"/var/lib/docker/devicemapper/mnt/777d7851d75b3ecc837d1cb61b9fbc9dd5beb379e66d7552b1f2eb6da2fbff8e/rootfs/run/secrets/kubernetes.io/serviceaccount\" caused \"mkdir /var/lib/docker/devicemapper/mnt/777d7851d75b3ecc837d1cb61b9fbc9dd5beb379e66d7552b1f2eb6da2fbff8e/rootfs/run/secrets/kubernetes.io: read-only file system\"""
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
dustymabe added a new comment to an issue you are following: `` @cverna do you mind taking a look? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
The issue: `Building of containers does not work` of project: `atomic-wg` has been assigned to `cverna` by dustymabe.
The issue: `Building of containers does not work` of project: `atomic-wg` has been reset by smilner.
smilner added a new comment to an issue you are following: `` This looks like an issue with OSBS. Is there a queue/issue space for reporting problems for that service ... or does the Atomic Working Group usually front these? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
cverna added a new comment to an issue you are following: `` I am on it .
This looks like an issue with OSBS. Is there a queue/issue space for reporting problems for that >service ... or does the Atomic Working Group usually front these?
It is better to open these in the fedora-infra, there is an OSBS tag.
I have opened https://pagure.io/fedora-infrastructure/issue/6861 to track this issue.
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
The status of the issue: `Building of containers does not work` of project: `atomic-wg` has been updated to: Closed as Duplicate by cverna.
dustymabe added a new comment to an issue you are following: ``
I am on it .
This looks like an issue with OSBS. Is there a queue/issue space for reporting problems for that >service ... or does the Atomic Working Group usually front these?
It is better to open these in the fedora-infra, there is an OSBS tag. I have opened https://pagure.io/fedora-infrastructure/issue/6861 to track this issue.
Yeah. the problem is that fedora infra (and releng) repos are quite high volume and it can be hard as a user (or even as someone who tries to help manage existing problems in the Atomic* space) to keep up with them. I typically open an issue here and then strategize about the best way to solve the problem. If it involves including infra/releng/websites/fesco/qa/etc then I open a ticket there too and report back here.
It's a hard problem to solve. I honestly wish pagure had the ability to have tickets depend on other tickets in other repos etc..
If this is a bad practice then we can revisit it, but it's been what works best for us so far. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
puiterwijk added a new comment to an issue you are following: `` This issue is now fixed on our infra (again), but maybe the underlying issue is something that the atomic WG should look at:
```` puiterwijk | Short summary: if a special directory exists on the container host (osbs-node*), docker will mount that directory in /var/run/secrets for RHEL | subscription manager certificates. But that conflicts directly with the attempts to mount service account secrets into /run/secrets/<uuid> | that Kubernetes/Openshift tries to do puiterwijk | Basically, deleting /usr/share/rhel/secrets will fix this, because that avoids the Fedora/RH docker to mount that into /run/secrets ```` ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
The status of the issue: `Building of containers does not work` of project: `atomic-wg` has been updated to: Open by puiterwijk.
puiterwijk added a new comment to an issue you are following: `` (note that OSBS production is currently on Openshift Origin 3.6: https://koji.fedoraproject.org/koji/buildinfo?buildID=953622) ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
hhorak added a new comment to an issue you are following: `` It looks like the main problem is fixed, thanks a lot! However, the build still fails in some late step:
ERROR - one or more exit plugins failed: plugin 'koji_tag_build' raised an exception: TypeError('Invalid type unicode for argument 1',)
https://koji.fedoraproject.org/koji/taskinfo?taskID=26445345
Although it doesn't prevent the image to be available in the candidate registry. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
hhorak added a new comment to an issue you are following: `` Still seeing the same issue.. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
cverna added a new comment to an issue you are following: `` On 25 April 2018 at 08:34, Honza Horak pagure@pagure.io wrote:
hhorak added a new comment to an issue you are following: `` Still seeing the same issue.. ``
I ll look at it, today.
Sorry about that
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
cverna added a new comment to an issue you are following: `` So we have the following error ``` 2018-04-18 19:59:04,058 platform:- - atomic_reactor.plugin - INFO - running plugin instance with args: '{u'kojihub': u'https://koji.fedoraproject.org/kojihub', u'koji_principal': u'osbs/osbs.fedoraproject.org@FEDORAPROJECT.ORG', u'koji_keytab': u'FILE:/etc/krb5.osbs_osbs.fedoraproject.org.keytab', u'target': u'f28-container-candidate'}' 2018-04-18 19:59:04,059 platform:- - atomic_reactor.koji_util - INFO - Using Kerberos for Koji authentication 2018-04-18 19:59:04,471 platform:- - atomic_reactor.plugin - DEBUG - Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/atomic_reactor/plugin.py", line 238, in run plugin_response = plugin_instance.run() File "/usr/lib/python2.7/site-packages/atomic_reactor/plugins/exit_koji_tag_build.py", line 88, in run session = create_koji_session(self.kojihub, self.koji_auth) File "/usr/lib/python2.7/site-packages/atomic_reactor/koji_util.py", line 112, in create_koji_session koji_login(session, **auth_info) File "/usr/lib/python2.7/site-packages/atomic_reactor/koji_util.py", line 92, in koji_login result = session.krb_login(**kwargs) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2165, in krb_login sprinc = krbV.Principal(name=self._serverPrincipal(cprinc), context=ctx) TypeError: Invalid type unicode for argument 1 ```
This is because the kerberos Principal is passed as an unicode by atomic-reactor and the python-krbV module is expecting a string.
I ll wait for the end of the infra freeze (next week) to test a patch and submit it to upstream. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
puiterwijk added a new comment to an issue you are following: `` @cverna: https://github.com/projectatomic/atomic-reactor/pull/860 Me and Adam had a patch written for that, which was in our RPMs before, did that backport get lost? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
puiterwijk added a new comment to an issue you are following: `` Also, it shouldn't even get to the krbV codepaths, as that means that gssapi failed. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
cverna added a new comment to an issue you are following: `` @puiterwijk Hum, it looks like I removed the patch[0] when upgrading to atomic-reactor 1.6.29 not sure why tho :disappointed:
[0] - https://src.fedoraproject.org/rpms/atomic-reactor/c/fb1219f7abf2bbda6648da59... ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
cverna added a new comment to an issue you are following: ``
Also, it shouldn't even get to the krbV codepaths, as that means that gssapi failed.
Looking at koji's code, gssapi fails silently, there is a debug statement [here](https://pagure.io/koji/blob/master/f/koji/__init__.py#_2123) but I am not how I would get that in atomic-reactor ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
puiterwijk added a new comment to an issue you are following: `` If you make sure that python-krbV is not available, it goes into the "else:", which raises it as an exception. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
cverna added a new comment to an issue you are following: `` @hhorak I have rebuilt the buildroot container, if you could try to build your container again to see if the build works.
Thanks ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
hhorak added a new comment to an issue you are following: `` I've successfully built container today, thanks! ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455
The status of the issue: `Building of containers does not work` of project: `atomic-wg` has been updated to: Closed as Fixed by cverna.
atomic@lists.fedoraproject.org
-
Clement Verna -
Dusty Mabe
-
Honza Horak
-
Patrick "マルタインアンドレアス" Uiterwijk
-
Steve Milner