[buildsystem]: Fix error 'chown: missing operand after'#13569
[buildsystem]: Fix error 'chown: missing operand after'#13569liat-grozovik merged 1 commit intosonic-net:masterfrom
Conversation
|
PR contains a fix for: #13412 |
|
We can't build SONiC locally if we use default value SONIC_BUILD_RETRY_COUNT=0. |
Signed-off-by: Nazarii Hnydyn <[email protected]>
2b0d922 to
ab0c36f
Compare
|
@liushilongbuaa could you please review following your comment? |
| fi | ||
| PKG_CACHE_FILE_NAME=${PKG_CACHE_PATH}/cache.tgz | ||
| $SUDO mkdir -p ${PKG_CACHE_PATH} | ||
| $SUDO chown $USER $PKG_CACHE_PATH |
There was a problem hiding this comment.
From the log, it looks like $USER="".
But it needs tests. SUDO can't be removed. Because there will be other error message.
There was a problem hiding this comment.
@liushilongbuaa originally it was without sudo. Please see the PR description. Looks like sudo is not needed since the cache path is created with the regular user privileges long before executing the script during docker container build (environment doesn't have USER variable defined)
There was a problem hiding this comment.
Building sonic-slave-* is different from build target/sonic-*.gz.
Some needs sudo, but some din't need.
I added sudo because of error message.
|
Maybe change |
@liushilongbuaa This is not a good way, since we should aim to utilize the FYI: nazariig@sonic-build-server: sonic-buildimage$ tree -ugh target/vcache/
target/vcache/
|-- [nazariig dev 4.0K] docker-base-buster
|-- [nazariig dev 4.0K] sonic-slave-bullseye
| `-- [nazariig dev 124] cache.tgz
`-- [nazariig dev 4.0K] sonic-slave-buster
`-- [nazariig dev 125] cache.tgz
3 directories, 2 files |
|
https://dev.azure.com/mssonic/build/_build/results?buildId=201413&view=logs&j=3dc8fd7e-4368-5a92-293e-d53cefc8c4b3&t=44e6c678-cb87-52d9-8547-bcdbd0ad6ae4 |
|
LGTM, the user should have the permission to access PKG_CACHE_PATH without sudo, /vcache/ or /sonic/target/vcache. |
|
@liushilongbuaa I see your comments is not fully addressed, still has some concern on this PR? |
|
@StormLiangMS , just go a head. My concern is fixed through pipeline settins. |
|
When cherry-pick to 202211, this one should be after #13412 |
|
@nazariig PR conflicts with 202205 branch |
|
@nazariig please create separate PR for 202205 branch. |
|
@nazariig, because manually cherry-pick conflict, please also create cherry-pick PR for 202012 branch. |
|
@nazariig PR conflicts with 202211 branch |
|
Remove request label because #13412 will not backport. |
Related work items: sonic-net#276, sonic-net#305, sonic-net#332, sonic-net#338, sonic-net#339, sonic-net#1188, sonic-net#1192, sonic-net#1197, sonic-net#1206, sonic-net#1685, sonic-net#1690, sonic-net#1696, sonic-net#1699, sonic-net#1709, sonic-net#1727, sonic-net#1737, sonic-net#1741, sonic-net#1742, sonic-net#2511, sonic-net#2512, sonic-net#2532, sonic-net#2559, sonic-net#2626, sonic-net#2638, sonic-net#2645, sonic-net#2649, sonic-net#2660, sonic-net#2669, sonic-net#2670, sonic-net#2678, sonic-net#10084, sonic-net#11442, sonic-net#11873, sonic-net#12047, sonic-net#12110, sonic-net#12207, sonic-net#12529, sonic-net#12678, sonic-net#13235, sonic-net#13287, sonic-net#13372, sonic-net#13395, sonic-net#13456, sonic-net#13497, sonic-net#13522, sonic-net#13545, sonic-net#13547, sonic-net#13552, sonic-net#13569, sonic-net#13572, sonic-net#13578, sonic-net#13591, sonic-net#13611, sonic-net#13647, sonic-net#13649, sonic-net#13660, sonic-net#13710, sonic-net#13716, sonic-net#13724, sonic-net#13726, sonic-net#13732, sonic-net#13735, sonic-net#13739, sonic-net#13757, sonic-net#13786, sonic-net#13792, sonic-net#13800, sonic-net#13801, sonic-net#13802, sonic-net#13805, sonic-net#13806, sonic-net#13812, sonic-net#13814, sonic-net#13822, sonic-net#13831, sonic-net#13834, sonic-net#13847, sonic-net#13870, sonic-net#13882, sonic-net#13884, sonic-net#13885, sonic-net#13894, sonic-net#13895, sonic-net#13926, sonic-net#13932, sonic-net#13935, sonic-net#13942, sonic-net#13951, sonic-net#13953, sonic-net#13964
Fixes: #13395
This fix resolves ownership configuration for
vcache:Originally the issue was introduced here: #13287
Why I did it
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)