[Starlingx-discuss] repo sync failures: 503 error in ima-evm-utils.git
We are currently seeing the following error from 'repo sync' up here in Ottawa. fatal: unable to access 'https://git.code.sf.net/p/linux-ima/ima-evm-utils.git/': The requested URL returned error: 503 Timestamp is roughly 2018-10-15 18:45 UTC Can other sites see this ? *Workaround:* If you already have an established repo, including ima, you can use the following to refresh your repo ... repo sync --optimized-fetch This works because ima in our manifest is anchored to a specific tag/sha, which you already have downloaded, so no need to refresh that specific git.
It looks like ima is no longer compiled by StarlingX. grep -r ima $MY_REPO/stx/stx*/centos_pkg_dirs* << nothing found >> We are now using externally built binaries. grep ima-evm-utils $MY_REPO/../stx-tools/centos-mirror-tools/*.lst .../stx-tools/centos-mirror-tools/rpms_centos3rdparties.lst:ima-evm-utils-1.1-2.el7.x86_64.rpm .../stx-tools/centos-mirror-tools/rpms_centos3rdparties.lst:ima-evm-utils-devel-1.1-2.el7.x86_64.rpm I believe ima can safely be removed from the manifest. Scott On 18-10-15 02:56 PM, Scott Little wrote:
We are currently seeing the following error from 'repo sync' up here in Ottawa.
fatal: unable to access 'https://git.code.sf.net/p/linux-ima/ima-evm-utils.git/': The requested URL returned error: 503
Timestamp is roughly 2018-10-15 18:45 UTC
Can other sites see this ?
*Workaround:*
If you already have an established repo, including ima, you can use the following to refresh your repo ...
repo sync --optimized-fetch
This works because ima in our manifest is anchored to a specific tag/sha, which you already have downloaded, so no need to refresh that specific git.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Mon, Oct 15, 2018 at 2:27 PM Scott Little <scott.little@windriver.com> wrote:
It looks like ima is no longer compiled by StarlingX.
...
I believe ima can safely be removed from the manifest.
Even better! https://review.openstack.org/610710 Should this be backported to r/2018.10 too? dt -- Dean Troyer dtroyer@gmail.com
Yes, please backport. Scott On 18-10-15 03:35 PM, Dean Troyer wrote:
On Mon, Oct 15, 2018 at 2:27 PM Scott Little <scott.little@windriver.com> wrote:
It looks like ima is no longer compiled by StarlingX. ...
I believe ima can safely be removed from the manifest. Even better!
https://review.openstack.org/610710
Should this be backported to r/2018.10 too?
dt
On Mon, Oct 15, 2018 at 1:59 PM Scott Little <scott.little@windriver.com> wrote:
We are currently seeing the following error from 'repo sync' up here in Ottawa. fatal: unable to access 'https://git.code.sf.net/p/linux-ima/ima-evm-utils.git/': The requested URL returned error: 503
I am able to git clone that URL from home just now... (Google Fiber if it matters) dt -- Dean Troyer dtroyer@gmail.com
participants (2)
-
Dean Troyer
-
Scott Little