updatemgr: error while unpacking: shell command: tar -C /storage/update/untarTemp -xf /storage/update-staging/repo FAILED.
7 views
Skip to first unread message
Vaishali Dhakate
Feb 21, 2022, 11:25:58 AM2/21/22
to openxt
Dear openxt Team,
I have created a update.tar package from an openxt iso which we build after changing the https://raw.githubusercontent.com/OpenXT/bordel/master/templates/master/openxt.conf file.
We didn't do any changes to the code so there is no update as such only changed below. The openxt 10 and openxt 10.0.10 code/repo are just the same.
OPENXT_RELEASE="10.0.10"
Feb 21 11:41:01.326694 xec: invoked with: list-vms
Feb 21 11:41:01.368538 xec: invoked with: -o /vm/5e729829_8ec0_4859_907c_2b3b08205bd4 set icbinn-path /storage/sync/klc/,/config/sync/klc/
Feb 21 11:41:01.392154 dbd: [info|dbd] write :1.24 /vm/5e729829-8ec0-4859-907c-2b3b08205bd4/icbinn-path /storage/sync/klc/,/config/sync/klc/
Feb 21 11:41:01.392338 dbd: [info|dbd] Updating database
Feb 21 11:41:08.664214 updatemgr: in applyUpdateFromTarball
Feb 21 11:41:08.664825 updatemgr: in stage: NoUpdate
Feb 21 11:41:08.665291 updatemgr: and in the right stage
Feb 21 11:41:08.665476 dbd: [info|dbd] write :1.21 /updatemgr/update-state applying
Feb 21 11:41:08.665641 dbd: [info|dbd] Updating database
Feb 21 11:41:08.674563 updatemgr: request to unpack "/storage/update-staging/repo" to "/storage/update/untarTemp"
Feb 21 11:41:08.690568 updatemgr: error while unpacking: shell command: tar -C /storage/update/untarTemp -xf /storage/update-staging/repo FAILED.
Feb 21 11:41:08.690587 updatemgr: unpacked "/storage/update-staging/repo" to "/storage/update/untarTemp"
Feb 21 11:41:08.690598 updatemgr: unpacked tarball to updateDirUntarTemp.
Feb 21 11:41:08.693110 kernel:[ 950.206373] audit: type=1400 audit(1645443668.679:10): avc: denied { read } for pid=7903 comm="tar" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
Feb 21 11:41:08.706040 updatemgr: Failed to apply update from tarball - 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
Feb 21 11:41:08.709149 dbd: [info|dbd] write :1.21 /updatemgr/update-fail-reason 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
Feb 21 11:41:08.710760 dbd: [info|dbd] write :1.21 /updatemgr/update-state failed
Feb 21 11:41:08.713185 kernel:[ 950.230886] audit: type=1400 audit(1645443668.699:11): avc: denied { read } for pid=1310 comm="updatemgr" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
This Synchronizer setup works for the download of update.tar which I procured online at
https://openxt.ainfosec.com/OpenXT/releases/9.0.0-rc2/6664/update/update.tar
I edit /etc/xenclient.conf and /config/xenclient.conf and set all the versions to 8
And I can download update.tar to my openxt 10 which is mocking as the version 8.
But Then I created a new build of openxt 10.0.10 with the same code as 10.0.0 .
From the openxt iso I copied the package.main to a tar file
tar -cvf update.tar package.main
I have the above error upon trying to download the repo / update.tar file.
Thanks for all the great support so far. And I feel grateful for the help.
Thanks and Regards
Vaishali.
I have created a update.tar package from an openxt iso which we build after changing the https://raw.githubusercontent.com/OpenXT/bordel/master/templates/master/openxt.conf file.
We didn't do any changes to the code so there is no update as such only changed below. The openxt 10 and openxt 10.0.10 code/repo are just the same.
OPENXT_RELEASE="10.0.10"
OPENXT_UPGRADEABLE_RELEASES="9.0.0 9.0.1 9.0.2 10.0.0"
Getting this error.
Feb 21 11:40:12.441617 VM syncvm (6): sync-client-daemon: klc: sync-client failed (exit status 5)
Feb 21 11:40:12.591347 VM syncvm (6): rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="501" x-info="https://www.rsyslog.com"] startFeb 21 11:41:01.326694 xec: invoked with: list-vms
Feb 21 11:41:01.368538 xec: invoked with: -o /vm/5e729829_8ec0_4859_907c_2b3b08205bd4 set icbinn-path /storage/sync/klc/,/config/sync/klc/
Feb 21 11:41:01.392154 dbd: [info|dbd] write :1.24 /vm/5e729829-8ec0-4859-907c-2b3b08205bd4/icbinn-path /storage/sync/klc/,/config/sync/klc/
Feb 21 11:41:01.392338 dbd: [info|dbd] Updating database
Feb 21 11:41:08.664214 updatemgr: in applyUpdateFromTarball
Feb 21 11:41:08.664825 updatemgr: in stage: NoUpdate
Feb 21 11:41:08.665291 updatemgr: and in the right stage
Feb 21 11:41:08.665476 dbd: [info|dbd] write :1.21 /updatemgr/update-state applying
Feb 21 11:41:08.665641 dbd: [info|dbd] Updating database
Feb 21 11:41:08.674563 updatemgr: request to unpack "/storage/update-staging/repo" to "/storage/update/untarTemp"
Feb 21 11:41:08.690568 updatemgr: error while unpacking: shell command: tar -C /storage/update/untarTemp -xf /storage/update-staging/repo FAILED.
Feb 21 11:41:08.690587 updatemgr: unpacked "/storage/update-staging/repo" to "/storage/update/untarTemp"
Feb 21 11:41:08.690598 updatemgr: unpacked tarball to updateDirUntarTemp.
Feb 21 11:41:08.693110 kernel:[ 950.206373] audit: type=1400 audit(1645443668.679:10): avc: denied { read } for pid=7903 comm="tar" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
Feb 21 11:41:08.706040 updatemgr: Failed to apply update from tarball - 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
Feb 21 11:41:08.709149 dbd: [info|dbd] write :1.21 /updatemgr/update-fail-reason 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
Feb 21 11:41:08.710760 dbd: [info|dbd] write :1.21 /updatemgr/update-state failed
Feb 21 11:41:08.713185 kernel:[ 950.230886] audit: type=1400 audit(1645443668.699:11): avc: denied { read } for pid=1310 comm="updatemgr" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
Feb 21 11:41:08.953912 uid: [info|uid] UI: An internal error occurred [106]
https://openxt.ainfosec.com/OpenXT/releases/9.0.0-rc2/6664/update/update.tar
I edit /etc/xenclient.conf and /config/xenclient.conf and set all the versions to 8
And I can download update.tar to my openxt 10 which is mocking as the version 8.
But Then I created a new build of openxt 10.0.10 with the same code as 10.0.0 .
From the openxt iso I copied the package.main to a tar file
tar -cvf update.tar package.main
I have the above error upon trying to download the repo / update.tar file.
Thanks for all the great support so far. And I feel grateful for the help.
Thanks and Regards
Vaishali.
Vaishali Dhakate
Feb 21, 2022, 11:22:13 PM2/21/22
to openxt
Dear openxt Team,
The repo/update.tar file of 10.0.10 with upgrade from:10.0.0 does not download. It gives the error above.
While changing the /etc/xenclient.conf and /config/xenclient.conf to 8 and trying to update using a update.tar which I get from https://openxt.ainfosec.com/OpenXT/releases/9.0.0-rc2/6664/update/update.tar works with the messages as in the log file attached.
So I need to figure out how to create an update.tar for my openxt 10.0.0 correctly..
Thanks and Regards,
Vaishali.
Vaishali Dhakate
Feb 22, 2022, 5:29:25 AM2/22/22
to openxt
Dear openxt Team,
The steps I used for the update.tar creation of 10.0.10 are these.
Download the openxt-installer.iso
sudo losetup /dev/loopX openxt-installer.iso
sudo mount /dev/loopX ./mnt
cp ./mnt/packages.main ../
tar -cvf update.tar packages.main
This fails for version 10.0.10
But, Download each file from https://openxt.ainfosec.com/OpenXT/releases/9.0.0-rc2/6664/repository/packages.main/
And tar -cvf update.tar packages.main
This works. If I change the openxt version to 8 and add this as the repo in the Synchronizer. This is version 9.
No problem, it works. The steps to generate the update.tar are correct then. So then I need to figure out why the update.tar of openxt 10.0.10 version is failing.
Thanks and Regards,
Vaishali.
The steps I used for the update.tar creation of 10.0.10 are these.
Download the openxt-installer.iso
sudo losetup /dev/loopX openxt-installer.iso
sudo mount /dev/loopX ./mnt
cp ./mnt/packages.main ../
tar -cvf update.tar packages.main
This fails for version 10.0.10
But, Download each file from https://openxt.ainfosec.com/OpenXT/releases/9.0.0-rc2/6664/repository/packages.main/
And tar -cvf update.tar packages.main
This works. If I change the openxt version to 8 and add this as the repo in the Synchronizer. This is version 9.
No problem, it works. The steps to generate the update.tar are correct then. So then I need to figure out why the update.tar of openxt 10.0.10 version is failing.
Thanks and Regards,
Vaishali.
Jason Andryuk
Feb 22, 2022, 8:12:57 AM2/22/22
to Vaishali Dhakate, openxt
Hi, Vaishali,
On Tue, Feb 22, 2022 at 5:29 AM Vaishali Dhakate
file. This includes proper cryptographic signing of the files.
>>
>> On Mon, Feb 21, 2022 at 9:55 PM Vaishali Dhakate <vaishali...@networkmarvels.com> wrote:
>>>
>>> Dear openxt Team,
>>> I have created a update.tar package from an openxt iso which we build after changing the https://raw.githubusercontent.com/OpenXT/bordel/master/templates/master/openxt.conf file.
>>> We didn't do any changes to the code so there is no update as such only changed below. The openxt 10 and openxt 10.0.10 code/repo are just the same.
>>> OPENXT_RELEASE="10.0.10"
>>>
>>> OPENXT_UPGRADEABLE_RELEASES="9.0.0 9.0.1 9.0.2 10.0.0"
>>>
>>> Getting this error.
>>>
>>> Feb 21 11:40:12.441617 VM syncvm (6): sync-client-daemon: klc: sync-client failed (exit status 5)
>>> Feb 21 11:40:12.591347 VM syncvm (6): rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="501" x-info="https://www.rsyslog.com"] start
>>> Feb 21 11:41:01.326694 xec: invoked with: list-vms
>>> Feb 21 11:41:01.368538 xec: invoked with: -o /vm/5e729829_8ec0_4859_907c_2b3b08205bd4 set icbinn-path /storage/sync/klc/,/config/sync/klc/
>>> Feb 21 11:41:01.392154 dbd: [info|dbd] write :1.24 /vm/5e729829-8ec0-4859-907c-2b3b08205bd4/icbinn-path /storage/sync/klc/,/config/sync/klc/
>>> Feb 21 11:41:01.392338 dbd: [info|dbd] Updating database
>>> Feb 21 11:41:08.664214 updatemgr: in applyUpdateFromTarball
>>> Feb 21 11:41:08.664825 updatemgr: in stage: NoUpdate
>>> Feb 21 11:41:08.665291 updatemgr: and in the right stage
>>> Feb 21 11:41:08.665476 dbd: [info|dbd] write :1.21 /updatemgr/update-state applying
>>> Feb 21 11:41:08.665641 dbd: [info|dbd] Updating database
>>> Feb 21 11:41:08.674563 updatemgr: request to unpack "/storage/update-staging/repo" to "/storage/update/untarTemp"
>>> Feb 21 11:41:08.690568 updatemgr: error while unpacking: shell command: tar -C /storage/update/untarTemp -xf /storage/update-staging/repo FAILED.
>>> Feb 21 11:41:08.690587 updatemgr: unpacked "/storage/update-staging/repo" to "/storage/update/untarTemp"
>>> Feb 21 11:41:08.690598 updatemgr: unpacked tarball to updateDirUntarTemp.
>>> Feb 21 11:41:08.693110 kernel:[ 950.206373] audit: type=1400 audit(1645443668.679:10): avc: denied { read } for pid=7903 comm="tar" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
This and ...
>>> Feb 21 11:41:08.706040 updatemgr: Failed to apply update from tarball - 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
>>> Feb 21 11:41:08.709149 dbd: [info|dbd] write :1.21 /updatemgr/update-fail-reason 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
>>> Feb 21 11:41:08.710760 dbd: [info|dbd] write :1.21 /updatemgr/update-state failed
>>> Feb 21 11:41:08.713185 kernel:[ 950.230886] audit: type=1400 audit(1645443668.699:11): avc: denied { read } for pid=1310 comm="updatemgr" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
... this SELinux failures are probably your problem. It looks like
"repo" which should be a directory is a symlink. I think this is
/storage/sync/klc/repo for your setup. However the policy expects it
to be a true directory. I'm not sure what you are doing there, but
`rm /storage/sync/klc/repo ; mkdir
/storage/sync/klc/repo ; restorecon -vRF /storage/sync/klc/repo`
should hopefully fix that.
Regards,
Jason
On Tue, Feb 22, 2022 at 5:29 AM Vaishali Dhakate
<vaishali...@networkmarvels.com> wrote:
> On Tue, Feb 22, 2022 at 9:51 AM Vaishali Dhakate <vaishali...@networkmarvels.com>
wrote:
> On Tue, Feb 22, 2022 at 9:51 AM Vaishali Dhakate <vaishali...@networkmarvels.com>
wrote:
>> So I need to figure out how to create an update.tar for my openxt 10.0.0 correctly..
FYI, `bordel deploy update` will create a properly formed update.tar
file. This includes proper cryptographic signing of the files.
>>
>> On Mon, Feb 21, 2022 at 9:55 PM Vaishali Dhakate <vaishali...@networkmarvels.com> wrote:
>>>
>>> Dear openxt Team,
>>> I have created a update.tar package from an openxt iso which we build after changing the https://raw.githubusercontent.com/OpenXT/bordel/master/templates/master/openxt.conf file.
>>> We didn't do any changes to the code so there is no update as such only changed below. The openxt 10 and openxt 10.0.10 code/repo are just the same.
>>> OPENXT_RELEASE="10.0.10"
>>>
>>> OPENXT_UPGRADEABLE_RELEASES="9.0.0 9.0.1 9.0.2 10.0.0"
>>>
>>> Getting this error.
>>>
>>> Feb 21 11:40:12.441617 VM syncvm (6): sync-client-daemon: klc: sync-client failed (exit status 5)
>>> Feb 21 11:40:12.591347 VM syncvm (6): rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="501" x-info="https://www.rsyslog.com"] start
>>> Feb 21 11:41:01.326694 xec: invoked with: list-vms
>>> Feb 21 11:41:01.368538 xec: invoked with: -o /vm/5e729829_8ec0_4859_907c_2b3b08205bd4 set icbinn-path /storage/sync/klc/,/config/sync/klc/
>>> Feb 21 11:41:01.392154 dbd: [info|dbd] write :1.24 /vm/5e729829-8ec0-4859-907c-2b3b08205bd4/icbinn-path /storage/sync/klc/,/config/sync/klc/
>>> Feb 21 11:41:01.392338 dbd: [info|dbd] Updating database
>>> Feb 21 11:41:08.664214 updatemgr: in applyUpdateFromTarball
>>> Feb 21 11:41:08.664825 updatemgr: in stage: NoUpdate
>>> Feb 21 11:41:08.665291 updatemgr: and in the right stage
>>> Feb 21 11:41:08.665476 dbd: [info|dbd] write :1.21 /updatemgr/update-state applying
>>> Feb 21 11:41:08.665641 dbd: [info|dbd] Updating database
>>> Feb 21 11:41:08.674563 updatemgr: request to unpack "/storage/update-staging/repo" to "/storage/update/untarTemp"
>>> Feb 21 11:41:08.690568 updatemgr: error while unpacking: shell command: tar -C /storage/update/untarTemp -xf /storage/update-staging/repo FAILED.
>>> Feb 21 11:41:08.690587 updatemgr: unpacked "/storage/update-staging/repo" to "/storage/update/untarTemp"
>>> Feb 21 11:41:08.690598 updatemgr: unpacked tarball to updateDirUntarTemp.
>>> Feb 21 11:41:08.693110 kernel:[ 950.206373] audit: type=1400 audit(1645443668.679:10): avc: denied { read } for pid=7903 comm="tar" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
>>> Feb 21 11:41:08.706040 updatemgr: Failed to apply update from tarball - 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
>>> Feb 21 11:41:08.709149 dbd: [info|dbd] write :1.21 /updatemgr/update-fail-reason 301:internal error: shell command: mv /storage/update/untarTemp/packages.main /storage/update/current FAILED.
>>> Feb 21 11:41:08.710760 dbd: [info|dbd] write :1.21 /updatemgr/update-state failed
>>> Feb 21 11:41:08.713185 kernel:[ 950.230886] audit: type=1400 audit(1645443668.699:11): avc: denied { read } for pid=1310 comm="updatemgr" name="repo" dev="dm-7" ino=29187 scontext=system_u:system_r:updatemgr_t:s0-s0:c0.c1023 tcontext=root:object_r:updatemgr_sync_client_storage_t:s0 tclass=lnk_file permissive=0
"repo" which should be a directory is a symlink. I think this is
/storage/sync/klc/repo for your setup. However the policy expects it
to be a true directory. I'm not sure what you are doing there, but
`rm /storage/sync/klc/repo ; mkdir
/storage/sync/klc/repo ; restorecon -vRF /storage/sync/klc/repo`
should hopefully fix that.
Regards,
Jason
Reply all
Reply to author
Forward
0 new messages