March 2017 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

Fedora 26 Alpha Freeze now in effect
by Kevin Fenzi 05 Apr '17

05 Apr '17

Greetings. we are now in the infrastructure freeze leading up to the Fedora 26 Alpha release. This is a pre-release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 26 Alpha when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2017-03-21 (or later if Alpha slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 1

[PATCH] add compose-utils to bodhi-backend<foo>
by dennis＠ausil.us 31 Mar '17

31 Mar '17

From: Dennis Gilmore <ausil(a)fedoraproject.org> in order to stage the release we need top have compose-utils installed we use the compose-partial-copy script to do teh syncing.The box of choice for staging is bodhi-backend do to the readily available sigul setup so we can sign the CHECKSUM files. https://pagure.io/releng/blob/master/f/scripts/stage-release.sh is the script used to stage the release. Signed-off-by: Dennis Gilmore <ausil(a)fedoraproject.org> --- roles/bodhi2/backend/tasks/main.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml index 4d1d93b..b09ee17 100644 --- a/roles/bodhi2/backend/tasks/main.yml +++ b/roles/bodhi2/backend/tasks/main.yml @@ -25,6 +25,7 @@ - python-alembic - python-scandir - python2-productmd + - compose-utils tags: - packages - bodhi -- 1.8.3.1

3 2

Freeze Break Request: add user to bugzilla fas override
by Kevin Fenzi 31 Mar '17

31 Mar '17

Greeings. There's a use that wants to use their @fedoraproject.org alias in bugzilla so we need to add an exception for them. +1s? kevin -- diff --git a/roles/pkgdb2/files/fas2.py b/roles/pkgdb2/files/fas2.py index 3cd2c4e..c048af8 100644 --- a/roles/pkgdb2/files/fas2.py +++ b/roles/pkgdb2/files/fas2.py @@ -265,6 +265,8 @@ class AccountSystem(BaseClient): 163460: 'besser82(a)fedoraproject.org', # Amit Shah: amit(a)amitshah.net 115389: 'amitshah(a)fedoraproject.org', + # Mark Wielard: fedora(a)wildebeest.org + 102697: 'mjw(a)fedoraproject.org', } # A few people have an email account that is used in owners.list but # have setup a bugzilla account for their primary account system email

3 2

[FBR] Improve permissions for certs that enable container image sync on compose-x86-01
by Adam Miller 30 Mar '17

30 Mar '17

Hello all, I'd like to make the permissions for the container image sync certs to be more restrictive. diff --git a/roles/push-docker/tasks/main.yml b/roles/push-docker/tasks/main.yml index 9baad7f..ed70253 100644 --- a/roles/push-docker/tasks/main.yml +++ b/roles/push-docker/tasks/main.yml @@ -13,11 +13,15 @@ copy: src: "{{private}}/files/koji/{{docker_cert_name}}.cert.pem" dest: "{{docker_cert_dir}}/client.cert" + owner: root + mode: 0600 - name: install docker client key for registry copy: src: "{{private}}/files/koji/{{docker_cert_name}}.key.pem" dest: "{{docker_cert_dir}}/client.key" + owner: root + mode: 0600 - name: start and enable docker service: name=docker state=started enabled=yes Thank you, -AdamM

3 2

Plan for tomorrow's Fedora Infrastructure meeting - 2017-03-30
by Patrick Uiterwijk 29 Mar '17

29 Mar '17

The infrastructure team will be having it's weekly meeting tomorrow, 2017-03-30 at 18:00 UTC in #fedora-meeting on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. Patrick -- This shared document is for the next fedora infrastructure meeting. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2017-03-30) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = Status / information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info Fedora 26 Alpha freeze is on now! - everyone #info Bodhi 2.5.0 beta deployed to staging, release notes available at https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1 - bowlofeggs #info Fedora 26 alpha testing in full swing - kevin #info kojipkgs01/02 updated and rebooted, speed seems better - kevin #info space added to openqa/openqa.stg nfs volumes - kevin #info = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic = Apprentice office hours = #topic Apprentice Open office hours Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or gsetup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #topic Learn about: = Meeting end stuff = #topic Open Floor #endmeeting

1 0

[release] pagure: 2.14.2
by Pierre-Yves Chibon 29 Mar '17

29 Mar '17

Good Morning Everyone, I just cut a new release of pagure: 2.14.2. Here is the changelog * Wed Mar 29 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.14.2-1 - Update to 2.14.2 - Fix a bug in the logic around diff branches in repos This should fix the issue I encountered when pushing 2.14.1 to prod this morning. What would you think about pushing 2.14.2 to prod? Happy hacking, Pierre

3 3

[FBR] Update pagure.io to 2.14.1
by Pierre-Yves Chibon 29 Mar '17

29 Mar '17

Good Morning Everyone, I would like to do two things: - Update pagure in prod to 2.14.1 - Change the PAGURE_AUTH configuration key from 'fas' to 'openid' since legal just cleared the requirement for the FPCA on pagure.io https://lists.fedoraproject.org/archives/list/legal%40lists.fedoraproject.o… For 2.14.1, while not released, the changelog is going to be: - Fix typo for walking the repo when creating a diff of a PR - Have the web-hook use the signed content and have a content-type header - Fix running the tests on jenkins via a couple of fixes to pagure-admin and skipping a couple of tests on jenkins due to the current pygit2/libgit2 situation in epel7 Thoughts on these? Thanks, Pierre

4 7

[release] pagure: 2.14.1
by Pierre-Yves Chibon 29 Mar '17

29 Mar '17

Good Morning Everyone, I just cut a new release of pagure: 2.14.1 Here is the corresponding changelog: * Wed Mar 29 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.14.1-1 - Update to 2.14.1 - Fix typo for walking the repo when creating a diff of a PR - Have the web-hook use the signed content and have a content-type header - Fix running the tests on jenkins via a couple of fixes to pagure-admin and skipping a couple of tests on jenkins due to the current pygit2/libgit2 situation in epel7 This is currently happily running in stg (still missing one +1 to push it to prod). Happy hacking! Pierre

1 0

Freeze break: update/reboot kojipkgs01/02
by Kevin Fenzi 28 Mar '17

28 Mar '17

Greetings. openqa is seeing some very slow downloads from our kojipkgs01/02 machines. I cannot see anything obviously wrong with them, but as a first step I'd like to update them (which would move them from a 4.9.x to a 4.10.x kernel) to see if it's some odd networking stack thing thats already been fixed. The process would be: * Update 01/reboot. * Run playbook to make sure all was set right. * Wait a few hours and make sure 01 is processing ok. * Do the same to 02. This shouldn't result in any downtime (the two are load balanced over haproxy now) and if 01 doesn't process correctly after updating we can limp along on 02 until after freeze. +1s? kevin

3 2

F25 wifi running at 1MB/s
by InvalidPath 28 Mar '17

28 Mar '17

Fellas, I noticed today, while finally getting to use the Fedora side of my work laptop, that my wifi is running at 1MB/s on d Dell XPS 13 9550. According to Dell this model has the Killer AC 1535 wireless chipset so possibly just a driver issue? ➜ .ssh iwconfig wlp2s0 IEEE 802.11 ESSID:"waffle_house" Mode:Managed Frequency:2.447 GHz Access Point: C0:56:27:C4:77:BC Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=58/70 Signal level=-52 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:285 Invalid misc:1819 Missed beacon:0 lo no wireless extensions. virbr0-nic no wireless extensions. macvtap0 no wireless extensions. virbr0 no wireless extensions. vnet0 no wireless extensions. 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Attached is wireless-info.txt, generated from: wget -N -t 5 -T 10 https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info && chmod +x wireless-info && ./wireless-info Found via: https://forums.linuxmint.com/viewtopic.php?t=217258 (Yes I know Mint.. the results for later version of Fedora were severely lacking) Whats odd is that I Put F25 on the wifes Lenovo just Sunday night to resolve this exact issue. Thanks!

2 2

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting
by bowlofeggs＠fedoraproject.org 27 Mar '17

27 Mar '17

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2017-03-28 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/4671/

1 0

[release] pagure: 2.14
by Pierre-Yves Chibon 27 Mar '17

27 Mar '17

Good Morning Everyone, I just cut a new release of pagure: 2.14 Here is the corresponding changelog (pretty long): * Mon Mar 27 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.14-1 - Update to 2.14 - Update the label of the button to comment on a PR (Abhijeet Kasurde) - Make search case insensitive (Vivek Anand) - Improve the debugging on pagure_loadjson - Only link the diff to the file if the PR is local and not remote - Do not log on fedmsg edition to private comment - When deleting a project, give the fullname in the confirmation window - Add link to the FPCA indicating where to sign it when complaining that the user did not sign it (Charelle Collett) - Fix the error: 'Project' object has no attribute 'ci_hook' - Fix input text height to match to button (Abhijeet Kasurde) - Fix the data model to make deleting a project straight forward - Fix searching issues in the right project by including the namespace - When creating the pull-request, save the commit_start and commit_stop - Ensure there is a date before trying to humanize it - Fixing showing tags even when some of them are not formatted as expected - Allow repo user to Take/Drop assignment of issue (Vivek Anand) - Add merge status column in pull requests page (Abhijeet Kasurde) - Allow user with ticket access to edit custom fields, metadata and the privacy flag (Vivek Anand) - Add number of issues in my issues page (Abhijeet Kasurde) - Allow report to filter for a key multiple times - Add the support to delete a report in a project - Fix rendering the roadmap when there are tickets closed without a close date - Fix to show tabs in pull request page on mobile (Abhijeet Kasurde) - Document some existing API endpoints that were missing from the doc - Make issues and pull-requests tables behave in responsive way (Abhijeet Kasurde) - Add option to custom field for email notification (Mark Reynolds) - When resetting the value of a custom field, indicate what the old value was - Add instance wide API token - Move the admin functions out of the UI and into a CLI tool pagure-admin - Do not update the hash in the URL for every tabs on the PR page - Fix heatmap to show current datetime not when when object was created (Smit Thakkar and Vivek Anand) - Do not include watchers in the subscribers of a private issue - Do not highlight code block unless a language is specified - Make getting a project be case insensitive - Do not change the privacy status of an issue unless one is specified - Fix the logic of the `since` keyword in the API (Vivek Anand) - Fix the logic around ticket dependencies - Add reset watch button making it go back to the default (Vivek Anand) - Do not show dates that are None object, instead make them empty strings - Allow filtering tickets by milestones in the API - Allow filtering tickets by priorities in the API - Expand the API to support filtering issues having or not having a milestone - Use plural form for SSH key textfield (Martin Basti) - Support irc:// links in our markdown and adjust the regex - Remove backticks from email subject (Martin Basti) - Adjust the logic when filtering issues by priorities in the API - Remove mentioning if a commit is in master on the front page - Optimize finding out which branches are in a PR or can be - Add required asterisk to Description on new issues (Abhijeet Kasurde) - Fix misc typo in 404 messages (Abhijeet Kasurde) - Add performance git repo analyzer/framework (Patrick Uiterwijk) - Added tip_tricks in doc to document how to pre-fill issues using the url (Eashan) - Document how to filter out for issues having a certain tag in the tips and tricks section - Allow to manually triggering a run of pagure-ci via a list of sentences set in the configuration - Add support for admin API token to pagure-admin - Make clicking on 'Unassigned' filter the unassigned PR as it does for issues - Add Priority column to My Issues page (Abhijeet Kasurde) - Optimize diffing pull-requests - Add a description to the API tokens - Include the fullname in the API output, in the project representation - Add the possibility to edit issue milestone in the API (Martin Basti) - Fix some wording (Till Maas) - Rename "request pull" to pull request (Stanislav Laznicka) - Make tags in issue list clickable (Martin Basti) - Include the priority name in the notification rather than its level - Update the ticket metadata before adding the new comment (if there is one) One important change this release brought: - Patrick and I worked on optimizing the front page of each project and the calls performing diffs. Still some work to be done but this should already help Many thanks to all the contributors who helped making this release! 2.14 is currently happily running in stg, I've already got one small bug which I'll want to fix and maybe cut a 2.14.1. If things look stable, I would like to submit a FBR to push it to stable. Thanks, Pierre

1 1

Weekly Koji Infra Tag Report
by Nobody 26 Mar '17

26 Mar '17

This is a list of packages in the various infrastructure koji tags Please check and make sure there are not any that can be removed/dropped epel6-infra (no matching packages) epel7-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- freeipa-ktutils epel7-infra puiterwijk glusterfs epel7-infra kevin fedmsg-beaker-repoupdate epel7-infra tflink anitya epel7-infra jcline the-new-hotness epel7-infra jcline fedocal epel7-infra pingou python-IPy epel7-infra kevin python-robosignatory epel7-infra puiterwijk pdc-updater epel7-infra ralph python-pdc epel7-infra ralph mirrormanager2 epel7-infra puiterwijk blockerbugs epel7-infra tflink python-django-jsonfield epel7-infra ralph f23-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- libphutil, f23-infra tflink arcanist, f23-infra tflink phabricator f23-infra tflink phabricator-extension-ipsilonauth f23-infra tflink libphutil f23-infra tflink arcanist f23-infra tflink f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin phabricator-extension-oauth f24-infra tflink python-twill f24-infra codeblock stickynotes2modernpaste f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-skin-fedora f24-infra puiterwijk mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk phabricator f24-infra tflink mediawiki-Lockdown f24-infra kevin libphutil f24-infra tflink arcanist f24-infra tflink mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python-flask-testing f25-infra codeblock modern-paste f25-infra codeblock python-coveralls f25-infra codeblock mdapi f25-infra pingou basset f25-infra puiterwijk mediawiki-FedoraBadges f25-infra kevin mediawiki-Lockdown f25-infra kevin mediawiki-RSS f25-infra kevin mediawiki-openid f25-infra kevin plus-plus-service f25-infra pingou python-pdc f25-infra ralph python-django-cors-headers f25-infra ralph python-django-rest-framework-composed-permissions f25-infra ralph patternfly1 f25-infra ralph fas f25-infra kevin libphutil, f25-infra tflink arcanist, f25-infra tflink phabricator f25-infra tflink phabricator-extension-ipsilonauth f25-infra tflink libphutil f25-infra tflink arcanist f25-infra tflink python-twill f25-infra codeblock stickynotes2modernpaste f25-infra codeblock mediawiki-skin-fedora f25-infra kevin f26-infra (no matching packages) f27-infra (no matching packages)

1 0

Multiple 404 not founds on SOP links
by InvalidPath 25 Mar '17

25 Mar '17

While looking for SOP's to inspect I've stumbled across It seems the correct url is: https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/sop… The link from https://fedoraproject.org/wiki/Category:Infrastructure_SOPs might be incorrect as: https://infrastructure.fedoraproject.org/infra/docs/ i.e.: https://fedoraproject.org/wiki/Content_Hosting_Infrastructure_SOP fails here: https://infrastructure.fedoraproject.org/infra/docs/contenthosting.rst https://fedoraproject.org/wiki/SELinux_Infrastructure_SOP fails here: https://infrastructure.fedoraproject.org/infra/docs/selinux.rst https://fedoraproject.org/wiki/Outage_Infrastructure_SOP fails here: https://infrastructure.fedoraproject.org/infra/docs/outage.rst I'm thinking either someone typo'd teh path to add a second 'doc' or possibly the site side didn't get the url updated. In either case, things be broken :)

3 5

Pull Request Troubles
by InvalidPath 24 Mar '17

24 Mar '17

Hey all, So last night I ran into an issue performing a PR to infra-docs. I did fork it, was able to clone it locally.. add my new files but upon pushing I get an error stating: error: The requested URL returned error: 403 Forbidden while accessing https://pagure.io/forks/skeer/infra-docs.git Google results showed this is typically an issue on the destinations side, it was late so I decided to wait and retry today. A few hours ago, same error. Anyone run into this before? Last night I did initially try to git clone using the ssh link but that failed.. Linuxmodder suggested to use the https url which worked just fine.

2 2

FBR, check_modulemd check for taskotron!
by Ralph Bean 24 Mar '17

24 Mar '17

Hey all, I'm seeking a FBR to enable a new taskotron check in production. It's not urgent (nothing will be blocked without it). It would just be nice to have. Tim Flink says in channel that "it's not a risky or major change". Backing it out would involve reverting that conditional in trigger_rules.yml and re-running the playbook to disable it. Anyone +1 on this? diff --git a/inventory/group_vars/taskotron-prod b/inventory/group_vars/taskotron-prod index 284d069..d75b0e3 100644 --- a/inventory/group_vars/taskotron-prod +++ b/inventory/group_vars/taskotron-prod @@ -24,6 +24,7 @@ grokmirror_repos: - { name: fedoraqa/abicheck, url: 'https://pagure.io/task-abicheck.git'} - { name: fedoraqa/rpmgrill, url: 'https://bitbucket.org/fedoraqa/task-rpmgrill.git'} - { name: fedoraqa/python-versions, url: 'https://github.com/fedora-python/task-python-versions'} + - { name: fedoraqa/check_modulemd, url: 'https://github.com/fedora-modularity/check_modulemd'} grokmirror_user: grokmirror grokmirror_default_branch: master diff --git a/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 b/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 index 8994e9a..f939c1d 100644 --- a/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 +++ b/roles/taskotron/taskotron-trigger/templates/trigger_rules.yml.j2 @@ -33,11 +33,10 @@ do: - {tasks: [upgradepath]} {% endif %} -{% if deployment_type in ['dev', 'stg'] %} + - when: {message_type: DistGitCommit, namespace: modules} do: - {tasks: [check_modulemd]} -{% endif %} {% if deployment_type in ['dev'] %} - when:

3 3

Plan for tomorrow's Fedora Infrastructure meeting - 2017-03-23
by Kevin Fenzi 22 Mar '17

22 Mar '17

The infrastructure team will be having it's weekly meeting tomorrow, 2017-03-23 at 18:00 UTC in #fedora-meeting on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. kevin -- This shared document is for the next fedora infrastructure meeting. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2017-03-23) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson #topic New folks introductions = Status / information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info Fedora 26 Alpha freeze is on now! - everyone #info Bodhi 2.5.0 beta deployed to staging, release notes available at https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1 - bowlofeggs #info Fedora 26 alpha testing in full swing - kevin #info = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic OpenShift trial - kevin #topic = Apprentice office hours = #topic Apprentice Open office hours Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or gsetup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #topic Learn about: = Meeting end stuff = #topic Open Floor #endmeeting

1 0

[PATCH] rename releng group
by dennis＠ausil.us 22 Mar '17

22 Mar '17

From: Dennis Gilmore <ausil(a)fedoraproject.org> we renamed the releng group in fas to releng-team but in the process forgot to update the bodhi cnfigs, this change will make sure that members of the releng-team group in fas will ahve full perms in bodhi Signed-off-by: Dennis Gilmore <ausil(a)fedoraproject.org> --- roles/bodhi2/base/templates/production.ini.j2 | 4 ++-- roles/bodhi2/base/templates/staging.ini.j2 | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2 index 8d05bc0..5df5af4 100644 --- a/roles/bodhi2/base/templates/production.ini.j2 +++ b/roles/bodhi2/base/templates/production.ini.j2 @@ -378,10 +378,10 @@ buildroot_overrides.expire_after = 1 # When a user logs in, bodhi will look for any of these groups and associate # # them with the user. They will then appear as the users effective principals in # the format "group:groupname" and can be used in Pyramid ACE's. -important_groups = proventesters provenpackager releng security_respons packager bodhiadmin virtmaint-sig kde-sig eclipse-sig infra-sig gnome-sig python-sig robotics-sig qa-tools-sig nodejs-sig lxqt-sig astro-sig +important_groups = proventesters provenpackager releng-team security_respons packager bodhiadmin virtmaint-sig kde-sig eclipse-sig infra-sig gnome-sig python-sig robotics-sig qa-tools-sig nodejs-sig lxqt-sig astro-sig # Groups that can push updates for any package -admin_packager_groups = provenpackager releng security_respons +admin_packager_groups = provenpackager releng-team security_respons # User must be a member of this group to submit updates mandatory_packager_groups = packager diff --git a/roles/bodhi2/base/templates/staging.ini.j2 b/roles/bodhi2/base/templates/staging.ini.j2 index faa3b60..8e1fe0e 100644 --- a/roles/bodhi2/base/templates/staging.ini.j2 +++ b/roles/bodhi2/base/templates/staging.ini.j2 @@ -348,10 +348,10 @@ buildroot_overrides.expire_after = 1 # When a user logs in, bodhi will look for any of these groups and associate # # them with the user. They will then appear as the users effective principals in # the format "group:groupname" and can be used in Pyramid ACE's. -important_groups = proventesters provenpackager releng security_respons packager bodhiadmin virtmaint-sig kde-sig eclipse-sig infra-sig gnome-sig python-sig robotics-sig +important_groups = proventesters provenpackager releng-team security_respons packager bodhiadmin virtmaint-sig kde-sig eclipse-sig infra-sig gnome-sig python-sig robotics-sig # Groups that can push updates for any package -admin_packager_groups = provenpackager releng security_respons +admin_packager_groups = provenpackager releng-team security_respons # User must be a member of this group to submit updates mandatory_packager_groups = packager -- 1.8.3.1

3 2

FBR: Autocloud to exclude testing of aarch64 images
by Sayan Chowdhury 22 Mar '17

22 Mar '17

I need to remove the testing of the aarch64 from Autocloud. Here is the PR[1] to the change. I will merge the PR and deploy a hotfix if the PR is approved. Can I get +1s? [1] https://github.com/kushaldas/autocloud/pull/56 -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization!

3 2

Freeze Break Request: fix iscsi/mpath
by Kevin Fenzi 22 Mar '17

22 Mar '17

Greetings. This thursday (2017-03-23) there's going to be some upgrades done on our netapp storage. These upgrades should not cause any outages if everything was working as expected, but there's an issue: A number of our machines are logged into iscsi luns, but not properly multipathing that connection, which means that those machines could see an outage to the iscsi storage since they don't have the redundant paths. However, we are not using iscsi as widely as we used to either, so a number of these machines are logged in, but don't otherwise use the storage at all. So, I'd like to get a freeze break to do the following: 1. Wait until our f26rc2 is composed (which might mean waiting until tomorrow). 2. Apply the following ansible patch: diff --git a/playbooks/groups/virthost.yml b/playbooks/groups/virthost.yml index e3d673f..e53d540 100644 --- a/playbooks/groups/virthost.yml +++ b/playbooks/groups/virthost.yml @@ -22,7 +22,7 @@ - hosts - fas_client - collectd/base - - { role: iscsi_client, when: datacenter == "phx2" } + - { role: iscsi_client, when: inventory_hostname.startswith(('bvirthost','buildvmhost')) } - sudo - { role: openvpn/client, when: datacenter != "phx2" } - virthost This will restrict the iscsi client setup to only bvirthost and buildvmhost machines. Those are the only ones that _should_ be using this storage (but see below): 3. Run ansible commands over the non bvirthost/buildvmhost machines to do a 'iscsi logout', disable iscsi and multipathd services and remove the /var/lib/iscsi/nodes/* files. 4. Re-provision docker-registry02.stg.phx2.fedoraproject.org and loopabull01.stg.phx2.fedoraproject.org that were provisioned on the iscsi storage and make them use local storage. 5. Sadly, that leaves bvirthost01/02/03 still not working right. However, they use 0 things from the iscsi storage, so we can fix them after freeze. That should hopefully do it. ;) +1s? kevin

3 2

SSH to Bastion
by InvalidPath 22 Mar '17

22 Mar '17

I had to change my ssh key, how long does replication take before I can access bastion? Thanks! Ben

4 6

Bodhi 2.5.0 beta deployed to stg
by Randy Barlow 21 Mar '17

21 Mar '17

Hello! After a lot of wrestling I got a Bodhi 2.5.0 beta deployed to staging. We have a stakeholder's meeting in 7.5 days so I wanted to have a new version to discuss there and here it is. This release has some exciting new features and bug fixes[0], the most exciting of which is a theme redesign done by Ryan Lerch. He put particular focus on the update page, and I think it greatly increases the usability of the page by putting the most common information you want to see first. For an example, check out a kernel update[1]. Another neat thing about 2.5.0 is that Bodhi is now hosting its own docs at /docs. The UI doesn't advertise this link yet, though I do have an issue tracking that[3]. Obviously I don't plan to deploy this to production until after the freeze, but I thought it would be good to get it deployed to stg before the stakeholder's meeting next week and I thought it would be good to get the new design "out there" sooner rather than later as well. [0] https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1 [1] https://bodhi.stg.fedoraproject.org/updates/FEDORA-2017-e8e717e2b7 [2] https://bodhi.stg.fedoraproject.org/docs/ [3] https://github.com/fedora-infra/bodhi/issues/1321

4 8

Meeting Agenda Item: Introduction Ivan Garcia
by Ivan Garcia 21 Mar '17

21 Mar '17

Hello! My name is Ivan Garcia, my irc nic is cyberworm54. I've been here before but due to some time constraints, I needed to go idle for a while. Now I have free time that I can invest on this wonderful community! I am Linux Engineer currently working for Salesforce, I also hold/held a RHCE/RHCSA. I have a broad and in depth knowledge on rhel,fedora,centos and openstack. When it comes to programming and scripting bash and python are my go to's. I am an avid chef user and since I know the team uses ansible, I really would like to get a grip on ansible as I haven't worked with it before. I can bring some useful sysadmin skills to the table when it comes to openstack and rhel/centos . I am really looking forward to this! Have a great night/day !

1 0

FBR: Bodhi should stop sending error emails on success, and should start sending error emails on error
by Randy Barlow 20 Mar '17

20 Mar '17

There is a 1-character diff patch on fedmsg-atomic-composer that I'd like to apply to production to stop us from getting error e-mails whenever Bodhi succeeds: https://github.com/fedora-infra/fedmsg-atomic-composer/pull/21 Basically, the logic is exactly backwards on whether the stderr should be considered an error or info based on the exit code. If the FBR is approved I will also need someone to review the PR, and then I'll just make an upstream release and get it deployed.

3 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2017