Fedora-Cloud-33-20210324.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210323.0):

ID: 827462  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/827462
ID: 827469  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/827469

Passed openQA tests: 6/7 (aarch64), 6/7 (x86_64)

New passes (same test not passed in Fedora-Cloud-33-20210323.0):

ID: 827465  Test: aarch64 Cloud_Base-qcow2-qcow2 base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/827465
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: is the license AGPL 3.0 useable in terms of distributing the software as a package?

[Marius Schwarz]

Am 24.03.21 um 02:44 schrieb Kevin Kofler via devel:

Kevin Kofler via devel wrote:

This is the reason why MBROLA is not in Fedora. MBROLA is not new. It is
much older than the 2-year-old GitHub project. The license of the voices
has always been the blocker.

PS: This was already discussed when the GitHub project was created in 2019:
https://lists.fedoraproject.org/archives/list/le...@lists.fedoraproject.org/thread/MAAY3B6KUVAV7YRNUSW7G6672WUAFWYJ/
with the same conclusion. (It is not acceptable for Fedora, unfortunately.)

And, a small correction: according to the Wikipedia article:
https://en.wikipedia.org/wiki/MBROLA
the license of the software itself did actually change from a non-free
license to the AGPL when the project was imported into GitHub. But
unfortunately, the license of the data files is still a blocker, sorry.



A very helpfull explanation. Thanks.

Best regards,
Marius Schwarz

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-32-20210324.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-32-20210323.0):

ID: 827476  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/827476
ID: 827483  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/827483

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

OUTAGE NOTICE: 2021-03-24 1030 UTC - 2021-03-25 2000 UTC Approx

[Aoife Moloney]

Hi all,

The outage to facilitate the migration and deployment of the new Fedora
Accounts system has begun.
This outage is due to last until approx 2000 UTC tomorrow.

Please check status.fedoraproject.orghttps://status.fedoraproject.org/
 for affected services & outage ticket for
more details https://pagure.io/fedora-infrastructure/issue/9747
Details of what to expect during this outage period can be found here
https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/message/JGVRX7CSXSDJ2MV5TJNYPCGVWWI5XSNB/

The team working on this deployment can be contacted on freenode channel
#fedora-aaa if you run into any serious issues.

Thank you for your patience and understanding over the next two days while
we complete this work, and we hope you experience minimal disruption.


Kindest regards & many thanks,
Aoife & The Fedora Accounts Team

-- 

Aoife Moloney

Product Owner

Community Platform Engineering Team

Red Hat EMEA 

Communications House

Cork Road

Waterford

___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: devel Digest, Vol 205, Issue 210

[hanh le]

Ok

Vào 18:00, Th 4, 24 thg 3, 2021  đã
viết:

> Send devel mailing list submissions to
> devel@lists.fedoraproject.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> devel-requ...@lists.fedoraproject.org
>
> You can reach the person managing the list at
> devel-ow...@lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
> Today's Topics:
>
>1. Fedora-Cloud-33-20210324.0 compose check report
>   (Fedora compose checker)
>2. [Test-Announce] Fedora Linux 34 Beta Release Announcement
>   (Mohan Boddu)
>3. Re: is the license AGPL 3.0 useable in terms of distributing the
> software as a package?
>   (Marius Schwarz)
>4. Fedora-Cloud-32-20210324.0 compose check report
>   (Fedora compose checker)
>5. OUTAGE NOTICE: 2021-03-24 1030 UTC - 2021-03-25 2000 UTC Approx
>   (Aoife Moloney)
>
>
> --
>
> Date: Wed, 24 Mar 2021 07:38:46 + (GMT)
> From: Fedora compose checker 
> Subject: Fedora-Cloud-33-20210324.0 compose check report
> To: t...@lists.fedoraproject.org, devel@lists.fedoraproject.org
> Message-ID:
> <20210324073846.3da8730a2...@bastion01.iad2.fedoraproject.org>
>
> No missing expected images.
>
> Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
> (Tests completed, but using a workaround for a known bug)
>
> Old soft failures (same test soft failed in Fedora-Cloud-33-20210323.0):
>
> ID: 827462  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
> URL: https://openqa.fedoraproject.org/tests/827462
> ID: 827469  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
> URL: https://openqa.fedoraproject.org/tests/827469
>
> Passed openQA tests: 6/7 (aarch64), 6/7 (x86_64)
>
> New passes (same test not passed in Fedora-Cloud-33-20210323.0):
>
> ID: 827465  Test: aarch64 Cloud_Base-qcow2-qcow2 base_update_cli@uefi
> URL: https://openqa.fedoraproject.org/tests/827465
> --
> Mail generated by check-compose:
> https://pagure.io/fedora-qa/check-compose
>
> --
>
> Date: Tue, 23 Mar 2021 10:02:20 -0400
> From: Mohan Boddu 
> Subject: [Test-Announce] Fedora Linux 34 Beta Release Announcement
> To: test-annou...@lists.fedoraproject.org,
> devel-annou...@lists.fedoraproject.org,
> annou...@lists.fedoraproject.org
> Message-ID:
>  rynfse5b3ldzzr7w25uuhyacj28ndsqav...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Fedora Linux 34 Beta Released
> --
>
> The Fedora Project is pleased to announce the immediate availability
> of Fedora 34 Beta, the next step towards our planned Fedora 34 release
> at the end of April.
>
> Download the prerelease from our Get Fedora site:
> * Get Fedora 34 Beta Workstation:
> https://getfedora.org/workstation/download/
> * Get Fedora 34 Beta Server: https://getfedora.org/server/download/
> * Get Fedora 34 IoT: https://getfedora.org/iot/download/
>
> Or, check out one of our popular variants, including KDE Plasma, Xfce,
> and other desktop environments, as well as images for ARM devices:
>
> * Get Fedora 34 Beta Spins: https://spins.fedoraproject.org/prerelease
> * Get Fedora 34 Beta Labs: https://labs.fedoraproject.org/prerelease
> * Get Fedora 34 Beta ARM: https://arm.fedoraproject.org/prerelease
>
> ## Beta Release Highlights
>
> * BTRFS transparent compression
>
> * Replacing PulseAudio with PipeWire
>
> * Fedora 34 Workstation Beta includes GNOME 40
>
> * A new i3 spin
>
> * And more ...
>
> For more details about the release, read the full announcement at
>
> * https://fedoramagazine.org/announcing-the-release-of-fedora-34-beta/
>
> or look for the prerelease pages in the download sections at
>
> * https://getfedora.org/
>
> Since this is a Beta release, we expect that you may encounter bugs or
> missing features. To report issues encountered during testing, contact
> the Fedora QA team via the t...@lists.fedoraproject.org mailing list or
> in #fedora-qa on Freenode.
>
> Regards,
> Mohan Boddu
> Fedora Release Engineering.
> ___
> test-announce mailing list -- test-annou...@lists.fedoraproject.org
> To unsubscribe send an email to
> test-announce-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
> --
>
> Date: Wed, 24 Mar 2021 09:28:38 +0100
> From: Marius Schwarz 
> Subject: Re: is the license AGPL 3.0 useable in terms of distributing
> the software as a package?
> To: devel@lists.f

Review swap: guestfs-tools

[Richard W.M. Jones]

https://bugzilla.redhat.com/show_bug.cgi?id=1942114

This is actually a split of an existing package.  The existing package
(https://src.fedoraproject.org/rpms/libguestfs) is huge and unwieldy
and upstream we've split off the tools part from the library part.  So
I want to make the same change downstream.  It's explained in more
detail in the bug comments.

Will swap for a package of similar complexity.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)

[Daniel Pocock]

On 22/02/2021 22:43, Dan Horák wrote:
> On Mon, 22 Feb 2021 21:19:26 -
> "Tom Seewald"  wrote:
> 
>>> On 22/02/2021 21:18, Tom Seewald wrote:
>>>
>>>
>>>
>>> Personally, I have an older GPU, RX 580 Polaris series, I will only
>>> spend dev time on the AMD Navi GPU issues after AMD makes the RX 6800 XT
>>> available in my region.  I simply don't have that card and I'm not going
>>> to waste money buying the original Navi card, RX 5700, when the new card
>>> will arrive imminently.
>>
>> There is no indication from the bug report that it requires a Navi card to 
>> reproduce. The reporter stated that they are using a RX Vega 56 which is the 
>> previous gpu generation. Why do you believe this is specific to Navi devices?

To clarify, there are a range of different issues with different amdgpu
cards

If anybody can provide tips for troubleshooting in any of these bug
reports it would be very welcome.

https://gitlab.freedesktop.org/drm/amd/-/issues/1519
navi2 - RX 6900 XT

https://gitlab.freedesktop.org/drm/amd/-/issues/1446
vega RX 56 Red Dragon

https://gitlab.freedesktop.org/drm/amd/-/issues/1293
Fiji-based cards since kernel 5.7



>>> Ultimately, even if it isn't hard to bisect, it doesn't feel fair that
>>> AMD is validating their drivers work on x86 before a release but the
>>> ppc64le users have to check things after a buggy release.
>>
>> Unfortunately smaller platforms will almost always get less testing than the 
>> more popular platforms, and I don't see that trend changing in the 
>> foreseeable future. This is where motivated community members need to come 
>> in. I doubt amdgpu developers even have easy access to ppc64le hardware.

Does anybody know about programs from AMD or any other vendor to make
their hardware available to volunteers in the Fedora development world?

This is even more critical now that GPU delivery is such a huge problem.
 Shops that receive stock are selling it at double the RRP.  Volunteers
won't rush to buy those cards and it will take even longer to fully
support them.

Simply having a critical mass of developers with the right hardware can
make a huge difference.  For example, with 7 developers, maybe a given
platform is always overloaded but with 8 developers maybe the backlog of
bugs is fixed faster than new bugs are discovered.  The same phenomena
appears in so many domains: what some of us perceive now is like the
congestion on a freeway at peak hour when the cars come in faster than
they can go out.


>> I will also say that regardless of ISA there are going to be times where 
>> bisection is needed. I have personally had to bisect and report an issue 
>> with amdgpu and I am using x86 hardware. There's also a decent chance I'm 
>> going to be bisecting another amdgpu bug this evening. I am not expecting 
>> you or others to do things that I am not willing to do myself.
>>  
>>> I'm all in favor of collaboration with the AMD and kernel developers
>>>
>>> Ultimately, the only way to ensure equality across different
>>> architectures is to have upstream developers using all of these
>>> architectures throughout their development cycle.
>>
>> It would of course be great if amd fully tested their drivers on every 
>> architecture that Linux supports, but I don't think that's currently a 
>> realistic expectation for *any* device/driver vendor. If amdgpu support is 
>> something that is important to IBM, Talos, or other members of OpenPower, 
>> then I think reaching out to developers and offering free ppc64le hardware 
>> or VM access for kernel development and testing would be an excellent start. 
>> Providing automated ppc64le build and boot testing for the 
>> amd-staging-drm-next tree would be great as well.
> 
> There has been such idea within the OpenPOWER Foundation some time ago,
> to have a lab where (primarily) HW vendors would have access and could
> test their HW and drivers on a number of different platforms. I suppose
> we should revive this idea.
> 

In the SIP world, we had SIPit events for this type of testing from time
to time.  Having people get together can be fun and productive.  Maybe
it will be possible in 2022 or beyond.  From a Fedora perspective, it
could be interesting to align it with the release schedule.

https://www.sipforum.org/news-events/test-event-wg-overview-and-charter-sipit/upcoming-sipit-events/

> 
>   Dan
> 
>>
>>> How can we encourage greater use of ppc64le and aarch64 in those
>>> communities?  While it may sound trivial, I made a post here last week
>>> about how we can help people choose the right workstation through the wiki:
>>>
>>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
>>>
>>> I estimate spending one or two hours in my own comparison of the Raptor
>>> motherboards and I hope the table allows other developers to save the
>>> same amount of time.
>>
>> While there's no silver bullet, reaching out to the upstream developers 
>> (e.g. via their mailing list) and havin

Summary/Minutes from today's FESCo Meeting (2021-03-24)

[David Cantrell]

=
#fedora-meeting-2: FESCO (2021-03-24)
=


Meeting started by dcantrell at 14:00:13 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-03-24/fesco.2021-03-24-14.00.log.html
.



Meeting summary
---
* init process  (dcantrell, 14:00:16)
  * ACTION: everyone read and add additional comments to the ticket;
hopefully voting takes place there  (dcantrell, 14:29:24)
  * AGREED: (+9,0,-0)  (dcantrell, 14:33:51)
  * ACTION: mhroncok to open infra ticket to do it  (mhroncok, 14:34:04)

* Next week's chair  (dcantrell, 14:34:37)
  * ACTION: zbyszek will chair next meeting  (dcantrell, 14:35:24)

* Open Floor  (dcantrell, 14:35:30)
  * ACTION: zbyszek will update the FESCo meeting times to 17UTC on
Tuesdays  (dcantrell, 14:57:00)
  * ACTION: bcotton will help us verify irc meeting room we can use on
Tuesdays at 17UTC  (dcantrell, 14:59:42)
  * LINK:

https://apps.fedoraproject.org/calendar/location/fedora-meeting-2%40irc.freenode.net/
(zbyszek, 14:59:50)

Meeting ended at 15:02:28 UTC.




Action Items

* everyone read and add additional comments to the ticket; hopefully
  voting takes place there
* mhroncok to open infra ticket to do it
* zbyszek will chair next meeting
* zbyszek will update the FESCo meeting times to 17UTC on Tuesdays
* bcotton will help us verify irc meeting room we can use on Tuesdays at
  17UTC




Action Items, by person
---
* mhroncok
  * mhroncok to open infra ticket to do it
* zbyszek
  * zbyszek will chair next meeting
  * zbyszek will update the FESCo meeting times to 17UTC on Tuesdays
* **UNASSIGNED**
  * everyone read and add additional comments to the ticket; hopefully
voting takes place there
  * bcotton will help us verify irc meeting room we can use on Tuesdays
at 17UTC




People Present (lines said)
---
* mhroncok (74)
* dcantrell (72)
* Eighth_Doctor (68)
* zbyszek (41)
* sgallagh (18)
* zodbot (14)
* nirik (6)
* cverna (6)
* decathorpe (1)
* ignatenkobrain (0)
* Conan_Kudo (0)
* Sir_Gallantmon (0)
* King_InuYasha (0)
* Son_Goku (0)
* Pharaoh_Atem (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Summary/Minutes from today's FESCo Meeting (2021-03-24)

[Zbigniew Jędrzejewski-Szmek]

On Wed, Mar 24, 2021 at 11:13:30AM -0400, David Cantrell wrote:
> * zbyszek will update the FESCo meeting times to 17UTC on Tuesdays
> * bcotton will help us verify irc meeting room we can use on Tuesdays at
>   17UTC

Next meeting: Tuesday, 17:00 UTC, #fedora-meeting.

I updated the fedora calendar and the meeting page on wiki.
Please let me know if I missed some spot.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-IoT-34-20210324.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 2/15 (aarch64), 1/16 (x86_64)

New failures (same test not failed in Fedora-IoT-34-20210321.0):

ID: 828221  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/828221

Old failures (same test failed in Fedora-IoT-34-20210321.0):

ID: 828205  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/828205
ID: 828214  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/828214

Soft failed openQA tests: 1/16 (x86_64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-34-20210321.0):

ID: 828199  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/828199

Passed openQA tests: 14/16 (x86_64), 13/15 (aarch64)

New passes (same test not passed in Fedora-IoT-34-20210321.0):

ID: 828197  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/828197
ID: 828209  Test: x86_64 IoT-dvd_ostree-iso podman
URL: https://openqa.fedoraproject.org/tests/828209
ID: 828210  Test: x86_64 IoT-dvd_ostree-iso podman_client
URL: https://openqa.fedoraproject.org/tests/828210
ID: 828213  Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/828213
ID: 828215  Test: aarch64 IoT-dvd_ostree-iso iot_greenboot@uefi
URL: https://openqa.fedoraproject.org/tests/828215
ID: 828216  Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi
URL: https://openqa.fedoraproject.org/tests/828216
ID: 828217  Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_rebase@uefi
URL: https://openqa.fedoraproject.org/tests/828217
ID: 828218  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/828218
ID: 828219  Test: aarch64 IoT-dvd_ostree-iso base_reboot_unmount@uefi
URL: https://openqa.fedoraproject.org/tests/828219
ID: 828220  Test: aarch64 IoT-dvd_ostree-iso base_system_logging@uefi
URL: https://openqa.fedoraproject.org/tests/828220
ID: 828222  Test: aarch64 IoT-dvd_ostree-iso base_selinux@uefi
URL: https://openqa.fedoraproject.org/tests/828222
ID: 828223  Test: aarch64 IoT-dvd_ostree-iso base_service_manipulation@uefi
URL: https://openqa.fedoraproject.org/tests/828223
ID: 828224  Test: aarch64 IoT-dvd_ostree-iso podman@uefi
URL: https://openqa.fedoraproject.org/tests/828224
ID: 828225  Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi
URL: https://openqa.fedoraproject.org/tests/828225
ID: 828226  Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/828226
ID: 828227  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi
URL: https://openqa.fedoraproject.org/tests/828227
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora Accounts Migration & Production Rollout Update: Day 1/2

[Aoife Moloney]

Hi Everyone,

Just wanted to share a quick update on the New Fedora Accounts deployment
to production and migration.

The team are working around the clock to configure all systems to
authenticate with the new service and you are likely to
experience inaccessibility to some services over the next 24 - 48 hours. If
you try to login to some services and recieve an 'Unknown User' or 'OpenID
request Cancelled' or similar, please try clearing cookies and try to
re-log in. If this still doesn't work, the accounts team are likely working
on this service at that moment. Please wait a few hours and re-try. If you
have any serious issues logging into services. please file a ticket in
https://pagure.io/fedora-infrastructure and our team will look into them as
soon as the production rollout has been completed. We are still expecting
this to be completed by Friday 26th March.

Over the next 24 - 48 hours, we are asking you all to please be patient
with us while we operationalize the new service and sincerely thank you for
your understanding during this outage period.

Our team is working in channel freenode #fedora-aaa and we would like to
also offer our sincerest gratitude and thanks to those of you across the
Fedora and CentOS communities who are helping us roll the new system out.

We will send another status report tomorrow on the progress we have made
and you can also use https://status.fedoraproject.org/ to check on service
downtime.

On behalf of the Fedora Accounts team, thank you all again for bearing with
us while we complete this project!


Kindest regards,
Aoife & The Fedora Account Team

-- 

Aoife Moloney

Product Owner

Community Platform Engineering Team

Red Hat EMEA 

Communications House

Cork Road

Waterford

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Default 'fedora' hostname and failing split DNS VPN

[Robert Marcano via devel]

Currently I am connecting to a VPN that provides a few DNS search 
entries. One of these domains on the search path is having DNS 
resolution problems. This is not per se the the problem I am  writing 
this email for.


The problem is that starting Firefox and Thunderbird take a long time, 
it took time to detect the DNS resolution problem was the origin of 
these timeouts. I am not using that domain that is having resolution 
problems.


The real culprit is the default `fedora` hostname, instead of localhost. 
Starting a Wireshark capture there are DNS searches for 
fedora.domain_failing.tld, when starting Firefox and Thunderbird. The 
presence of the search path on generated /etc/resolv.conf isn't the 
cause of these DNS searches, I edited them out while the VPN was still 
active.


Even 'ping fedora' start doing these searches with the search paths 
appended. 'ping localhost' doesn't do that. The only workaround to this 
issue is to add fedora to the localhost entries on /etc/hosts.


This in some way is a DNS leak, even on a VPN with perfectly working DNS 
resolution, the fedora name should not be searched on these domains 
until I am using the fedora full hostname on these domains. Even worse 
when simply starting applications like Firefox o Thunderbird.


Maybe changing the default hostname to fedora wasn't a good idea after 
all, or at least fedora should be added to the default /etc/hosts.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Default 'fedora' hostname and failing split DNS VPN

[Michael Catanzaro]

Hi,

I have a couple different ideas of what could be going wrong. Let's 
test a few things. First, please run:


$ cat /etc/nsswitch.conf | grep hosts | tail -1

If it is our default configuration, it should say:

hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] 
myhostname dns


Now, see what happens if you disable systemd-resolved:

$ sudo systemctl stop systemd-resolved.service

Does the bug go away? If so, it's likely a systemd-resolved bug to be 
fixed. (Reenable systemd-resolved with 'sudo systemctl start 
systemd-resolved.service'.)


If the bug does NOT go away, then let's test one more thing: please 
edit /etc/authselect/user-nsswitch.conf as root and change the hosts 
line to look like this:


hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns


Then run:

$ sudo authselect apply-changes

Does the bug go away? I think that should almost certainly "fix" it. If 
so, you have a good workaround, and we know the problem must be caused 
by avahi, and we should reconsider our NSS configuration. But if the 
bug does not go away after this big hammer, then it must be a 
Firefox/Thunderbird bug, because if they try to resolve anything that 
doesn't exactly match the local hostname, then of course we have to do 
some DNS.


I'm interested to see the your results,

Michael

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure