Re: [atomic-devel] Fedora Atomic 2wk: Release Candidate
On 24/01/17, Dusty Mabe wrote: > > New build just finished with new kernel and new kubernetes versions that > prevented us from releasing our 2wk release last week. > > The vm images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/ > > The iso is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170124.1.iso > > > Please give these a sping and report any issues! The qcow2 image passed through all of our Fedora Atomic tests on Fedora Infra Openstack. $ ./gotun --job fedora Starts a new Tunir Job. Server ID: f15923aa-a523-4f7e-a538-fdcc58924952 Let us wait for the server to be in running state. Time to assign a floating pointip. Polling for a successful ssh connection. Polling for a successful ssh connection. Polling for a successful ssh connection. Polling for a successful ssh connection. Polling for a successful ssh connection. Polling for a successful ssh connection. Executing: curl -O http://infrastructure.fedoraproject.org/infra/autocloud/tunirtests.tar.gz Executing: tar -xzvf tunirtests.tar.gz Executing: ## sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtests -v Executing: ## sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtestBzip2 -v Executing: ## sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtestsCpio -v Executing: ## sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtestDiffutills -v Executing: ## sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtestaudit -v Executing: ## sudo python3 -m unittest tunirtests.selinux.TestSELinux -v Executing: ## sudo python3 -m unittest tunirtests.sshkeygentest.sshkeygenTest -v Executing: ## sudo python3 -m unittest tunirtests.testumountroot.TestUmountRoot -v Executing: sudo python3 -m unittest tunirtests.cloudtests.TestBase -v Executing: sudo python3 -m unittest tunirtests.cloudtests.TestCloudtmp -v Executing: sudo python3 -m unittest tunirtests.cloudtests.Testtmpmount -v Executing: sudo python3 -m unittest tunirtests.cloudtests.Testnetname -v Executing: ## python3 -m unittest tunirtests.cloudtests.TestJournalWritten -v Executing: sudo python3 -m unittest tunirtests.cloudservice.TestServiceStop -v Executing: sudo python3 -m unittest tunirtests.cloudservice.TestServiceDisable -v Executing: @@ sudo reboot Sleeping for 30 Executing: ## sudo python3 -m unittest tunirtests.testreboot.TestReboot -v Executing: sudo python3 -m unittest tunirtests.cloudservice.TestServiceManipulation -v Executing: ## python3 -m unittest tunirtests.cloudtests.TestJournalWrittenAfterReboot -v Executing: @@ sudo reboot Sleeping for 30 Executing: sudo python3 -m unittest tunirtests.cloudservice.TestServiceAfter -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestDockerInstalled -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestDockerStorageSetup -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestAtomicFirstBootRun -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestAtomicCommand -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestAtomicDockerImage -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestRootMount -v Executing: sudo python3 -m unittest tunirtests.atomictests.Testreadonlymount -v Executing: sudo python3 -m unittest tunirtests.atomictests.TestDockerDaemon -v Result file at: /tmp/tunirresult_062736880 Job status: true command: curl -O http://infrastructure.fedoraproject.org/infra/autocloud/tunirtests.tar.gz status:true %!T(MISSING)otal%!R(MISSING)eceived %!X(MISSING)ferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 12540 100 125400 0 23983 0 --:--:-- --:--:-- --:--:-- 23977 command: tar -xzvf tunirtests.tar.gz status:true tunirtests/ tunirtests/atomictests.py tunirtests/cloudservice.py tunirtests/cloudtests.py tunirtests/__init__.py tunirtests/loopbacktest.py tunirtests/nongatingtests.py tunirtests/selinux.py tunirtests/sshkeygentest.py tunirtests/testreboot.py tunirtests/testumountroot.py tunirtests/testutils.py tunirtests/LICENSE command: sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtests -v status:true test_bash (tunirtests.nongatingtests.TunirNonGatingtests) Tests the bash version as the same of upstream ... ok -- Ran 1 test in 0.002s OK command: sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtestBzip2 -v status:true test_bzip2 (tunirtests.nongatingtests.TunirNonGatingtestBzip2) Test to run a file through bzip2,bzcat,bunzip2 ... ok -- Ran 1 test in 0.011s OK command: sudo python3
Re: [atomic-devel] Fedora Atomic 2wk: Release Candidate
On 24/01/17, Dusty Mabe wrote: > > New build just finished with new kernel and new kubernetes versions that > prevented us from releasing our 2wk release last week. > > The vm images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/ > > The iso is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170124.1.iso > > > Please give these a sping and report any issues! Autocloud found the old ssh not available issue. Rest of the tests seems to be working properly. Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org
Re: [atomic-devel] Fedora Atomic 2wk: Release Candidate
On Tue, Jan 24, 2017, at 05:32 AM, Dusty Mabe wrote: > The vm images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/ As a reminder, Atomic Host uses rpm-ostree (which uses ostree) for updates, and in the future[1] hopefully the releases will be based on that, and disk images like this will be a secondary artifact. Hence, we should include the OSTree commit hash in these messages. Here's a quick way to extract it from the disk image without booting: $ (echo run; echo mount /dev/mapper/atomicos-root /; echo ls /ostree/deploy/fedora-atomic/deploy) | env LIBGUESTFS_BACKEND=direct guestfish --ro -a /srv/libvirt/gold/Fedora-Atomic-25-20170124.1.x86_64.qcow2 27b1ae24686697235c35b793b5c8ab0822b8427e892d3659f0cb300c400979fa.0 27b1ae24686697235c35b793b5c8ab0822b8427e892d3659f0cb300c400979fa.0.origin $ So anyone who wants to upgrade in place to this hash can do so via e.g.: $ atomic host deploy 27b1ae24686697235c35b793b5c8ab0822b8427e892d3659f0cb300c400979fa This is also: Version: 25.46 (2017-01-24 02:48:29) [1] https://pagure.io/releng/issue/6545
[atomic-devel] Fedora Atomic 2wk: Release Candidate
New build just finished with new kernel and new kubernetes versions that prevented us from releasing our 2wk release last week. The vm images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/ The iso is here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170124.1.iso Please give these a sping and report any issues! Dusty
