Repository navigation
Tags
Tags
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
octeon: append fwtool metadata to vEdge 1000 sysupgrade images (#25) The cisco,vedge1000 squashfs sysupgrade tar was built without embedded fwtool image metadata, so sysupgrade printed "Image metadata not present" on every run and could not validate SUPPORTED_DEVICES / version compatibility -- it fell back to the sysupgrade-<board>/ directory-name check in platform_check_image alone. The octeon Device/Default sysupgrade recipe never pipes through append-metadata; only itus_shield-router opts in. Add the same append-metadata step to cisco_vedge1000. SUPPORTED_DEVICES already defaults to the device name (cisco,vedge1000), so the metadata now carries supported_devices plus the version/target/board block. Verified by rebuilding the image: fwtool -i on the resulting tar now returns the metadata JSON (supported_devices ["cisco,vedge1000"] and the version block) instead of "Data not found". Fixes #24
PreviousNext