As we have to decommission an old IBM BladeCenter Chassis (8+y old now) we have to migrate some .stg. (non prod, non critical) services to different infra. https://git.stg.centos.org is part of these services
Non urgent but creating ticket so that it's in backlog and we can pick the task between other ones
Metadata Update from @arrfab: - Issue tagged with: centos-common-infra, low-gain, low-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
Due to some reports and now hardware issue, we'll have to migrate sooner than later :
[19109.584970] sd 5:0:0:0: [sdb] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=132s [19109.584973] sd 5:0:0:0: [sdb] CDB: Write(10) 2a 00 12 7a 04 00 00 20 00 00 [19109.584975] blk_update_request: I/O error, dev sdb, sector 309986304 [19109.585453] sd 5:0:0:0: [sdb] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=132s [19109.585456] sd 5:0:0:0: [sdb] CDB: Write(10) 2a 00 12 7a c4 00 00 20 00 00 [19109.585458] blk_update_request: I/O error, dev sdb, sector 310035456 [19134.508236] JBD2: Detected IO errors while flushing file data on dm-3-8 [25434.666475] connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4320092147, last ping 4320075928, now 4320102147 [25434.666554] connection5:0: detected conn error (1022) [37242.913540] connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4331900412, last ping 4331905424, now 4331910432 [37242.913614] connection5:0: detected conn error (1022) [87069.286399] EXT4-fs (dm-3): error count since last fsck: 2 [87069.286405] EXT4-fs (dm-3): initial error at time 1611890599: ext4_journal_check_start:56 [87069.286408] EXT4-fs (dm-3): last error at time 1611890599: ext4_journal_check_start:56
So creating some repositories through pagure api call ends with :
{ "error": "It is not possible to create the repo \"rpms/<reponame>\"", "error_code": "ENOCODE" }
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.