The atomic ISO images are using the wrong tree. The images built on 8/23 [1] yield the following system after an install:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC * 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
The tree it has on the ISO is from 06/15. Whereas the latest tree is actually something like this:
-bash-4.3# rpm-ostree status State: idle Deployments: fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.25 (2016-08-23 12:30:17) Commit: 29330133bb883ae3e257ceb40676bb21a59aecd98eb3068f0d3f8675a12ab4f3 OSName: fedora-atomic GPGSignature: (unsigned)
● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.13 (2016-08-09 04:25:51) Commit: 900457420c4881a937e9167fc6cde670cbada858e3290943417279a76708be75 OSName: fedora-atomic GPGSignature: (unsigned)
[1] - https://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-2016082...
Adding atomic-devel
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
The atomic ISO images are using the wrong tree. The images built on 8/23 [1] yield the following system after an install:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
- 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
The tree it has on the ISO is from 06/15. Whereas the latest tree is actually something like this:
-bash-4.3# rpm-ostree status State: idle Deployments: fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.25 (2016-08-23 12:30:17) Commit: 29330133bb883ae3e257ceb40676bb21a59aecd98eb3068f0d3f8675a12ab4f3 OSName: fedora-atomic GPGSignature: (unsigned)
● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.13 (2016-08-09 04:25:51) Commit: 900457420c4881a937e9167fc6cde670cbada858e3290943417279a76708be75 OSName: fedora-atomic GPGSignature: (unsigned)
[1] - https://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-2016082...
Adding rel-eng. They might be able to help us out more on this topic.
Dusty
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
The atomic ISO images are using the wrong tree. The images built on 8/23 [1] yield the following system after an install:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
- 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
The tree it has on the ISO is from 06/15. Whereas the latest tree is actually something like this:
-bash-4.3# rpm-ostree status State: idle Deployments: fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.25 (2016-08-23 12:30:17) Commit: 29330133bb883ae3e257ceb40676bb21a59aecd98eb3068f0d3f8675a12ab4f3 OSName: fedora-atomic GPGSignature: (unsigned)
● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.13 (2016-08-09 04:25:51) Commit: 900457420c4881a937e9167fc6cde670cbada858e3290943417279a76708be75 OSName: fedora-atomic GPGSignature: (unsigned)
[1] - https://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-2016082...
Adding rel-eng. They might be able to help us out more on this topic.
Could you maybe add a little bit more information? Like what tree is expected to be there etc? Presumably this is the two week release?
Peter
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
The atomic ISO images are using the wrong tree. The images built on 8/23 [1] yield the following system after an install:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
- 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
The tree it has on the ISO is from 06/15. Whereas the latest tree is actually something like this:
-bash-4.3# rpm-ostree status State: idle Deployments: fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.25 (2016-08-23 12:30:17) Commit: 29330133bb883ae3e257ceb40676bb21a59aecd98eb3068f0d3f8675a12ab4f3 OSName: fedora-atomic GPGSignature: (unsigned)
● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.13 (2016-08-09 04:25:51) Commit: 900457420c4881a937e9167fc6cde670cbada858e3290943417279a76708be75 OSName: fedora-atomic GPGSignature: (unsigned)
[1] - https://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-2016082...
cloud mailing list cloud@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On 08/25/2016 04:07 AM, Peter Robinson wrote:
Adding rel-eng. They might be able to help us out more on this topic.
Could you maybe add a little bit more information? Like what tree is expected to be there etc? Presumably this is the two week release?
Hey Peter,
Thanks for the reply. It looks like the latest two week release [1] that was released yesterday shows this problem:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC * 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
Honestly I have no idea where it is getting the wrong information from. I thought it was pointing at the old ref: http://dl.fedoraproject.org/pub/fedora/linux/atomic/24/refs/heads/fedora-ato... but that one is actually from 7/20:
2016-07-20 00:05:19 24.8 955a54ca5c fedora-atomic fedora-atomic:fedora-atomic/f24/x86_64/docker-host
So this iso is being build from a tree even older than that maybe it is pulling from some old koji internal location (from before f24 release?)
Dusty
[1] https://download.fedoraproject.org/pub/alt/atomic/stable/Atomic/x86_64/iso/F...
On 08/23/2016 10:09 PM, Dusty Mabe wrote:
The atomic ISO images are using the wrong tree. The images built on 8/23 [1] yield the following system after an install:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
- 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
The tree it has on the ISO is from 06/15. Whereas the latest tree is actually something like this:
-bash-4.3# rpm-ostree status State: idle Deployments: fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.25 (2016-08-23 12:30:17) Commit: 29330133bb883ae3e257ceb40676bb21a59aecd98eb3068f0d3f8675a12ab4f3 OSName: fedora-atomic GPGSignature: (unsigned)
● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.13 (2016-08-09 04:25:51) Commit: 900457420c4881a937e9167fc6cde670cbada858e3290943417279a76708be75 OSName: fedora-atomic GPGSignature: (unsigned)
[1] - https://kojipkgs.fedoraproject.org/compose//twoweek/Fedora-Atomic-24-2016082...
cloud mailing list cloud@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
cloud mailing list cloud@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On 08/25/2016 12:05 PM, Dusty Mabe wrote:
On 08/25/2016 04:07 AM, Peter Robinson wrote:
Adding rel-eng. They might be able to help us out more on this topic.
Could you maybe add a little bit more information? Like what tree is expected to be there etc? Presumably this is the two week release?
Hey Peter,
Thanks for the reply. It looks like the latest two week release [1] that was released yesterday shows this problem:
-bash-4.3# rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
- 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
Honestly I have no idea where it is getting the wrong information from. I thought it was pointing at the old ref: http://dl.fedoraproject.org/pub/fedora/linux/atomic/24/refs/heads/fedora-ato... but that one is actually from 7/20:
2016-07-20 00:05:19 24.8 955a54ca5c fedora-atomic fedora-atomic:fedora-atomic/f24/x86_64/docker-host
So this iso is being build from a tree even older than that maybe it is pulling from some old koji internal location (from before f24 release?)
Dusty
[1] https://download.fedoraproject.org/pub/alt/atomic/stable/Atomic/x86_64/iso/F...
Dennis has looked into this and opened up a PR that we think will fix the issue: